Difference between revisions of "Google Summer of Code 2019"
| Line 36: | Line 36: | ||
* which '''specific project''' do you want to work on? It might be one of the project ideas that we have prepared… or something else you want to contribute to Software Heritage: your source code archival pet peeve, surprise us! | * which '''specific project''' do you want to work on? It might be one of the project ideas that we have prepared… or something else you want to contribute to Software Heritage: your source code archival pet peeve, surprise us! | ||
* your '''work plan''': a brief description of how you plan to go about your project, including a list of ''deliverables'' and a ''timeline'' of when do you expect them to be available | * your '''work plan''': a brief description of how you plan to go about your project, including a list of ''deliverables'' and a ''timeline'' of when do you expect them to be available | ||
| − | * a reference to the diff you submitted before applying (see the "Before you apply" section above) | + | * a reference to '''the diff''' you submitted before applying (see the "Before you apply" section above) |
== Ideas list == | == Ideas list == | ||
Revision as of 17:00, 3 February 2019
WORK IN PROGRESS !!!
General information
This page is the central point of information for Software Heritage participation into the Google Summer of Code program.
Google Summer of Code is a program where Google pays students stipends to work over the (northern hemisphere) summer on free software projects such as Software Heritage. Each student works with mentors from the community to complete a software project.
I want to participate as a student
Great!, we are very glad for your interest in contributing to Software Heritage and we are looking forward to work with you.
Prerequisites
The following prerequisites apply to Software Heritage GSoC projects:
- Python is our language of choice, you should be fluent with that language to apply - Git is our version control system of choice, you should be familiar with it to apply - additional prerequisites depend on the project you will work on; check project descriptions for details
Before you apply
Here are the steps you should follow before applying, to make sure you have a good grasp of what we are doing at Software Heritage and how we do it:
- Follow our getting started guide: it will make sure you can locally run a (small) copy of the archive and ingest source code into it
- Create an account our development forge
- Familiarize yourself with our code review workflow
- Make a simple change to any one of our software components and submit it as a diff for code review, following the above workflow. Easy hacks and Web UI issues are good options for what to fix, but feel free to submit any patch you think it might be useful.
What to include in your application
Make sure that your application includes the following information:
- which specific project do you want to work on? It might be one of the project ideas that we have prepared… or something else you want to contribute to Software Heritage: your source code archival pet peeve, surprise us!
- your work plan: a brief description of how you plan to go about your project, including a list of deliverables and a timeline of when do you expect them to be available
- a reference to the diff you submitted before applying (see the "Before you apply" section above)
Ideas list
Increase archive coverage
Mine information from archived content
Improve and extend the archive Web UI
Contact
GSoC students are encouraged to get in touch with the Software Heritage community using the standard development communication channels, i.e.:
- the #swh-devel IRC channel on Freenode
- the swh-devel mailing list
See our development information page for more details.
Timeline
See the official Google Summer of Code timeline.