Archived/Outreachy/Round12+2016GSoC: Difference between revisions
Lars.kurth (talk | contribs) |
Lars.kurth (talk | contribs) |
||
| Line 94: | Line 94: | ||
|} |
|} |
||
<br> |
|||
== Useful Resources == |
== Useful Resources == |
||
Revision as of 16:54, 12 February 2016
Xen Project, Outreachy and GSoC 2016
The Xen Project Advisory Board will be sponsoring two interns for Round 12 of Outreachy (formerly known as the GNOME Outreach Program) which runs from May 23, 2016 to August 23, 2016. The project will also apply as mentoring organisation for GSoC 2016, which runs during the same time period as Outreachy.
- Outreachy helps people from groups underrepresented in free and open source software get involved in open source projects. 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.
- Google Summer of Code is a global program that offers students stipends to write code for open source projects.
Information For Applicants
Eligibility Outreachy
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).
Eligibility GSoC
The program is open to you, if you are enrolled in or into an accredited institution, including a college, university, undergraduate program, masters program, or PhD program. For more information, see gsoc/student_agreement.
How To Apply to Outreachy
The official program period for Outreachy Round 12 begins Feb 9. Please fill our your application and complete your Xen Project patch by March 22nd. Applicants that do not complete the first patch will not be considered for an internship. We will also require that you show some basic understanding in building and running the project you have chosen. 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:
- Start engaging with the developer community as early as possible
- Join the xen-devel@, mirageos-devel@, ... mailing list depending on the project you choose (check the table below). Please do no contact mentors privately - open source is about openness: use the mailing lists and CC the mentor(s).
- Check whether you have all the hardware you need to participate (see table below).
- Try to build the project (e.g. Hypervisor, Mirage OS, ...) from source and run it
- 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 March 22nd 2016 !
- 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 March 22nd 2016.
How To Apply to GSoC
We will provide more information related to GSoC, if the project is accepted as GSoC mentoring organization.
However, the following information applies generally
- Start engaging with the developer community as early as possible
- Join the xen-devel@, mirageos-devel@, ... mailing list depending on the project you choose (check the table below). Please do no contact mentors privately - open source is about openness: use the mailing lists and CC the mentor(s).
- Check whether you have all the hardware you need to participate (see table below).
- Try to build the project (e.g. Hypervisor, Mirage OS, ...) from source and run it
- Get yourself a suitable starter project (see Requirement to Make a Small Code Contribution and table below). Although GSoC does nor require a starter project, you will compete with applicants who will do so.
- Join the IRC channel on irc.gnome.org related to the table below (you are also free to join #xen-opw)
- Familiarise yourself with our GSoC_Student_Application_Template, such that you know what information you need to provide
Timeline
We will fill in the timeiine once the Outreachy/Round12 timeline has been published. The GSoc Timeline can be found here.
Pre-application and application period
During this time period, you should ensure that you familiarise yourself with the project, the community, make some small contributions and work on your proposal. The earlier you engage with the community, the more you will get out of participating.
- 29 February - 13 March: Would-be participants discuss application ideas with mentoring organizations.
- 14 March: application period opens.
- 25 March: application deadline.
- 22 April: accepted proposals announced
Bonding Period
If you have not done so, familiarise yourself with the project, the community, make some small contributions and work on your proposal. You should get to know mentors, read documentation, get up to speed to begin working on your project.
Program Period
- 23 May: begin coding
- 20 - 27 June : mid-term evaluations.
- 5 August - 23 August: Final week
Community Reviewed Project List
| Xen Project Team | Project List | Small Code Contributions | Contact Information |
|---|---|---|---|
| Hypervisor 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. 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.
Also note that to do Hypervisor development, you will need to have the correct hardware. You can find more information on how to check whether you have the right hardware at Outreachy/Hypervisor. |
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 |
| Infrastructure & Community | Infra and Community Projects | These may differ per individual project. Projects that are currently available are:
|
These may differ per individual project. Contact information for projects are:
|
| XAPI 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.
- All Developer Information
- Xen Project Overview
- Submitting Xen Patches with Git
- Xen Beginners Guide
- Introduction to Git
Contributor Training
- File:XP Contributor Training - Pt 1 Introduction v1.0.pdf
- XP Contributor Training - Pt 2 Processes and Conventions v1.1.pdf - split into two files due to file size
- XP Contributor Training - Pt 3 Communication v1.0.pdf - split into two files due to file size
- XP Contributor Training - Pt 4b Culture.pdf - split into three files due to file size
Information about Outreachy and past participants
- Xen Project Participates in Outreachy (formerly OPW)
- Are we growing our community with OPW and GSoC?
- Women interns rocking open source at Xen Project
Information For Mentors
- Please review general mentor information here
- Mentor FAQ for Round 11
