The Fedora project represented the Google Summer of Code program for 6 years and willing to participate on year 2012 program as well. This wiki page serves as the GSoC portal. Please feel free to contact us via firstname.lastname@example.org for clarifications/ more info.
- 1 Students
- 2 Administration
- 3 Mentors
- 4 Communication
- 5 Time Line
- 6 Organization Application
- 7 Ideas Page
- 8 Links
Students who are looking for challenges and would like to contribute to the worlds' leading and innovative Linux Distro, this could be the chance. Please feel free to contact and refer to the material and start contacting mentors.
Why spend your summer working on FOSS?
When you work in the open on free software, you create a body of work that follows you for the rest of your life. Rather than a coding assignment done by thousands of other students and relegated to the bottom of the bit drawer at semester's end, working in FOSS is a chance to contribute to a living project.
Working in FOSS gives you a chance to:
- Work with real world large codebases.
- Collaborate with real engineers and other professional experts.
- Contribute to something meaningful while learning and earning student value.
- Learn tools and processes that are just like what you are going to use if you work in technology after graduation.
- Make friends and contacts around the globe.
- Possibly attract attention that gets you an internship or job after graduation.
- Create life time connections.
Why work with Fedora?
Our project is large and diverse. We are very experienced at working with new contributors and helping them be successful.
Many long-time contributors continue to be around, lending expertise and mentoring. People who stay around the community and do good work are noticed. They get hired for jobs from it, including being hired by Red Hat. Past Google Summer of Code students were hired by Red Hat, as well as interns in various positions. This is just an example, as experience and reputation in the Fedora Project communities is influential on your career in many ways.
As long-standing communities with many facets, it is possible for you to find many rewarding sub-projects to work on.
You should know that contributing to FOSS doesn't require you to have super programming skills, or super-anything else. You just need be interested and curious enough, and be willing to become comfortable being productively lost. This is the state of learning through finding your way around and figuring things out.
Step-by-step guide for students
Please check the Step by Step guide for students.
Please use the following application template to apply for the program.
In order to clarify matters/ obtain more info related with the GSoC 2012 with Fedora please contact the administrators directly (please consider CCing the summer-coding list where ever possible).
- Buddhike Kurera(Bckurera) - Administrator
- Karsten Wade(Quaid) - Backup-Admin
- Susmit Shannigrahi(Susmit) - Fall-back Admins
- Mo Duffy (Duffy) - Fall-back Admins
- Mo Morsi - Fall-back Admins
The contributors of the Fedora Project can propose ideas and mentor them. Please feel free to check following links and please add your ideas to the main idea page, further if you are not interested in proposing an idea but still want to support the program please check the students' idea page and pick one as per your interest.
How to work with students
- One way is to provide an idea for students to work on. This idea might be very well planned out, in which case you may need a high-level of contact with the student to get it implemented correctly.
- It is harder to find success where you are completely certain of how an idea needs to be implemented; finding a student with the skills and interest to implement a specific solution is a lot harder than finding a student with enough skills to respond to a use case need.
- Where you can have looser ideas, you may be able to find a student who works as a sort-of intern who can implement a solution to a use case you have. In past experiences, students going after a use case are more likely to get somewhere with self-direction.
- You may also want to work with a student who brings an idea to your sub-project. This requires a different level of communication throughout the project, but can be the most rewarding.
You are an essential part of the student's success, the project's success, and the success for your overall organization (Fedora, JBoss.org, or another).
Your responsibilities include:
- Being an interface for an identified sub-project or SIG in Fedora.
- Helping students communicate with the overall project and any upstreams.
- Be the final, accountable person for deciding if the student is successful or not, which affects payment.
List of Mentors
Please feel free to contact mentors to clarify the related matters.
- Hedayat Vatankhah
- Mo Morsi
- Dennis Gilmore
- Toshio kuratomi
- Kevin Fenzi
- Buddhike Kurera
- Mo Duffy
- Emily Dirsh
- Jkeating (at) fedoraproject (dot) org
- María "tatica"
- Peter Tibor Borsa
- Brendan Jones
- Stanislav Ochotnický
- Tim Niemueller
- Peng Tao
- Tim Flink
List of registered members
List of mentors who are registered with Google and added to the project as a mentor are listed here;
Mailing List (GSOC related) : https://admin.fedoraproject.org/mailman/listinfo/summer-coding
Mailing List (Technical) : http://lists.fedoraproject.org/mailman/listinfo/devel
IRC : Channel - #fedora-devel or #fedora-summer-coding on Freenode
- March 9: Mentoring organization application deadline.
- March 12-15: Google program administrators review organization applications.
- March 16: List of accepted mentoring organizations published on the Google Summer of Code 2012 site.
- March 17-25: Would-be student participants discuss application ideas with mentoring organizations.
- March 26: Student application period opens.
- April 6: Student application deadline.
Interim Period: Mentoring organizations review and rank student proposals; where necessary, mentoring organizations may request further proposal detail from the student applicant.
- April 20: All mentors must be signed up and all student proposals matched with a mentor. Student ranking/scoring deadline.
- April 23: Accepted student proposals announced on the Google Summer of Code 2012 site.
Community Bonding Period: Students get to know mentors, read documentation, get up to speed to begin working on their projects.
- May 21: Students begin coding for their Google Summer of Code projects;
Interim Period: Mentors give students a helping hand and guidance on their projects.
- July 9: Mentors and students can begin submitting mid-term evaluations.
- July 13: Mid-term evaluations deadline;
Google begins issuing mid-term student payments provided passing student survey is on file. Interim Period: Mentors give students a helping hand and guidance on their projects.
- August 13: Suggested 'pencils down' date. Take a week to scrub code, write tests, improve documentation, etc.
- August 20: Mentors, students and organization administrators can begin submitting final evaluations to Google.
- August 24: Final evaluation deadline
- August 27: Final results of Google Summer of Code 2012 announced
- August 31: Students can begin submitting required code samples to Google
- October 20 - 21: Mentor Summit at Google.
Status : Submitted
Link : https://fedoraproject.org/wiki/GSoC_2012_org_application
Status : Open for Ideas
Link : https://fedoraproject.org/wiki/Summer_coding_ideas_for_2012
We encourage students to provide creative yet useful ideas towards the Fedora project as well. Please use Student Idea page to note your idea. The idea will be moved to the original idea page once the idea is picked by a mentor.