This page is aimed as the collection of projects which potential developers could be involved in for the Google Summer of Code project.
Why Source Mage
Most of the Source Mage utilities are written in bash, the defacto shell on GNU/Linux systems. This means that the entrance level is lower than usual and it is a great opportunity for any bash fans to do what they love, help Source Mage and get paid for it.
Proposals
All the current proposals require good knowledge of bash scripting. A recommended, albeit long, read is the Advanced Bash-Scripting Guide.
Your own brilliant proposal
You can post your own proposals on the sm-discuss mailing list, so we can help you shape it, suggest changes and find you a mentor. Other means of communication are possible, but the mailing list is preffered.
All project proposals should contain at least this information:
- project name
- a short explanation
- the expected results
an approximate time frame (keep the GSOC timeline in mind)
- any prerequisites for the completion
- mentor (if you've found one)
Feel free to submit multiple proposals.
Grimoire
Name |
Description |
Result |
Requirements |
Mentors |
Spell linting library |
see #14105 |
an extensive library and if time allows also a git hook and integration in Quill |
Knowledge of bash, regular expressions (grep/sed/awk) |
Arwed von Merkatz, Jaka Kranjc |
Cauldron
Name |
Description |
Result |
Requirements |
Mentors |
Automate Quality Assurance/Testing of ISOs |
Currently, testing of ISOs is not well-automated and the process is largely manual. This will be a challenging project to take on. |
an automated script (or set of scripts) for testing generated ISOs to ensure they work properly |
Knowledge of bash and automated testing |
Justin Boffemmyer |
Automated cross-compilation |
Develop automated cross-compilation to generate ISOs for any given architecture on a single build machine. |
a library implementing scalable, automated cross-compilation of ISO targets |
Knowledge of bash, cross-compilation |
Justin Boffemmyer |
Sorcery
Name |
Description |
Result |
Requirements |
Mentors |
Rewrite of the Sorcery menu system |
see #8429 |
a library implementing a scalable, clean and easy to use menu system (phase 1) and sorcery adapted to use it (phase 2) |
Knowledge of bash |
Andrew Stitt, Jaka Kranjc |
Misc
Name |
Description |
Result |
Requirements |
Mentors |
Scripting support for Quill |
see #13478 |
a generic interface to quill internals. The goal is to be able to predictably automate the use of quill |
Knowledge of bash |
Jaka Kranjc |
Getting accepted
To maximize your chances of being accepted, research your project proposals beforehand, so you will be able to present them better, find issues early and inspire confidence in the (potential) mentors. Initiative, fervor and good communication can greatly improve your chances of getting accepted.
Besides the presentation of the proposal, you should also include some personal information (in no particular order): area of study, prior programming work/experience, prior Source Mage experience, contact information, geographic location (timezone).
Don't forget that other students may submit similar proposals, so try to convince us you are the right person for the job. If you have any other major commitments that can get in the way, please tell us about them and suggests ways to compensate.
The Thousand Parsec GSOC page has a good explanation of the selection criteria.