Find an idea you like? Want to propose your own? See the student application process.
If you are a student looking forward to participate the GSoC 2017 with Fedora, please feel free to browse this idea list which is still growing. Do not hesitate to contact the mentors or contributors listed on this page for any questions or clarification. You can find people on the
#fedora-summer-coding IRC channel.
If you are new to the Fedora Project, the following material will help you to get started. You should also follow the student application process
#fedora-devel can be used for getting help with programming problems.
The following contributors are available to provide general help and support for the GSoC 2017 program (existing contributors, feel free to add yourselves and your wiki page). If a specific project mentor is busy, you can contact one of the people below for short-term help on your project or task.
- Brian (bex) Exelbierd (Fedora Community Action and Impact Coordinator, FCAIC, 🎂, containers, general development, general Linux)
- Radka (rhea) Janek (C#, webserver or dotnet related stuff on linux, general support)
- Justin W. Flory (General development, general Linux, Fedora community, GSoC alumnus, questions about program, misc. advice)
- Corey Sheldon (Python, 2Factor/Multi-Factor Auth, QA Testing, general mentoring,2nd year as a mentor, security)
Draft of an idea
Please add your idea using the following template. The template contains examples and questions that should be answered.
|Status||Proposed - draft (use this)|
|Skill level||Are the required skills below something a beginner would no or could reasonably learn quickly? Is there an area where knowledge is already expected making this an advanced project? Also consider how much knowledge about Fedora is required.|
|Skills required||Programming languages or other skills that the student should already posess. Keep in mind that students come to both practice thieir existing skills and grow. Scope your tasks for someone to be able to apply and learn during the project, therefore you shouldn't list everything required to complete the task.|
|Mentor(s)||DotNet SIG - Radka (rhea) Janek, ... //If your SIG is taking the responsibility, specify as in this example (and always link to people or groups)|
|Contacts (IRC & email)||example-list //Mentors email or mailing list of your SIG.&|
|Notes & references||...|
Support for end-of-life notification
|Project||IRC Channel||Web Page||Mentor(s)||Notes|
|Fedora Atomic||#atomic||ProjectAtomic.io||Josh Berkus (jberkus)||Description
Libraries and Software:
Idea list for GSoC 2017
Open Ideas From GSoC 2016
In addition to the above list of ideas, you may want to check out ideas from previous years and contact the mentors for those projects to see if they're still interested in mentoring someone this year.
Note: Do not submit a proposal for an idea from a previous year without contacting the mentor to ensure they will be available to mentor you. Without a mentor, proposals will be rejected.