Difference between revisions of "Archived/Outreachy/Round11"

From Xen
m (Timeline)
m (Information For Mentors)
Line 74: Line 74:
= Information For Mentors =
= Information For Mentors =
Please review the mentor information [https://wiki.gnome.org/Outreachy/Admin/InfoForMentors here]
Please review the mentor information
* [https://wiki.gnome.org/Outreachy/Admin/InfoForMentors here]
* [http://lists.xenproject.org/archives/html/xen-devel/2015-09/msg03386.html Mentor FAQ]
<!-- Round 8 data; replace with Round 9 when available
= Accepted Projects =
|Project=Improvements to the block I/O paravirtualized Xen drivers
|Contact=Mentor: Konrad Rzeszutek Wilk, Intern: Arianna Avanzini
|Desc= See [https://docs.google.com/document/d/16W9RkaZBBqKVoHJjTYhAEzPAtKnqes_wlrp6QJqloKs/edit?usp=sharing here]
|Project=MirageOS contributions and improvements
|Contact=Mentor: Richard Mortier, Intern: Mindy Preston
|Desc=1 booting on the myriad cloud providers remains a total pain, so figuring out how to create one command that takes some credentials and gets a unikernel started on rackspace/amazon/openstack would be very handy. There's also cloud-init to look at.
2 protocol bisimulations against existing implementations: for a number of our libraries, we'd like a way to test our protocol code against standard implementations and verify that they are functionally equivalent. In certain cases, we will of course know that they are not, so we should be able to mark those as TODOs in our code. Good protocol testing choices: the TCP/IP stack vs Linux, the Cohttp web stack vs Nginx/Apache, the emerging SSL stack vs OpenSSL (important!)
3 new functionality: adding IPv6 support into mirage-net would be fairly straightforward and rather useful. Multipath TCP and/or TCPcrypt are more difficult but in scope.
4 If you feel like low-level hackery, porting Xen MiniOS to ARM would be a difficult but exceedinly rewarding project, as Mirage would then run on embedded devices like the Cubieboard2. This is a kernel hacking heavy project.
5 you could also pen test the heck out of the libraries to find and fix denial of services (e.g. unbounded reads in Cohttp for long headers, that sort of thing). We know of quite a few, but a structured set of attacks would help keep them out.

Revision as of 11:02, 28 September 2015

Xen Project and Outreachy

The Xen Project Advisory Board will be sponsoring two interns for Round 11 of Outreachy (formerly known as the GNOME Outreach Program) which runs from Dec 7, 2015 to March 7, 2016. Outreachy helps people from groups underrepresented in free and open source software get involved. Our goal is to increase the participation of underrepresented groups in the Xen Project. It is an expansion of the very successful GNOME Outreach Program for Women and we are running the program in conjunction with GNOME and other prominent open source projects.

Information For Applicants


The program is open internationally to women (cis and trans), trans men, and genderqueer people. Additionally, it's open to residents and nationals of the United States of any gender who are Black/African American, Hispanic/Latin@, American Indian, Alaska Native, Native Hawaiian, or Pacific Islander (see outreachy/about).

How To Apply

The official program period for Outreachy Round 11 begins Dec 7. Please fill our your application and complete your Xen Project patch by November 2. Applicants that do not complete the first patch will not be considered for an internship. Please take a look at our application FAQ for more info on how to fill our your initial application. Applicants will be notified in April if they have been accepted.

If you are interested in being a Xen Project intern, please:

  • Join the xen-devel@, mirageos-devel@, ... mailing list depending on the project you choose (check the table below).
  • Get yourself a suitable starter project (see Requirement to Make a Small Code Contribution and table below).
  • Join the #outreachy IRC channel on irc.gnome.org for questions related to the program and to connect with other participants
  • Join the #xen-opw IRC channel on irc.freenode.net for meetings between applicants and mentors (note: we may change the channel name later to reflect the name change)
  • Read our instructions for applying, and apply by November 2nd 2015 !
  • Ask one of our friendly developers on for a bite size bug or work item to fulfil the Make a Small Contribution Requirement. This can be reviewing somebody's code, submitting a patch, or similar and will need to be done by November 2nd 2015.


  • September 29 (applicants): Application process opens
  • November 2 (applicants): Application deadline
  • November 6 (mentors): Xen Project mentors get together and evaluate applicants
  • November 9 (mentors): Xen Project decides which applicants to put forward
  • November 17 (applicants & mentors): Accepted applicants announced
  • December 7 - March 7 (applicants & mentors): Internship dates

Community Reviewed Project List

Xen Project Team Project List Small Code Contributions Contact Information

Skills needed:
Linux/BSD, C, scripting
Outreach Program Projects 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. Once you built trust, you may ask for access to coverity scan. Open bugs to fix under the Small Code Contribution Requirement can also be found on bugs.xenproject.org. xen-devel@lists.xenproject.org
IRC: #xendevel
Mirage OS

Skills needed:
Linux/BSD, OCaml
MirageOS Pioneer Projects Ask on the list mirageos-devel@lists.xenproject.org
IRC: #mirage

Skills needed:
Linux/BSD, OCaml
None at this stage Ask on the list xen-api@lists.xenproject.org
IRC: #xenapi

Useful Resources

Here is some links to guides, tools, development flows etc.

Contributor Training

Information about Outreachy and past participants

Information For Mentors

Please review the mentor information