|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [Minios-devel] [MirageOS-devel] Preparing for GSoC and Outreachy : getting Outreach Program Projects into good shape
On 24/01/18 10:22, Anil Madhavapeddy wrote: Looks good to me. The difficulties are all ‘medium’ though. Perhaps break up the “new execution targets” into medium/hard for the various backends? For example, Xen/ARM is probably easier than bare metal ARM, and I imagine HyperV is quite complex due to the extra coordination code that is required. To be honest, the only difference between Xen/ARM, KVM/Arm or bare metal are in term of drivers. The rest could be common and discovered through the firmware tables (e.g ACPI, DT). You could even share most of it between 32-bit and 64-bit too. Even for Xen/ARM I would still consider the project as medium/hard given the subtlety of the ARM ARM. Cheers, regards AnilOn 24 Jan 2018, at 09:40, Simon Kuenzer <simon.kuenzer@xxxxxxxxx <mailto:simon.kuenzer@xxxxxxxxx>> wrote:Hi all,since we are participating the first time to GSoC, we are happy to receive any feedback from you regarding our proposed Unikraft projects!https://wiki.xenproject.org/wiki/Outreach_Program_Projects#Unikraft Thanks, Simon On 23.01.2018 10:16, Lars Kurth wrote:Hi all, just a quick note that I submitted the application for GSoC.The project list is not perfect and I removed a number of projects because I believe they were completed (or at least started by others). A Thank You to Mirage OS and Unikraft folks for adding new projects If we do get accepted, we will have to have another go at the project listBest Regards LarsOn 8 Jan 2018, at 15:19, Lars Kurth <lars.kurth.xen@xxxxxxxxx <mailto:lars.kurth.xen@xxxxxxxxx>> 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 toa) 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 sameb) Decide whether you still want to mentor:This requires some of your bandwidth from mid-Feb to March 2018 to work on small projectsThe actual work happens from May 14 - Aug 14 If not, please reply and list projects affectedIf yes, please also do so and I will update the Verified field accordinglyc) 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 <http://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._______________________________________________ Minios-devel mailing listMinios-devel@xxxxxxxxxxxxxxxxxxxx <mailto:Minios-devel@xxxxxxxxxxxxxxxxxxxx>https://lists.xenproject.org/mailman/listinfo/minios-devel_______________________________________________ MirageOS-devel mailing listMirageOS-devel@xxxxxxxxxxxxxxxxxxxx <mailto:MirageOS-devel@xxxxxxxxxxxxxxxxxxxx>https://lists.xenproject.org/mailman/listinfo/mirageos-devel_______________________________________________ Minios-devel mailing list Minios-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/minios-devel -- Julien Grall _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-devel
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |