Difference between revisions of "GSoC Student Requirements"
(updated for 2013) |
(language tweaks and clarifications) |
||
| Line 1: | Line 1: | ||
To be able to track student progress during the Summer of Code, we propose that students follow these principles. These are just some broad guidelines - details can always be discussed with your mentor. | To be able to track student progress during the Summer of Code, we propose that students follow these principles. These are just some broad guidelines - details can always be discussed with your mentor. | ||
| + | |||
== Progress Report == | == Progress Report == | ||
| Line 12: | Line 13: | ||
* Where do you think you may be facing a problem or require more time? | * Where do you think you may be facing a problem or require more time? | ||
| − | Whether you send this progress report to your | + | Whether you send this progress report to your mentor or publish it somewhere (e.g. on a blog or on the geeklog-devel mailing list) is up to you and your mentor to decide. |
| + | |||
| + | We would, however, allow the community to get an idea about the progress of your project once in a while, so we would like to ask you to prepare a summary at around the time of the mid-term evaluation and again at the end of the project. We would like to post that summary in the [http://www.geeklog.net/index.php?topic=GSoC "Summer of Code" topic] on geeklog.net. | ||
| − | |||
== Commits == | == Commits == | ||
| − | The Coding Period starts on June 17. From that point on, we would like to see regular commits and a push to your GSoC repository (which will be provided for you) at least once per week. | + | The Coding Period starts on '''June 17'''. From that point on, we would like to see regular commits and a push to your GSoC repository (which will be provided for you) at least once per week (preferably more often). |
| + | |||
== Integration Period == | == Integration Period == | ||
| − | The last two weeks of the Coding Period should be reserved for integration and test (of the integration). At this point, your project should be complete and ready for merging it back into the main development branch. | + | The last two weeks of the Coding Period should be reserved for integration and test (of the integration). '''At this point, your project should be complete and ready for merging it back into the main development branch.''' |
Geeklog has a bi-annual release cycle, with major releases in April and November. We would very much like to see the results of your project make it into the November release. Just think of all the people who will soon use your code <tt>:)</tt> | Geeklog has a bi-annual release cycle, with major releases in April and November. We would very much like to see the results of your project make it into the November release. Just think of all the people who will soon use your code <tt>:)</tt> | ||
| + | |||
== Talk to us == | == Talk to us == | ||
| − | Please remember: When you run into a problem (be it with the project or something personal) - tell us about it. We're here to help you finish your project. But to be able to help you, we need to know that there is a problem first . | + | Please remember: When you run into a problem (be it with the project or something personal) - tell us about it. We're here to help you finish your project. But to be able to help you, we obviously need to know that there is a problem first. So don't be afraid - we'll find a solution. |
[[Category:Summer of Code]] | [[Category:Summer of Code]] | ||
Latest revision as of 08:33, 29 March 2013
To be able to track student progress during the Summer of Code, we propose that students follow these principles. These are just some broad guidelines - details can always be discussed with your mentor.
Progress Report
We expect a weekly progress report. This will help you as much as it will help us, since just sitting down once in a while and thinking about what you did so far and what you plan to do next will help you get a better idea of the progress of your project.
Your progress report should roughly cover:
- What did you achieve over the last week?
- What did not work out as expected and why?
- What are your plans for the coming week?
- Where do you think you may be facing a problem or require more time?
Whether you send this progress report to your mentor or publish it somewhere (e.g. on a blog or on the geeklog-devel mailing list) is up to you and your mentor to decide.
We would, however, allow the community to get an idea about the progress of your project once in a while, so we would like to ask you to prepare a summary at around the time of the mid-term evaluation and again at the end of the project. We would like to post that summary in the "Summer of Code" topic on geeklog.net.
Commits
The Coding Period starts on June 17. From that point on, we would like to see regular commits and a push to your GSoC repository (which will be provided for you) at least once per week (preferably more often).
Integration Period
The last two weeks of the Coding Period should be reserved for integration and test (of the integration). At this point, your project should be complete and ready for merging it back into the main development branch.
Geeklog has a bi-annual release cycle, with major releases in April and November. We would very much like to see the results of your project make it into the November release. Just think of all the people who will soon use your code :)
Talk to us
Please remember: When you run into a problem (be it with the project or something personal) - tell us about it. We're here to help you finish your project. But to be able to help you, we obviously need to know that there is a problem first. So don't be afraid - we'll find a solution.
