Google's Summer of Code - Guidelines
Following guidelines should be followed when mentoring student under Google’s Summer of Code program.
Any other issues not described on this page should be handled with mentor.
Weekly Reports
In order to keep track of progress of student’s work, weekly reports are required from the student. Weekly reports are used as administrative information to keep track of all students. If there is a pressing matter that weekly report cannot be done on time, it should be notified before hand to mentors.
Weekly reports shall contain following information:
- What was done during the week
- Were there any problems
- What was the solution for problems
- What is planned to be done on next week
At the end of week student should also prepare tarball and patch against CVS HEAD of GRUB 2 repository. Timestamp of CVS HEAD for patch should be within week. Patch should be unified diff displaying function names (-pruN).
It should be noted that if student faces a problem, he/she should contact other developers in grub-devel mailing list or mentor directly to resolve problems as soon as possible.
Integrating Students Changes
No changes related to student’s work should be integrated to repository before GSoC project has been ended. In meanwhile user can use his/her own version control system to keep track on changes. This is to keep it clear what is students modifications and what is not. Google is also requiring that student provides at the end of program code to Google Code website.
Student may also present patches to public during the program. This can be useful to test out the code with more users.