Find an idea you like? Want to propose your own? See the GSoC Getting Started Guide.
Students Welcome
If you are a student looking forward to participate the GSoC 2016 with Fedora, please feel free to browse the idea list which is still growing. Do not hesitate to contact the mentors or contributors as indicated in this page for any related clarification. You also should find some like-minded 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. Additionally, please register in the Fedora Account System (FAS) if you are willing to continue with the Fedora Project. For getting quick help, #fedora-devel can be used for getting help with programming problems.
Supporting Mentors
The following contributors are available to provide general help and support for the GSoC 2016 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.
Fedora Atomic Mentors
The following mentors are specifically available for projects related to Fedora Atomic:
- Giuseppe Scriviano
- Colin Walters
- Giuseppe Scrivano
- Matthew Barnes
Idea list for GSoC 2016
Implement Tinykdump
Status: Proposed - draft
Summary of idea: Tinykdump is a minimal daemon to capture kernel-based crash dumping (kdump) memory image to usb storage. Compared to the traditional kdump solution, it is,
* more reliable and scalable * has smaller memory foot-print * more friendly to kernel developers
More information here: https://fedorahosted.org/tinykdump/
Knowledge prerequisite: Python, kernel programming (desired)
Skill level: intermediate (programming)
Contacts: CAI Qian
Mentor(s): CAI Qian
Notes: Rough roadmap:
- Implement tinykdump daemon to be included in Fedora.
- Submit kernel patches for reserving kdump memory at run-time for community review and inclusion.
- Currently, pstore only log kernel messages for panic and Oops. Patches are needed to support logging of kdump kernel and initramfs console output.
Idea list for Fedora Community Operations and Infrastructure
Fedora Infrastructure Web Application Development: Community Operations (CommOps)
| Project | IRC Channel | Web Page | Mentor(s) | Notes |
|---|---|---|---|---|
| Community Operations (CommOps) | #fedora-commops | CommOps Wiki | Remy DeCausemaker (decause) | The rise of DevOps has been swift. Sysadmins are increasingly instrumenting and integrating automated systems to stand up and maintain their infrastructure. This same approach can be taken to support community infrastructure in a distributed and automated fashion, that doesn't force people to choose between using their precious volunteer time to "build things" or "build communities that build things." The community operations team works across numerous technologies, and interest areas in Fedora, including Messaging, Storytelling, Fedora Badges, Fedora Hubs, Wiki, Culture, Metrics, Voting, and other miscellaneous topics. It is important to note that CommOps team members are generalists, and the strengths and interests of individual applicants will determine the precise nature of your work. Enthusiasm for FOSS culture and community organization, and effective communication skills are most important. Specific deliverables can include automated metrics gathering, real-time messaging integration with Fedora hubs, and other big-data analysis and visualization. Tools are primarily written in python, and utilize libraries such as fedmsg, numpy, pandas, pygals, flask, sqlalchemy. We also leverage other web technologies like HTML5 and Javascript, and frameworks such as bootstrap and handlebars to deliver these metrics.
Your internship with this project could also involve any or all of the following:
Required:
Bonus Skills:
|
Fedora Infrastructure Web Application Development: Fedora Hubs
| Fedora Infrastructure Web Application Development: Fedora Hubs | #fedora-hubs |
|
Fedora has been in the process of creating a new web presence for all of the Fedora users, subprojects, and communities. We also plan to integrate some of the features of this system with the prototype of the Fedora Developer Portal, which is targeted at helping general developers use Fedora. While the Hubs project itself is aimed at Fedora contributor circles, the reusable features will allow the Portal to use this work to speak to general developers who may not have an interest in working in the Fedora community, but want to connect with community members for advice, best practices, or to generate interest in their upstream project. Several of the principal app developers in the Fedora Engineering team will be working together with you on this project during the Outreachy term. You'll participate directly with team members daily on core features of Hubs as well as integration with the Portal. This is a great opportunity both for regular mentorship and for being deeply involved in an exciting and fast-moving project with the Fedora team. Working on this project could involve any of the following:
Skills:
When applying to this project, it may be useful to review the designers' blogs about the projects' design here: Fedora Developer Portal Fedora Hubs A video overview of the Hubs project is available here: http://blog.linuxgrrl.com/2015/07/01/fedora-hubs-update/ |
Fedora Infrastructure Web Application Development: Pagure
| Project | IRC Channel | Web Page | Mentor(s) | Notes |
|---|---|---|---|---|
| Pagure | #fedora-apps | Pagure project | Pierre-Yves Chibon (pingou) | Pagure is a forge written in python and offering the possibility of self-hosting projects while still using the now well-know fork and pull-request contribution model. While being similar to other forge such as GitHub or GitLab it is also pretty different for example it does not namespace projects under usernames with the idea that projects should not belong to a single person but to a community.
Your internship with this project could also involve any or all of the following:
Required:
Bonus Skills:
|
Idea list for Fedora Atomic GSoC 2016
This idea list comes from the Project Atomic website. The most up-to-date version is there.
Next-generation Super Privileged Container
https://github.com/projectatomic/atomic/issues/298
| Project | IRC Channel | Web Page | Mentor(s) | Notes | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Fedora Atomic | #atomic | ProjectAtomic.io |
|
Description
Difficulty: Advanced Required skills: C, Python, and likely Golang Mentor: Colin Walters, Giuseppe Scrivano Expected outcomes
Atomic Host package layering
Bootstrap with gpgcheck in kickstart
Improve ability to monitor running/canceled transactions
Support for end-of-life notification
rpm-ostree operation history support
Support Metalink for OSTree
Drop privileges for HTTP fetches
Support kpatch
Open Ideas From GSoC 2015In 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.
|