From Fedora Project Wiki
(+2017)
 
Line 3: Line 3:
 
April 03: 16:00 UTC Student application Deadline
 
April 03: 16:00 UTC Student application Deadline
 
</pre>
 
</pre>
The timeline is decided and published by Google, track it at [https://developers.google.com/open-source/gsoc/timeline the official page].
+
 
 +
This timeline is decided and published by Google, see the full timeline on [https://developers.google.com/open-source/gsoc/timeline the official page].
 +
 
 
-------
 
-------
Following are specific guidelines for the students to follow, who are interested in submitting an application for the GSoC program through the Fedora Project. Please go through carefully and follow them. Incomplete applications will not be entertained after the deadline.
+
The following are specific guidelines for students to use to submit an application for the GSoC program through the Fedora Project.
 +
Please go through these carefully and follow them. Applications must be complete by the deadline listed above.  Late applications cannot be accepted.
 
-------
 
-------
  
 +
= Student Application Process =
 +
 +
== Learn ==
 +
 +
Before you do anything, learn about the program and Fedora.  These links may be helpful:
 +
 +
* [https://summerofcode.withgoogle.com/ GSoC official site]
 +
* [https://developers.google.com/open-source/gsoc/faq GSoC 2016 FAQs]
 +
* [[Foundations|The Four Foundations of Fedora]]
 +
* [[GSOC_2017|General GSoC Guidance]]
 +
* [[Mailing_list_guidelines|Mailing List Guidelines]]
 +
 +
== Communicate ==
 +
 +
Begin [[Communicating and getting help|communicating]] with the community.  Our community members can help you understand the existing project proposals.  If you're going to try and propose your own project, this is a great way to understand the needs of the project and find a mentor. 
 +
 +
* [http://lists.fedoraproject.org/mailman/listinfo/summer-coding the summer-coding list]
 +
* [http://lists.fedoraproject.org/mailman/listinfo/devel the development list].
 +
 +
Don't forget to contact mentors on projects that interest you to learn more.  If you're going to propose a project you must have a mentor at the time of proposal.
 +
 +
== Apply ==
 +
 +
The application for students is split into three main parts.  All parts need to be completed by the due date.
 +
 +
1. Google Summer of Code Application
  
'''''Process
+
2. Supplemental Application Materials on the Fedora Project Wiki
  
Following criterion should be fulfilled on or before the application deadline unless otherwise specifically noted.
+
3. Additional Fedora Requirements
  
*Create a FAS account  [https://admin.fedoraproject.org/accounts FAS Account Signup / Login Page ]
+
=== Google Summer of Code Application ===
  
*Join with fedora-summer-coding mailing list  [https://lists.fedoraproject.org/admin/lists/summer-coding Fedora Summer Coding Mailing List]
+
Submit the application/proposal at the [https://summerofcode.withgoogle.com/get-started/ Google Summer of Code Site]  
  
*Join with devel mailing list [https://admin.fedoraproject.org/mailman/devel Devel Mailing List]
+
=== Supplemental Application Materials on the Fedora Project Wiki ===
  
*Chose a project for proposal from [https://fedoraproject.org/wiki/Summer_coding_ideas_for_2017 Summer_coding_ideas_for_2017]
+
Chose a project for proposal from [https://fedoraproject.org/wiki/Summer_coding_ideas_for_2017 Summer_coding_ideas_for_2017].  While it is possible to propose your own project, it is often more successful for you to select one that is already proposed by a mentor.
  
*Submit application/proposal on Google-Melange [https://summerofcode.withgoogle.com/get-started/ Google Melange Submission Page]
+
Create a new wiki page to hold your application.  The url should look like <code>https://fedoraproject.org/wiki/GSOC_2017/Student_Application_Yourusername</code>, replacing <code>Yourusername</code> with your actual Fedora Account System username.
  
 +
You should include the information that is relevant to the project your are selecting or proposing as well as information about you, your background, etc.  The following format provides some guidance:
  
'''''What to write about in your proposal / application.''
+
* Contact Information
 +
** List your Name, Email Address, Blog URL, and any additional contact information you think we need.  We tend to email so be sure you're reading your email.
 +
* About You - Consider these questions
 +
** Do you have any past involvement with the Fedora Project or another open-source project as a contributor? What kind of contributions have you made (code and non-code)?  Please share any public contributions you have made (urls, etc.)
 +
** Have you participated in GSoC in the past? If so, what year(s) and which organization(s)?
 +
** What motivates you?
 +
** Briefly describe how you organize your work.
 +
* Why Us? - Consider these questions
 +
** Why do you want to work with the Fedora Project?
 +
** Do you plan to continue contributing to the Fedora Project after GSoC? If yes, what sub-project(s) are you interested with?
 +
* Why This Project? - Consider these questions
 +
** Which specific project interests you?  If you are proposing your own project, do it here.  If you are proposing the project, explain why it benefits the community.
 +
** Have you contacted the mentor(s) listed for the project?
 +
** What relevant experience do you have for this project?
 +
** What do you want to gain from this project?
 +
** Describe this project in your own words.  What does it mean to you?  What do you think the final deliverable is?
 +
* Why should we choose you over other applicants?
 +
* Propose a rough schedule for this project.  Ideally you will have regular deliverables throughout the entire period.
 +
* What are you specific plans from May to September (eg: Exams in university, internships, vacations..etc).  We need to know if there are periods of time where you are likely to be unavailable.  We are better at accommodating these periods if we know of them in advance.
  
*Details on your previous FOSS contributions (if any).
+
=== Additional Fedora Requirements ===
  
*A detailed plan with your planned activities in May to September (eg: Exams in university, internships, vacations..etc)
+
Students need to do the following as part of the application process:
  
* Bare mind - Remember to contact your mentor before you submit the application.  
+
* Create a FAS account  [https://admin.fedoraproject.org/accounts FAS Account Signup / Login Page ]
  
 +
* On the project wiki https://fedoraproject.org/wiki, create a user page.  Do this by opening a new web browser tab and going to <code>https://fedoraproject.org/wiki/User:Yourusername</code>, replacing <code>Yourusername</code> with your actual Fedora Account System username.
 +
** This [[Template:Userpage|user page template]] provides a basic layout that you can copy. You can also look at the markup for other users' pages. Here's a selection of some nice user pages:
 +
*** [[User:Jsimon]]
 +
*** [[User:Ianweller]]
 +
*** [[User:Pfrields]]
 +
*** [[User:Kaio]]
 +
** Do not forget to add the Summer coding <year> category to your page, for example for 2017: <code><nowiki>[[category:Summer coding 2017]]</nowiki></code>
 +
** When you save the page, remember to click 'watch this page' at the top.
 +
* Join the fedora-summer-coding mailing list  [https://lists.fedoraproject.org/admin/lists/summer-coding Fedora Summer Coding Mailing List] - This list is fairly low volume.
 +
* Join the devel mailing list [https://admin.fedoraproject.org/mailman/devel Devel Mailing List] - this list can be higher volume you may wish to use mail filters appropriately.
  
''Mentors are more likely to accommodate summer travel if they know in advance''
+
==Let others know==
 +
Let others know about your submission by forwarding your application URL with a brief description about your proposal to the {{fplist|summer-coding}} mailing list.
  
 +
==Keep communicating==
  
 +
We cannot overstress the importance of communication.  Keep talking, and listening, to the discussion group, to the sub-projects relevant to your proposal and to potential mentors.  Be patient, as mentors and other contributors are often very busy people.
  
We '''''DO NOT''''' accept any document after Google student application deadline, all entries make after the deadline is ignored unless you have not informed to Org Admins! However if you have any difficulty to meet this requirement please let us know in advance (before the deadline).
+
== Need Help? ==
  
'''''FAQ
+
If you need help, use the methods described at [[GSOC_2017#Communication]].
  
What is the need of a detailed plan of my activities?
+
You also find this example application helpful: [[GSOC_2012/Student_Application_Bckurera]]
It is important to get an idea about your free time and arrange things at the early stage. Therefore this is really important and try to make it accurate as much as possible.
 

Revision as of 20:34, 9 February 2017

March 20: 16:00 UTC Student application period opens
April 03: 16:00 UTC Student application Deadline

This timeline is decided and published by Google, see the full timeline on the official page.


The following are specific guidelines for students to use to submit an application for the GSoC program through the Fedora Project. Please go through these carefully and follow them. Applications must be complete by the deadline listed above. Late applications cannot be accepted.


Student Application Process

Learn

Before you do anything, learn about the program and Fedora. These links may be helpful:

Communicate

Begin communicating with the community. Our community members can help you understand the existing project proposals. If you're going to try and propose your own project, this is a great way to understand the needs of the project and find a mentor.

Don't forget to contact mentors on projects that interest you to learn more. If you're going to propose a project you must have a mentor at the time of proposal.

Apply

The application for students is split into three main parts. All parts need to be completed by the due date.

1. Google Summer of Code Application

2. Supplemental Application Materials on the Fedora Project Wiki

3. Additional Fedora Requirements

Google Summer of Code Application

Submit the application/proposal at the Google Summer of Code Site

Supplemental Application Materials on the Fedora Project Wiki

Chose a project for proposal from Summer_coding_ideas_for_2017. While it is possible to propose your own project, it is often more successful for you to select one that is already proposed by a mentor.

Create a new wiki page to hold your application. The url should look like https://fedoraproject.org/wiki/GSOC_2017/Student_Application_Yourusername, replacing Yourusername with your actual Fedora Account System username.

You should include the information that is relevant to the project your are selecting or proposing as well as information about you, your background, etc. The following format provides some guidance:

  • Contact Information
    • List your Name, Email Address, Blog URL, and any additional contact information you think we need. We tend to email so be sure you're reading your email.
  • About You - Consider these questions
    • Do you have any past involvement with the Fedora Project or another open-source project as a contributor? What kind of contributions have you made (code and non-code)? Please share any public contributions you have made (urls, etc.)
    • Have you participated in GSoC in the past? If so, what year(s) and which organization(s)?
    • What motivates you?
    • Briefly describe how you organize your work.
  • Why Us? - Consider these questions
    • Why do you want to work with the Fedora Project?
    • Do you plan to continue contributing to the Fedora Project after GSoC? If yes, what sub-project(s) are you interested with?
  • Why This Project? - Consider these questions
    • Which specific project interests you? If you are proposing your own project, do it here. If you are proposing the project, explain why it benefits the community.
    • Have you contacted the mentor(s) listed for the project?
    • What relevant experience do you have for this project?
    • What do you want to gain from this project?
    • Describe this project in your own words. What does it mean to you? What do you think the final deliverable is?
  • Why should we choose you over other applicants?
  • Propose a rough schedule for this project. Ideally you will have regular deliverables throughout the entire period.
  • What are you specific plans from May to September (eg: Exams in university, internships, vacations..etc). We need to know if there are periods of time where you are likely to be unavailable. We are better at accommodating these periods if we know of them in advance.

Additional Fedora Requirements

Students need to do the following as part of the application process:

Let others know

Let others know about your submission by forwarding your application URL with a brief description about your proposal to the summer-coding mailing list.

Keep communicating

We cannot overstress the importance of communication. Keep talking, and listening, to the discussion group, to the sub-projects relevant to your proposal and to potential mentors. Be patient, as mentors and other contributors are often very busy people.

Need Help?

If you need help, use the methods described at GSOC_2017#Communication.

You also find this example application helpful: GSOC_2012/Student_Application_Bckurera