Archived/2017-Summer-Internships: Difference between revisions

From Xen
Jump to navigationJump to search
 
(8 intermediate revisions by 2 users not shown)
Line 20: Line 20:


== How To Apply to Outreachy ==
== How To Apply to Outreachy ==
The official program period for Outreachy Round 14 begins Feb 9. Please fill our your [https://wiki.gnome.org/Outreachy#Submit_an_Application 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 [[Outreachy/Apply|application FAQ]] for more info on how to fill our your initial application. Applicants will be notified in April if they have been accepted.
The official program period for Outreachy Round 14 begins Feb 9. Please fill our your [https://wiki.gnome.org/Outreachy#Submit_an_Application application] and complete your Xen Project patch by '''April 13, 2017'''. 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 [[Outreachy/Apply|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:
If you are interested in being a Xen Project intern, please:
Line 30: Line 30:
* Get yourself a suitable starter project (see [https://wiki.gnome.org/Outreachy#Make_a_Small_Contribution Requirement to Make a Small Code Contribution] and [[#Community_Reviewed_Project_List|table]] below).
* Get yourself a suitable starter project (see [https://wiki.gnome.org/Outreachy#Make_a_Small_Contribution Requirement to Make a Small Code Contribution] and [[#Community_Reviewed_Project_List|table]] below).
* Join the [http://xenproject.org/help/irc.html IRC] channel on irc.gnome.org related to the [[#Community_Reviewed_Project_List|table]] below (you are also free to join #xen-opw)
* Join the [http://xenproject.org/help/irc.html IRC] channel on irc.gnome.org related to the [[#Community_Reviewed_Project_List|table]] below (you are also free to join #xen-opw)
* Read our [[Outreachy/Apply|instructions for applying]], and apply by '''March 22nd 2016''' !
* Read our [[Outreachy/Apply|instructions for applying]], and apply by '''April 13, 2017''' !
* Ask one of our friendly developers on for a bite size bug or work item to fulfil the '''[https://wiki.gnome.org/Outreachy#Make_a_Small_Contribution 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'''.
* Ask one of our friendly developers on for a bite size bug or work item to fulfil the '''[https://wiki.gnome.org/Outreachy#Make_a_Small_Contribution Make a Small Contribution] Requirement'''. This can be reviewing somebody's code, submitting a patch, or similar and will need to be done by '''April 13, 2017'''.
* <span style="color:red">Make the application via https://outreachy.gnome.org</span>


== How To Apply to GSoC ==
== How To Apply to GSoC ==
Line 44: Line 45:
* Join the [http://xenproject.org/help/irc.html IRC] channel on irc.gnome.org related to the [[#Community_Reviewed_Project_List|table]] below (you are also free to join #xen-opw)
* Join the [http://xenproject.org/help/irc.html IRC] channel on irc.gnome.org related to the [[#Community_Reviewed_Project_List|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
* Familiarise yourself with our [[GSoC_Student_Application_Template]], such that you know what information you need to provide
* <span style="color:red">Make the application via https://summerofcode.withgoogle.com/get-started/</span>


== What is the Timeline? ==
== What is the Timeline? ==
Line 53: Line 55:
* February 27: Application system opens for Outreachy
* February 27: Application system opens for Outreachy
* March 20: Application system opens for GSoC
* March 20: Application system opens for GSoC
* March 30: Application deadline for Outreachy closes (but you can edit applications submitted until April 28th)
* '''April 3: Application deadline for GSoC'''
* April 3: Application deadline for GSoC
* '''<del>March 30</del> April 13: Application deadline for Outreachy''' (but you can edit applications submitted until April 28th)
* April 28: Accepted Outreachy proposals announced
* April 28: Accepted Outreachy proposals announced
* May 4: Accepted GSoC proposals announced
* May 4: Accepted GSoC proposals announced
Line 84: Line 86:
! style="font-weight:normal"| '''[http://xenproject.org/developers/teams/hypervisor.html Hypervisor]'''<br> <br>''Skills needed:''<br>Linux/BSD, C, scripting
! style="font-weight:normal"| '''[http://xenproject.org/developers/teams/hypervisor.html Hypervisor]'''<br> <br>''Skills needed:''<br>Linux/BSD, C, scripting
! style="font-weight:normal"| [[Outreach Program Projects]]
! style="font-weight:normal"| [[Outreach Program Projects]]
! style="font-weight:normal"| 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 [http://bugs.xenproject.org/xen/ bugs.xenproject.org].
! style="font-weight:normal"| 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 [http://bugs.xenproject.org/xen/ bugs.xenproject.org]. A full list of open tasks is available on the [https://xenproject.atlassian.net/projects/XEN/board Xen Project Feature Tracker], few of them might be small enough for an initial contribution.


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 [[Internships/Hypervisor]].
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 [[Internships/Hypervisor]].

Latest revision as of 17:55, 19 January 2018

What is an Internship?

You can find a basic overview of internships here.

What Internship Programs is the Xen Project participating in Summer 2017?

The Xen Project Advisory Board has funding for interns for Round 14 of Outreachy (formerly known as the GNOME Outreach Program) which runs from May 2017 to August 2017. The project will also apply as mentoring organisation for GSoC 2017.

  • 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. Note that our Outreachy landing page is here.
  • Google Summer of Code is a global program that offers students stipends to write code for open source projects. Note that our GSoC landing page is here.
  • As the project is participating in GSoC and Outreachy, we are not going to participate in Linux Foundation Internships

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. Note that exact requiremenst change slightly from year to year and may be impacted by laws in various regions: for full eligibility requirements see Outreachy/Eligibility.

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 14 begins Feb 9. Please fill our your application and complete your Xen Project patch by April 13, 2017. 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 IRC channel on irc.gnome.org related to the table below (you are also free to join #xen-opw)
  • Read our instructions for applying, and apply by April 13, 2017 !
  • 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 April 13, 2017.
  • Make the application via https://outreachy.gnome.org

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 Internships/Make a Small Contribution Requirement 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
  • Make the application via https://summerofcode.withgoogle.com/get-started/

What is the Timeline?

Typically the Outreachy and GSoC timelines are identical

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.

  • February 27 - March 20: Potential participants discuss application ideas with mentoring organizations
  • February 27: Application system opens for Outreachy
  • March 20: Application system opens for GSoC
  • April 3: Application deadline for GSoC
  • March 30 April 13: Application deadline for Outreachy (but you can edit applications submitted until April 28th)
  • April 28: Accepted Outreachy proposals announced
  • May 4: Accepted GSoC 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

  • May 30: Coding officially begins!
  • June 30 mid-term evaluations
  • August 29: End of GSoC program
  • August 30: End of Outreachy program

Mentor Timeline

Note that some of the GSoC and Outreachy deadlines for mentor organizations have not yet been announced.

  • April 7: 1st Mentor Meeting to discuss GSoC and Outreachy applications
  • April 14: 2nd Mentor Meeting to discuss GSoC and Outreachy applications
  • April 21: 3rd Mentor Meeting to discuss GSoC and Outreachy applications


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. A full list of open tasks is available on the Xen Project Feature Tracker, few of them might be small enough for an initial contribution.

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 Internships/Hypervisor.

xen-devel@lists.xenproject.org
IRC: #xendevel
Mirage OS

Skills needed:
Linux/BSD, OCaml
MirageOS Pioneer Projects
(old page with some extra info)
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.

Contributor Training

Information about GSoC

Information about Outreachy and past participants

Information For Mentors