(added initial ideas list from Project Atomic) |
(Update mentors, English syntax clean-up, other minor changes) |
||
Line 5: | Line 5: | ||
== Students Welcome == | == 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 <code>#fedora-summer-coding</code> IRC channel. | |||
If you are | If you are new to the Fedora Project, the following material will help you to get started. Additionally, please register in the [[FAS|Fedora Account System (FAS)]] if you are willing to continue with the Fedora Project. For getting quick help, <code>#fedora-devel</code> can be used for getting help with programming problems. | ||
# [[Foundations|The Four Foundations of Fedora]] | |||
# [https://developers.google.com/open-source/gsoc/resources/ Official GSoC Resources] | |||
# [http://docs.fedoraproject.org/en-US/index.html Fedora Documentation] | |||
# [http://docs.fedoraproject.org/en-US/index.html Fedora Documentation | # [[Communicate/IRCHowTo|IRC]] | ||
# [[Communicate/IRCHowTo| | # [[Development|Development]] | ||
# [[ | |||
== Supporting Mentors == | == 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. | |||
# [[User:Decause|Remy DeCausemaker]] | |||
# [[User:Kushal|Kushal Das]] | |||
# [[User:Hguemar|Haïkel Guémar]] | |||
# [[User:Jberkus|Josh Berkus]] | |||
# [[User:Lmacken|Luke Macken]] | |||
=== Fedora Atomic Mentors === | |||
The following mentors are specifically available for projects related to [http://www.projectatomic.io/community/gsoc Fedora Atomic]: | |||
# Giuseppe Scriviano | |||
# [[User:Walters|Colin Walters]] | |||
# [[User:Mbarnes|Matthew Barnes]] | |||
==Draft of an idea== | == Draft of an idea == | ||
Please add your idea as follows. | Please add your idea as follows. | ||
=== Project | === Project Name === | ||
''Status | ''Status'': | ||
''Summary of idea | ''Summary of idea'': | ||
''Knowledge prerequisite | ''Knowledge prerequisite'': | ||
''Skill level | ''Skill level'': | ||
''Contacts | ''Contacts'': | ||
''Mentor(s) | ''Mentor(s)'': | ||
''Notes | ''Notes'': | ||
== Idea list for GSoC 2016 == | == Idea list for GSoC 2016 == | ||
Line 55: | Line 57: | ||
=== Implement Tinykdump === | === Implement Tinykdump === | ||
''Status | ''Status'': Proposed - draft | ||
''Summary of idea | ''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 | * more reliable and scalable | ||
Line 65: | Line 67: | ||
More information here: https://fedorahosted.org/tinykdump/ | More information here: https://fedorahosted.org/tinykdump/ | ||
''Knowledge prerequisite | ''Knowledge prerequisite'': Python, kernel programming (desired) | ||
''Skill level | ''Skill level'': intermediate (programming) | ||
''Contacts | ''Contacts'': [[User:caiqian|CAI Qian]] | ||
''Mentor(s) | ''Mentor(s)'': [[User:caiqian|CAI Qian]] | ||
''Notes | ''Notes'': | ||
Rough roadmap: | Rough roadmap: | ||
* Implement tinykdump daemon to be included in Fedora. | * Implement tinykdump daemon to be included in Fedora. | ||
Line 79: | Line 81: | ||
* Currently, pstore only log kernel messages for panic and Oops. Patches are needed to support logging of kdump kernel and initramfs console output. | * 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 Atomic == | == Idea list for Fedora Atomic GSoC 2016 == | ||
This idea list comes from the [http://www.projectatomic.io/community/gsoc Project Atomic | This idea list comes from the [http://www.projectatomic.io/community/gsoc Project Atomic] website. The most up-to-date version is there. | ||
* [https://github.com/projectatomic/rpm-ostree/issues/190 Bootstrap with gpgcheck in kickstart]: Add a way for importing a GPG key from the kickstart `ostreesetup` command before the download starts. [https://docs.fedoraproject.org/en-US/Fedora/23/html/Installation_Guide/appe-kickstart-syntax-reference.html "ostreesetup" is described here] | * [https://github.com/projectatomic/rpm-ostree/issues/190 Bootstrap with gpgcheck in kickstart]: Add a way for importing a GPG key from the kickstart `ostreesetup` command before the download starts. [https://docs.fedoraproject.org/en-US/Fedora/23/html/Installation_Guide/appe-kickstart-syntax-reference.html "ostreesetup" is described here] | ||
Line 98: | Line 100: | ||
* [https://github.com/projectatomic/rpm-ostree/issues/118 Support kpatch]: Support live update for the kernel without rebooting or restarting any processes. | * [https://github.com/projectatomic/rpm-ostree/issues/118 Support kpatch]: Support live update for the kernel without rebooting or restarting any processes. | ||
== Open Ideas From GSoC 2015 == | == Open Ideas From GSoC 2015 == | ||
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. | |||
Previous years: | Previous years: | ||
Line 113: | Line 115: | ||
* [[Summer_coding_ideas_for_2008|2008]] | * [[Summer_coding_ideas_for_2008|2008]] | ||
''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. | |||
[[Category:Summer coding]] | [[Category:Summer coding]] | ||
[[Category:Summer coding 2016]] | [[Category:Summer coding 2016]] |
Revision as of 03:56, 19 February 2016
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
- Matthew Barnes
Draft of an idea
Please add your idea as follows.
Project Name
Status:
Summary of idea:
Knowledge prerequisite:
Skill level:
Contacts:
Mentor(s):
Notes:
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 Atomic GSoC 2016
This idea list comes from the Project Atomic website. The most up-to-date version is there.
- Bootstrap with gpgcheck in kickstart: Add a way for importing a GPG key from the kickstart
ostreesetup
command before the download starts. "ostreesetup" is described here
- Improve ability to monitor running/canceled transactions: The rpm-ostree client termination doesn't block the command execution on the rpm-ostreed. This will cause new rpm-ostree clients to fail immediately because there is a transaction in progress. Change rpm-ostree to be notified of the status of the current transaction and possibly attach to it.
- Support for end-of-life notification: Add support for having an
end-of-life
notification to inform users if a particular branch is not supported anymore.
- rpm-ostree operation history support: Add support for
atomic history
to display the transactions history. It should work in a similar way toyum history
.
- Automatic updates: Implement a service that automatically upgrades the system when a new image is available. If the system is not restarting correctly, then rolblack to the previous working version. More details here:
- Support metalink for OSTree: Add support for metalink files and support downloads from a list of mirrors and fetch objects from multiple sources.
- Drop privileges for HTTP fetches: The HTTP fetcher code is running in the same process of OSTree. Move the HTTP fetcher code to another process with less privileges than the main process.
- Support kpatch: Support live update for the kernel without rebooting or restarting any processes.
Open Ideas From GSoC 2015
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.
Previous years:
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.