Difference between revisions of "GSoC"

From coreboot
Jump to navigation Jump to search
Line 26: Line 26:
What will be required of you to be a coreboot GSoC student?
What will be required of you to be a coreboot GSoC student?


Google Summer of Code is a full (day)time job. This means we expect roughly 40 hours per week on your project, during the three months of coding. Obviously we have flexibility, but if your schedule (exams, courses) does not give you this amount of spare time, then maybe you should not apply.  
Google Summer of Code is a full (day)time job. This means we expect roughly 40 hours per week on your project, during the three months of coding. Obviously we have flexibility, but if your schedule (exams, courses) does not give you this amount of spare time, then maybe you should not apply. We expect to be able to see this level of effort in student output.


# Prior to project acceptance, you have demonstrated that you can work with the coreboot codebase.  
# Prior to project acceptance, you have demonstrated that you can work with the coreboot codebase.  
Line 35: Line 35:
#* You must have made progress and committed significant code before the mid-term point and by the final.
#* You must have made progress and committed significant code before the mid-term point and by the final.
# We require that accepted students to maintain a blog, where you will write about your project weekly. This is a way to measure progress and for the community at large to be able to help you. SoC is not a private contract between your mentor and you. http://blogs.coreboot.org/
# We require that accepted students to maintain a blog, where you will write about your project weekly. This is a way to measure progress and for the community at large to be able to help you. SoC is not a private contract between your mentor and you. http://blogs.coreboot.org/
# Student must be active on IRC and the mailing list.  
# Student must be active on IRC and the mailing list.
# Students are expected to work on development publicly, and to push commits to the project on a regular basis. We do not want large dumps of code that need to be rushed to meet the mid-term and final goals.


We don't expect our students to be experts in our problem domain, but we don't want you to fail because some basic misunderstanding was in your way of completing the task.
We don't expect our students to be experts in our problem domain, but we don't want you to fail because some basic misunderstanding was in your way of completing the task.

Revision as of 17:43, 1 March 2016