Difference between revisions of "Google Summer of Code 2019"
| Line 12: | Line 12: | ||
Great!, we are very glad for your interest in contributing to Software Heritage and we are looking forward to work with you. | Great!, we are very glad for your interest in contributing to Software Heritage and we are looking forward to work with you. | ||
| + | |||
| + | === Before you apply === | ||
Here are the '''steps you should follow before applying''', to make sure you have a good grasp of what and how we are doing at Software Heritage: | Here are the '''steps you should follow before applying''', to make sure you have a good grasp of what and how we are doing at Software Heritage: | ||
| − | # | + | # Follow our [https://docs.softwareheritage.org/devel/getting-started.html 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 [https://forge.softwareheritage.org development forge] |
| − | # | + | # Familiarize yourself with our [[Code review in Phabricator|code review workflow]] |
| − | # | + | # Make a simple change to any one of our [https://docs.softwareheritage.org/devel/ software components] and submit it as a [https://forge.softwareheritage.org/differential/ diff] for code review, following the above workflow. [[Easy hacks]] and [https://forge.softwareheritage.org/project/view/20/ 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: | ||
| + | |||
| + | * '''TODO''' | ||
| + | * a reference to the diff you submitted before applying (see the "Before you apply" section above) | ||
== Ideas list == | == Ideas list == | ||
Revision as of 13:53, 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.
Before you apply
Here are the steps you should follow before applying, to make sure you have a good grasp of what and how we are doing at Software Heritage:
- 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:
- TODO
- 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.