Hi all, (mentors on CC list) a quick note that there are significant changes to Outreachy this year, which in my view will make it a little harder to participate.
Namely * This round, instead of having communities create landing pages on their own websites or wikis coordinators and mentors will create accounts on the Outreachy website * This means we would have to copy projects from our wiki to https://www.outreachy.org <https://www.outreachy.org/> - I don't know what the template is yet, but this may create some extra work for mentors * The Outreachy application period opens in two weeks, on February 12. * Apart from this, there is fairly little information on the timeline and process for this round and Outreachy mail ended up in my spam folder: I was polling the website for info and there was not much Current status: * I have claimed the Xen Project page on https://www.outreachy <https://www.outreachy/> - waiting for it to be approved (I tried with an xenproject.org <http://xenproject.org/> alias which did not work) * We have funding for one intern (maybe more) and thus qualify. Whether I can find more funds, depends on the cost of the developer summit. Hopefully I will know more this week (I expect concrete developer summit proposal this week) Need input: * For us too participate I need at least 3-4 mentors and projects to be added to https://www.outreachy.org <https://www.outreachy.org/> * If you are willing to do this, please raise your hand now by replying to this thread or contacting me privately and I will help Best Regards Lars > On 8 Jan 2018, at 15:19, Lars Kurth <[email protected]> wrote: > > Hi All, > > it's this time of the year again to prepare for GSoC/Outreachy! The > application deadline for orgs is January 23 - February 11: ideally we will > have a good updated lists of projects by then as Google will look at the > quality of the project list. I will also need co-org admins: @Mindy are you > willing to do this again? Maybe also someone from the Unikraft project. That > helps ensure that we have reps from various subproject that ensure that we > don't miss deadlines. > > > Best Regards > Lars > > Existing Projects (for people on the CC list) > ================= > If you are CC'ed you have one or several projects listed on > https://wiki.xenproject.org/wiki/Outreach_Program_Projects ... What I need > you to do is to > > a) Weed out any projects that have been completed or are not relevant any more > @Mindy: For MirageOS folks, please check and update > https://github.com/mirage/mirage-www/wiki/Pioneer-Projects and do the same > > b) Decide whether you still want to mentor: > This requires some of your bandwidth from mid-Feb to March 2018 to work on > small projects > The actual work happens from May 14 - Aug 14 > > If not, please reply and list projects affected > If yes, please also do so and I will update the Verified field accordingly > > c) Add any new information to existing projects as relevant. > > > New Projects > ============ > Feel free to add new projects to the list, but if you do so please let the > list know. We are not going to be very strict with > https://wiki.xenproject.org/wiki/Outreach_Program_Projects#Conventions_for_Projects_and_Project_Mentors, > but getting someone else to review your proposal is a good idea. > > Unikraft > -------- > I created a place-holder for Unikraft at > https://wiki.xenproject.org/wiki/Outreach_Program_Projects#Unikraft as > Unikraft project members indicated they want to participate. > You probably do want to set expectations with regards to start-up tasks and > come up with a set of tasks to act as a filter for applicants (e.g. showing > that they set up the environment, etc.) > > > Specific Improvements to the project documentation > ================================================== > > Hypervisor start-up tasks > ------------------------- > https://wiki.xenproject.org/wiki/Xen_Project_Development_Projects contains: > "An easy way to get started (and show that you can set up the Xen Development > Environment, fix an issue, build and test Xen, submit a patch, etc.) is to > address a suitable number of Coverity Scan issues. Ask on xen-devel@ for a > set of suitable Coverity issues. Note that this does not require any access > to the Coverity scan results. Open bugs to fix under the Small Code > Contribution Requirement can also be found on bugs.xenproject.org" > > Do we want to change this? Finding small get started projects is always a > little bit of a problem. Maybe we can prepare a better list somewhere. > > In-tree vs. Wiki based projects > ------------------------------- > We could also decide to move Hypervisor related ideas in-tree somewhere and > generate a list if that makes things easier. But this is not necessary, in > particular given with everything that is going on. I just wanted to raise > this as an option: I am not particularly wedded to using the wiki. >
_______________________________________________ MirageOS-devel mailing list [email protected] https://lists.xenproject.org/mailman/listinfo/mirageos-devel
