GSoC Student Requirements - Revision history

Dirk: language tweaks and clarifications

2013-03-29T08:33:27Z

language tweaks and clarifications

Dirk: updated for 2013

2013-03-20T12:33:29Z

updated for 2013

Dirk: updated for 2012 timeline

2012-02-16T09:08:41Z

updated for 2012 timeline

Dirk: minor update for 2011

2011-02-26T18:56:06Z

minor update for 2011

Dirk: Some GSoC Student Guidelines

2010-03-07T12:26:48Z

Some GSoC Student Guidelines

New page

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 mentors only or publish it somewhere (e.g. on a blog or on the geeklog-devel mailing list) is up to you.

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 May 24. 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.

== Integration Period ==

The last two weeks of the Coding Period (i.e. the first two weeks in August) should be reserved for integration and test. At this point, your project should be mostly complete and you should spend some time syncing with the latest changes in Geeklog's core code, so that your project can make it into the main repository soon thereafter.

Geeklog just switched to 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 ==

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 ...

[[Category:Summer of Code]]

@@ 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.
 == Progress Report ==
@@ Line 12: / Line 13: @@
 * Where do you think you may be facing a problem or require more time?
-Whether you send this progress report to your mentors only 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.
+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.
 == 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 ==
-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>
 == 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]]

@@ Line 12: / Line 12: @@
 * Where do you think you may be facing a problem or require more time?
-Whether you send this progress report to your mentors only or publish it somewhere (e.g. on a blog or on the geeklog-devel mailing list) is up to you.
+Whether you send this progress report to your mentors only 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.
@@ Line 18: / Line 18: @@
 == Commits ==
-The Coding Period starts on May 21. 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.
 == Integration Period ==
-The last two weeks of the Coding Period (i.e. the second & third week in August) should be reserved for integration and test. At this point, your project should be mostly complete and you should spend some time syncing with the latest changes in Geeklog's core code, so that your project can make it into the main repository soon thereafter.
+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>

@@ Line 18: / Line 18: @@
 == Commits ==
-The Coding Period starts on May 23. 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 May 21. 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.
 == Integration Period ==
-The last two weeks of the Coding Period (i.e. the first two weeks in August) should be reserved for integration and test. At this point, your project should be mostly complete and you should spend some time syncing with the latest changes in Geeklog's core code, so that your project can make it into the main repository soon thereafter.
+The last two weeks of the Coding Period (i.e. the second & third week in August) should be reserved for integration and test. At this point, your project should be mostly complete and you should spend some time syncing with the latest changes in Geeklog's core code, so that your project can make it into the main repository soon thereafter.
 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>