We are establishing an architecture for schools, corporations, and other organizations with an interest in open source software education to sponsor students to work under the mentoring and guidance of the Fedora Project teams.
Fedora Students Contributing is about connecting sponsors (those with resources to share) with students (those with time, passion, and skills to share.)
Why you should be a sponsor?
What do you get out of it?
- Positively impact FOSS projects.
- Get your brand in front of smart students who want to work on FOSS.
- Potentially end up hiring great developers through the program.
- Work on a community program that demonstrates how open source business is done.
- See something you’d like coded be completed.
- Other positive brand associations.
What you need to do
We need to start talking, soon.
- Open by default on the discuss list - http://lists.fedoraproject.org/mailman/listinfo/summer-coding-discuss
- Private via direct email to project leadership - Karsten Wade, ...
What are the resources you can supply?
- Money to pay stipends to students for spending focused time on these FOSS projects. This is a cross between a summer job and an internship.
- Someone to help coordinate and to contribute as part of the Fedora Summer Coding special interest group (SIG).
- Mentors, especially if they work actively in sub-project or area the sponsor is supporting.
What does the Students Contributing program do?
The Fedora Students Contributing mentors sort the student ideas, generate the list of approved proposals, work with the students throughout the summer, and make sure you hear back about how things went.
It’s not necessary as a sponsor to have ideas of how your resources should be used, that’s what the Fedora Project and JBoss.org mentors and sub-projects are prepared to do.
You can learn more about the model we are using in this blog post, Summer Of Code Swimchart: Now With More Generic.
Timeline for sponsoring organizations
It is still under construction and content may change. Do not rely on the information on this page.
Join the discussion mailing list and/or watch this page to be updated about schedule changes.
Start dates are emphasized and deadlines are in bold emphasis for student items.
For example, if the deadline is 09 August, all work must be in for mentor review by 23:59 UTC on 09 August. You must adjust for your own timezone, meaning the deadline may be at a different time of the day for you locally.
- September
- 20 September - Projects begin posting ideas
- 23 September - Begin publicity to students
- October
- Whole month - students, mentors, and sub-projects get to know each other
- 1 October - Students can begin submitting applications
- 13 October - Mentors need to finish idea pages
- 20 October - Students applications + proposals need to be in
- 21 October - Sponsors must pledge funding by this point
- 24 October - Organizers finalize how many applications will be accepted
- 27 October - Mentors + admins finalize rank-ordered list
- 28 October - Students informed yes/no about application
- 29 October - Collect payment info for selected students
- November
- Whole month - code, interact
- 01 November - Project begins (depending on proposal)
- December
- 05 December - Midterm evaluations period begins
- 05 December - Student midterm deadline for evaluation (first, soft deadline)
- 08 December - Student midterm deadline for evaluation (final deadline)
- 12 December - Midterm evaluations due from mentors
- January
- Whole month - code, interact
- Febuary
- 09 Febuary - Project coding completes
- 16 Febuary - Students final report, code snapshot, and evaluations due
- 20 Febuary - Mentor evaluations due for students
- 23 Febuary - Final evaluations due back to students
- 25 Febuary - Mentor, sub-project evaluations of the Summer Coding program requested
- March
- 01 March - Sponsors receive report from organizers
- 06 March - Sponsors release and deliver funds (proposed date)