Archived/2018-Summer-Internships: Difference between revisions
Lars.kurth (talk | contribs) |
Lars.kurth (talk | contribs) |
||
(22 intermediate revisions by the same user not shown) | |||
Line 7: | Line 7: | ||
The Xen Project Advisory Board has funding for interns for [https://www.outreachy.org/ Outreachy] this summer (formerly known as the GNOME Outreach Program) which runs from May 2018 to August 2018. The project will also apply as [https://developers.google.com/open-source/gsoc/timeline mentoring organisation for GSoC 2018]. |
The Xen Project Advisory Board has funding for interns for [https://www.outreachy.org/ Outreachy] this summer (formerly known as the GNOME Outreach Program) which runs from May 2018 to August 2018. The project will also apply as [https://developers.google.com/open-source/gsoc/timeline mentoring organisation for GSoC 2018]. |
||
* '''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. |
* '''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. For more information see [https://www.outreachy.org/2018-may-august/communities/xen-project/ 2018 May-August Xen Project approved projects] |
||
* '''Google Summer of Code''' is a global program that offers students stipends to write code for open source projects. |
|||
* We may also participate in [https://www.linuxfoundation.org/about/internships Linux Foundation Internships] |
|||
= Information For Applicants = |
= Information For Applicants = |
||
Line 16: | Line 14: | ||
The program is open <i>internationally if you identify as a women (cis and trans), trans man, or genderqueer person. Additionally, it's open to residents and nationals of the United States of any gender who are Black/African American, Hispanic/Latin, Native American/American Indian, Alaska Native, Native Hawaiian, or Pacific Islander</i>. Note that exact requirements change slightly from year to year and may be impacted by laws in various regions: for full eligibility requirements see [https://www.outreachy.org/apply/eligibility/ Outreachy/Eligibility]. |
The program is open <i>internationally if you identify as a women (cis and trans), trans man, or genderqueer person. Additionally, it's open to residents and nationals of the United States of any gender who are Black/African American, Hispanic/Latin, Native American/American Indian, Alaska Native, Native Hawaiian, or Pacific Islander</i>. Note that exact requirements change slightly from year to year and may be impacted by laws in various regions: for full eligibility requirements see [https://www.outreachy.org/apply/eligibility/ Outreachy/Eligibility]. |
||
{{WarningLeft|Before you can apply and see our project list, have you must have completed the [https://www.outreachy.org/eligibility/ Outreachy Eligibility Check]! Without having completed it, you cannot see our projects!}} |
|||
== Eligibility GSoC == |
|||
The program is open to you, if <i>you are enrolled in or into an accredited institution, including a college, university, undergraduate program, masters program, or PhD program</i>. For more information, see [http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2015/student_agreement gsoc/student_agreement]. |
|||
== How To Apply to Outreachy == |
== How To Apply to Outreachy == |
||
We will update this section, once more information for the next internship application period is available from [https://www.outreachy.org/apply/ Outreachy]. For more information on Xen Projects see [https://www.outreachy.org/communities/cfp/xen-project/ outreachy.org]. |
|||
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: |
|||
* Start engaging with the '''developer community as early as possible''' |
|||
* Join the [http://www.xenproject.org/help/mailing-list.html xen-devel@], [http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel mirageos-devel@], ... mailing list depending on the project you choose (check the [[#Community_Reviewed_Project_List|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 [[#Community_Reviewed_Project_List|table]] below). |
|||
* Try to build the project (e.g. Hypervisor, Mirage OS, ...) from source and run it |
|||
* 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) |
|||
* 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 '''April 13, 2017'''. |
|||
* <span style="color:red">Make the application via https://outreachy.gnome.org</span> |
|||
== 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 [http://www.xenproject.org/help/mailing-list.html xen-devel@], [http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel mirageos-devel@], ... mailing list depending on the project you choose (check the [[#Community_Reviewed_Project_List|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 [[#Community_Reviewed_Project_List|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 [[#Community_Reviewed_Project_List|table]] below). Although GSoC does nor require a starter project, you will compete with applicants who will do so. |
|||
* 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 |
|||
* <span style="color:red">Make the application via https://summerofcode.withgoogle.com/get-started/</span> |
|||
== What is the Timeline? == |
|||
Typically the [https://wiki.gnome.org/Outreachy/2017/MayAugust Outreachy] and [https://summerofcode.withgoogle.com/how-it-works/#timeline 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''' |
|||
* '''<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 |
|||
* 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 |
|||
<br> |
|||
== Community Reviewed Project List == |
== Community Reviewed Project List == |
||
Line 83: | Line 26: | ||
! style="width: 40%"| [https://wiki.gnome.org/Outreachy#Make_a_Small_Contribution Small Code Contributions] |
! style="width: 40%"| [https://wiki.gnome.org/Outreachy#Make_a_Small_Contribution Small Code Contributions] |
||
! style="width: 35%"| Contact Information |
! style="width: 35%"| Contact Information |
||
|- style="vertical-align: top;" |
|||
! colspan="4"|Hypervisor, mini-os and other core technology projects |
|||
|- style="vertical-align: top;" |
|- style="vertical-align: top;" |
||
! 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]. |
||
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]]. |
|||
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]]. |
|||
! style="font-weight:normal"| [http://lists.xenproject.org/cgi-bin/mailman/listinfo/xen-devel xen-devel@lists.xenproject.org]<br>[http://xenproject.org/help/irc.html IRC]: #xendevel |
! style="font-weight:normal"| [http://lists.xenproject.org/cgi-bin/mailman/listinfo/xen-devel xen-devel@lists.xenproject.org]<br>[http://xenproject.org/help/irc.html IRC]: #xendevel |
||
|- style="vertical-align: top;" |
|||
! colspan="4"|Unikernel related projects |
|||
|- style="vertical-align: top;" |
|||
! style="font-weight:normal"| '''[https://www.xenproject.org/developers/teams/unikraft.html Unikraft]'''<br> <br>''Skills needed:''<br> Linux/BSD, C, scripting |
|||
! style="font-weight:normal"| [[Outreach Program Projects#Unikraft|Outreach Program Projects]] |
|||
! style="font-weight:normal"| Ask on the list |
|||
! style="font-weight:normal"| [http://lists.xenproject.org/cgi-bin/mailman/listinfo/minios-devel minios-devel@lists.xenproject.org]<br>[http://xenproject.org/help/irc.html IRC]: #unikraft |
|||
|- style="vertical-align: top;" |
|- style="vertical-align: top;" |
||
! style="font-weight:normal"| '''[http://xenproject.org/developers/teams/mirage-os.html Mirage OS]'''<br> <br>''Skills needed:''<br> Linux/BSD, OCaml |
! style="font-weight:normal"| '''[http://xenproject.org/developers/teams/mirage-os.html Mirage OS]'''<br> <br>''Skills needed:''<br> Linux/BSD, OCaml |
||
! style="font-weight:normal"| [http://canopy.mirage.io/ |
! style="font-weight:normal"| [http://canopy.mirage.io/tags/help%20needed MirageOS Pioneer Projects] |
||
! style="font-weight:normal"| Ask on the list |
! style="font-weight:normal"| Ask on the list |
||
! style="font-weight:normal"| [http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel mirageos-devel@lists.xenproject.org]<br>[http://xenproject.org/help/irc.html IRC]: #mirage |
! style="font-weight:normal"| [http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel mirageos-devel@lists.xenproject.org]<br>[http://xenproject.org/help/irc.html IRC]: #mirage |
||
|- style="vertical-align: top;" |
|||
! colspan="4"|Tools related projects |
|||
|- style="vertical-align: top;" |
|- style="vertical-align: top;" |
||
! style="font-weight:normal"| '''Infrastructure & Community''' |
! style="font-weight:normal"| '''Infrastructure & Community''' |
||
! style="font-weight:normal"| [[Outreach Program Projects#Infra and Community|Infra and Community Projects]] |
! style="font-weight:normal"| [[Outreach Program Projects#Infra and Community|Infra and Community Projects]] |
||
! style="font-weight:normal"| These may differ per individual project. Projects that are currently available |
! style="font-weight:normal"| These may differ per individual project. Projects that are currently available cover projects such as improving a code review dashboard, process and tools related work, test and test infrastructure related projects, etc. |
||
* [[Outreach_Program_Projects#Xen_Code_Review_Dashboard|Xen Code Review Dashboard]] requiring SQL, Java/Javascript, HTML5/XML skills. Extend based proof-of-concept code review dashboard and data collection infrastructure for the Xen Project. This will involve adding additional tools to analyse code review messages, add ElasticSearch indexes and possibly add and work with the developer community to add additional widgets and views to the Kibana based graphical dashboard. |
|||
* [[Outreach_Program_Projects#Add_Centos_Virt_SIG_Xen_packages_test_to_the_CentOS_CI_loop|Add Centos Virt SIG Xen packages test to the CentOS CI loop]] |
|||
* [[Outreach_Program_Projects#Code_Standards_Checking_using_clang-format|Code Standards Checking using clang-format]] |
|||
! style="font-weight:normal"| These may differ per individual project. Contact information for projects are: |
! style="font-weight:normal"| These may differ per individual project. Contact information for projects are: |
||
* |
* Mentor and other contact details in the project<br>always CC xen-devel@lists.xenproject.org<br>[http://xenproject.org/help/irc.html IRC]: #xendevel |
||
|- style="vertical-align: top;" |
|- style="vertical-align: top;" |
||
! style="font-weight:normal"| '''[http://xenproject.org/developers/teams/xapi.html XAPI]'''<br> <br>''Skills needed:''<br> Linux/BSD, OCaml |
! style="font-weight:normal"| '''[http://xenproject.org/developers/teams/xapi.html XAPI]'''<br> <br>''Skills needed:''<br> Linux/BSD, OCaml |
||
Line 146: | Line 100: | ||
* Please review general mentor information [https://wiki.gnome.org/Outreachy/Admin/InfoForMentors here] |
* Please review general mentor information [https://wiki.gnome.org/Outreachy/Admin/InfoForMentors here] |
||
* [http://lists.xenproject.org/archives/html/xen-devel/2015-09/msg03386.html Mentor FAQ for Round 11] |
* [http://lists.xenproject.org/archives/html/xen-devel/2015-09/msg03386.html Mentor FAQ for Round 11] |
||
== Mentor Timeline == |
|||
* From February 12: Help interested students with enquiries and tasks such as building the project (e.g. Hypervisor, Mirage OS, Unikraft, ...) from source, on micro tasks. Help students establish a credible plan for the program. |
|||
* March 30: 1st Mentor Meeting to discuss GSoC and Outreachy applications |
|||
* April 6: 2nd Mentor Meeting to discuss GSoC and Outreachy applications |
|||
* April 13: 3rd Mentor Meeting to discuss GSoC and Outreachy applications |
|||
<br> |
|||
= Archive = |
|||
Note that we have not been accepted to GSoC in 2018 |
|||
== Eligibility GSoC == |
|||
The program is open to you, if <i>you are enrolled in or into an accredited institution, including a college, university, undergraduate program, masters program, or PhD program</i>. For more information, see [https://summerofcode.withgoogle.com/terms/student gsoc/student_agreement]. |
|||
== 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 [http://www.xenproject.org/help/mailing-list.html xen-devel@], [http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel mirageos-devel@], ... mailing list depending on the project you choose (check the [[#Community_Reviewed_Project_List|table]] below). Please '''do no contact mentors privately''' - open source is about openness: use the mailing lists and CC the mentor(s) AND community.manager@xenproject.org. |
|||
* Check whether you have all the hardware you need to participate (see [[#Community_Reviewed_Project_List|table]] below). |
|||
* Try to build the project (e.g. Hypervisor, Mirage OS, Unikraft, ...) from source and run it |
|||
* Get yourself a suitable starter project (see [[Internships/Make a Small Contribution]] Requirement and [[#Community_Reviewed_Project_List|table]] below). Although GSoC does nor require a starter project, you will compete with applicants who will do so. |
|||
* Join the [http://xenproject.org/help/irc.html IRC] channel on irc.gnome.org related to the [[#Community_Reviewed_Project_List|table]] below. Please do '''not''' join the channel, ask a question and then leave again without leaving some contact details: you won't see the reply and we wont be able to contact you. |
|||
* 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? == |
|||
Typically the [https://www.outreachy.org] and [https://summerofcode.withgoogle.com/how-it-works/#timeline 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 12 - March 12: Potential participants discuss application ideas with mentoring organizations |
|||
* March 12: Application system opens for GSoC |
|||
* '''March 27: Application deadline for GSoC''' |
|||
* April 23: 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 14: Coding officially begins! |
|||
* June 1: 1st mid-term evaluations |
|||
* July 9 : 2nd mid-term evaluations |
|||
* August 6: End of GSoC program |
|||
[[Category:Community]] |
[[Category:Community]] |
||
Line 151: | Line 152: | ||
[[Category:GSoC]] |
[[Category:GSoC]] |
||
[[Category:Internships]] |
[[Category:Internships]] |
||
[[Category:Archived]] |
Latest revision as of 09:32, 28 January 2020
What is an Internship?
You can find a basic overview of internships here.
What Internship Programs is the Xen Project participating in Summer 2018?
The Xen Project Advisory Board has funding for interns for Outreachy this summer (formerly known as the GNOME Outreach Program) which runs from May 2018 to August 2018. The project will also apply as mentoring organisation for GSoC 2018.
- 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. For more information see 2018 May-August Xen Project approved projects
Information For Applicants
Eligibility Outreachy
The program is open internationally if you identify as a women (cis and trans), trans man, or genderqueer person. Additionally, it's open to residents and nationals of the United States of any gender who are Black/African American, Hispanic/Latin, Native American/American Indian, Alaska Native, Native Hawaiian, or Pacific Islander. Note that exact requirements change slightly from year to year and may be impacted by laws in various regions: for full eligibility requirements see Outreachy/Eligibility.
Before you can apply and see our project list, have you must have completed the Outreachy Eligibility Check! Without having completed it, you cannot see our projects! |
How To Apply to Outreachy
We will update this section, once more information for the next internship application period is available from Outreachy. For more information on Xen Projects see outreachy.org.
Community Reviewed Project List
Xen Project Team | Project List | Small Code Contributions | Contact Information |
---|---|---|---|
Hypervisor, mini-os and other core technology projects | |||
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 |
Unikernel related projects | |||
Unikraft Skills needed: Linux/BSD, C, scripting |
Outreach Program Projects | Ask on the list | minios-devel@lists.xenproject.org IRC: #unikraft |
Mirage OS Skills needed: Linux/BSD, OCaml |
MirageOS Pioneer Projects | Ask on the list | mirageos-devel@lists.xenproject.org IRC: #mirage |
Tools related projects | |||
Infrastructure & Community | Infra and Community Projects | These may differ per individual project. Projects that are currently available cover projects such as improving a code review dashboard, process and tools related work, test and test infrastructure related projects, etc. | 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 GSoC
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
Mentor Timeline
- From February 12: Help interested students with enquiries and tasks such as building the project (e.g. Hypervisor, Mirage OS, Unikraft, ...) from source, on micro tasks. Help students establish a credible plan for the program.
- March 30: 1st Mentor Meeting to discuss GSoC and Outreachy applications
- April 6: 2nd Mentor Meeting to discuss GSoC and Outreachy applications
- April 13: 3rd Mentor Meeting to discuss GSoC and Outreachy applications
Archive
Note that we have not been accepted to GSoC in 2018
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 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) AND community.manager@xenproject.org.
- Check whether you have all the hardware you need to participate (see table below).
- Try to build the project (e.g. Hypervisor, Mirage OS, Unikraft, ...) 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. Please do not join the channel, ask a question and then leave again without leaving some contact details: you won't see the reply and we wont be able to contact you.
- 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 [1] 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 12 - March 12: Potential participants discuss application ideas with mentoring organizations
- March 12: Application system opens for GSoC
- March 27: Application deadline for GSoC
- April 23: 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 14: Coding officially begins!
- June 1: 1st mid-term evaluations
- July 9 : 2nd mid-term evaluations
- August 6: End of GSoC program