Archived/GSoc 2014

__TOC__
The Xen Project is a Linux Foundation collaborative project that develops the 
* Xen Hypervisor (for x86 and ARM)
* The XAPI toolstack
* Mirage OS
The project also has excellent relationships with its upstreams (Linux Kernel, the BSDs, QEMU and other projects) and upstreams such as Linux distributions. This is reflected in the project list, which contains many interesting cross-project development projects for students.
== GSoC and Xen ==
This page is used to list project ideas for Google Summer of Code (GSOC) 2014. 
=== Key GSoC resources ===
Google Summer of Code 2014 is On (see ). The Xen Project has applied as a Mentoring Organization. Stay posted.
* Google Code-in 2013 and Google Summer of Code 2014 are on GSoC announcement
* GSoC Homepage
=== Finding a project that fits you ===
This page lists Xen Project development projects for GSoC that can be picked up by anyone! If you're interesting in hacking Xen Project code and want to become a part of our friendly developer community this is the place to start! Ready for the challenge?
To work on a project:
* Find a project that looks interesting (or a bug if you want to start with something simple)
* Send an email to the relevant mailing list (see Developer Mailing Lists) and let us know if you are interested in starting to work or applying on a specific project.
* Post your ideas, questions, RFCs to the relevant mailing list sooner than later so you can get comments and feedback. 
You have your own project idea: no problem!
* If you have your own project idea, outline what you are trying to do on the mailing list. If you know the right list, post your project idea on mailing list. Failing that post on xen-devel and we can redirect you to the right list. Make sure you add GSoC 2014 to the subject line.
It is a good idea to ...
The Xen Project has also participated in the Gnome Outreach Program for Women (OPW) in the past. One of the things we learned by participating in OPW is that you will be more successful, happier and get more out of participating in student programs such as GSoC, if you do a bit of prep-work before writing an application. Here is some stuff you can do:
* Contact your mentor early and get to know him or her
* If the Xen Project is accepted into GSoC, start hanging out on our IRC channel. You can use the #xen-opw IRC channel on freenode.net for now (if accepted, we will create a GSoC channel)
* You may want to ask the mentor for a couple of small bitesize work-items (such as reviewing someones patch, a bitesize bug, ...) and start communicating on the relevant mailing list. That helps you become familiar with our development process, the mentor and other community members and will help you chose the right project and help you decide whether the Xen project is for you.
* Note that quite a few Xen maintainers used to be GSoC students once. Feel free to ask community dot manager at xenproject dot org to put you in touch with them if you have questions about their experience.
* Any work you submit before applying for a project should be based on xen-unstable development tree, if the project is Xen Hypervisor and/or tools related. Linux kernel related patches should be based on upstream kernel.org Linux git tree (latest version). XAPI and Mirage OS patches should be based on the right codeline too. Check out the navigation by audience section on the left to find resources.
==== More resources ====
Quick links to changelogs of the various Xen related repositories/trees: Please see XenRepositories wiki page!
Before to submit patches, please look at Submitting Xen Patches wiki page and the relevant Xen Project team page. This will contain more information.
If you have new ideas, suggestions or development plans let us know and we'll update this list!
=== Aspiring Students ===
* Please contact the mentor and CC the most appropriate mailing list
* Get a bite-size task from the mentor before the application starts
* If you feel comfortable with an idea, please put your name to an idea using the following format
{{project
...
|Review=(delete as addressed)
* {{Comment|~~~~:}} I am interested in this idea ... 
 (note that you may also want to link to the e-mail thread with the mentor)
* You will need to request write access to the wiki by filling out this form
=== Applying for GSoC ===
To apply for a project, follow the steps outlined on
* melange
* We do have our own GSoC Student Application Template form
=== GSoC Projects that were accepted in 2014 ===
* Hi, I am working on this project.
== List of peer reviewed Projects ==
=== Domain support (PVOPS and Linux) ===
* Hi, I am interested to work on this project.
 
=== Xen Hypervisor Userspace Tools ===
* I am interested in this idea ( )
=== Mirage OS ===
== List of projects that need more work ==
=== Domain support (PVOPS and Linux) ===
=== Xen Hypervisor ===
=== Xen Hypervisor Userspace Tools ===
=== PCI Pass-through improvements ===
=== XAPI ===
== New Project Ideas ==
Please add new project ideas here, following 
== Conventions for Projects and Project Mentors == 
=== Rules and Advice for Adding Ideas ===
* Be creative
* Add projects into New Project Ideas or improve projects in Project Ideas that Need Review or more work through review comments.
* Use the template to encode ideas on this page. Please read the Template Documentation before you do so.
* Be specific: what do you want to be implemented; if at all possible provide an indication of size and complexity as described above to make it easier for a student to choose ideas
* Check that the project meets the GSoC Program Goals
* If you are willing to mentors those ideas, add your name and email to the idea.
* Aspiring mentors should introduce themselves on the most appropriate Xen Project mailing list
=== Peer Review Goals ===
We strongly recommend and invite project proposers and project mentors to review each others proposals. When you review, please look out for
* Can a student get going and started with the information in the project description
* Are any unstated assumptions in the proposal, is there undefined terminology, etc. in the proposal 
* Can the project completed in 3 months (assume that one month is needed for preparation)
* Does the project meet Google Summer of Code goals, which are
** Create and release open source code for the benefit of all
** Inspire young developers to begin participating in open source development
** Help open source projects identify and bring in new developers and committers 
** Provide students the opportunity to do work related to their academic pursuits (think "flip bits, not burgers")
** Give students more exposure to real-world software development scenarios (e.g., distributed development, software licensing questions, mailing-list etiquette)
=== Peer Review Conventions ===
The template used to encode GSoC projects, contains some review functionality. Please read the Template Documentation before you add a template, also please use the conventions below to make comments.
|Review=(delete as addressed)
* {{Comment|~~~~:}} Comment 1
* {{Comment|~~~~:}} Comment 2
=== Choosing Projects ===
We have a bi-weekly mentor meeting overlooked by our program management team, which are a core team of 2-3 mentors and a program administrator. This group will work with mentors to ensure that project proposals are of good quality and whether mentors are engaging with the program management team and students in the weeks before the application period ends. 
Category:GSoC
Category:GSoC 2014
Category:Developers
Category:Index
Category:Project
Category:Archived
Category:Internships
Category:Transient