Difference between revisions of "GSoC"

From coreboot
Jump to: navigation, search
(3 intermediate revisions by one user not shown)
Line 1: Line 1:
= Google Summer of Code 2012 =
+
__FORCETOC__
  
Welcome to the [http://www.google-melange.com/gsoc/homepage/google/gsoc2012 Google Summer of Code 2012] page of the [[Welcome to coreboot|coreboot project]].
+
= Google Summer of Code 2013 =
  
The coreboot project also hosts payload and flashrom projects.
+
Welcome to the coreboot's [http://www.google-melange.com/gsoc/homepage/google/gsoc2013 Google Summer of Code 2013] page.
<br /><br />
+
  
== Deadlines ==
 
'''DEADLINE FOR STUDENT APPLICATIONS:''' Students who are interested in working on a coreboot-related GSoC project must apply between '''March 26, 2012''' and '''April 6, 2012'''! If you want to apply, please get in contact with us right away, not just when you send your application!
 
  
Make sure you check the official [http://google-melange.appspot.com/gsoc/events/google/gsoc2012 GSoC 2012 timeline].
+
We are preparing to apply for GSoC 2013. Please continue to add you ideas to the [[Project Ideas|projects page]].  
<br /><br />
+
  
= Why work for coreboot =
 
  
Why would you like to work for coreboot?
+
If you have questions, comments, or concerns, please send them to the [[Mailinglist|mailing list]] or join us in [[IRC]].
  
* coreboot offers you the opportunity to work with modern technology "right on the iron".
 
* Your application will be available to users worldwide and promoted along with all other coreboot projects.
 
* We are a very passionate team - so you will interact directly with the project initiators and project leaders.
 
* We have a large, helpful community. Over 100 experts in hardware and firmware lurk on our mailing list, many of them waiting to help you.
 
<br /><br />
 
 
== Some Caveats ==
 
 
* Google Summer-of-Code is a a full (day-) time job. This means we expect roughly 30-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.
 
* Getting paid by Google requires that you meet certain milestones. First, you must be in good standing with the community before the official start of the program. We suggest you post some design emails to the mailing list, and get feedback on them, both before applying, and during the "community bonding period" between acceptance and official start. Also, you must have made progress and committed significant code before the mid-term point.
 
* We require accepted students to have a blog, where you will write about your project on a regular basis. This is so that the community at large can be involved and help you. SoC is not a private contract between your mentor and you. http://blogs.coreboot.org/
 
  
Note that "regular basis" in the last item does _not_ mean "3 days before evaluation deadlines". You should be "around" all the time (reporting your feedback, sending in partial successes, discussing problems in IRC).
+
The coreboot project may also host payload and [http://flashrom.org/GSoC flashrom] projects.
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.
+
 
<br /><br />
 
<br /><br />
  
 +
[[Previous GSoC Projects|Previous coreboot GSoC projects]]
  
== Student requirements ==
+
= Call for Mentors and Project Ideas =
 +
Google has announced the 2013 GSoC program. coreboot had been a GSoC participant in the past, but was not accepted in 2012 and we would like to change that this year. The GSoC project acceptance has become much more competitive and the project ideas and student recruitment pages has become key in getting accepted.  Our project ideas were not flushed out enough in the application process and we didn't have a complete mentors list/assignment for those projects.
  
We will only accept your proposal if you have demonstrated that you can work with our codebase. For that, you have to send a patch to the list which is acceptable. Just ask for simple tasks on the mailing list or on IRC.
+
I think that coreboot has some extremely talented people involved in the project and students should be attracted to the experience of working with our mentors as much as the potential projects.  
<br /><br />
+
  
= Contact =
 
  
If you are interested in becoming a GSoC student, please contact the coreboot mailing list or visit our IRC channel on irc.freenode.net: #coreboot
+
What we need to apply for GSoC 2013:
  
If you need to contact someone directly, [mailto:marcj303@gmail.com Marc Jones] is the GSoC admin for coreboot.
+
Project Admins - We need a person or two to be the main liaison between coreboot and GSoC. This person(s) register the project, fills out the application, leads and organizes the projects and mentors.
<br /><br />
+
  
== coreboot GSoC Mentors ==
+
Mentors - We need a pool of mentors willing to support students on a number of levels; Helping them from the very beginning with project ideas and writing their applications, project and development time management, research, communication, documentation, drive deadlines.  
Please add you name to this list and follow the coreboot mentor link to [http://www.google-melange.com/gsoc/profile/mentor/google/gsoc2012?org=coreboot apply to be a coreboot mentor]
+
  
* [[User:Stepan|Stefan Reinauer]]
+
Mentor biographies - To improve out GSoC recruitment, i would like to have a one paragraph biography for each of our mentors. It should contain what your coreboot experience and contributions. Something about your work and/or education experience and maybe some other personal information. Maybe where you are located. It helps to have mentors can be matched with the students culture. 
* [[User:MJones|Marc Jones]]
+
* [[User:Jason Wang|QingPei Wang]]
+
<br /><br />
+
  
= Possible ideas =
+
Project ideas - We also need complete project ideas with pointers to background data and what the expected outcome would be. We need a list of potential mentors for each project idea.
== coreboot ==
+
  
Please look at our [[Project Ideas|project ideas page]].
+
coreboot GSoC support roles - Even if you can't commit to being a full time mentor, we could use your help with the coreboot promotion, student recruitment, wiki, project ideas, blog postings,  and code reviews , and encouragement and advice to students and mentors.  
<br /><br />
+
  
== flashrom ==
+
Important dates:
 
+
March18 - 29 - Org applications. We should have a list of mentors and suitable project ideas, policies, etc by this date.  
The flashrom project is somewhat independent of coreboot and has its own website and wiki. You can find project ideas for flashrom [http://www.flashrom.org/GSoC here].
+
April 1 - 5-  GSoC application review
<br /><br />
+
April 8 - Org acceptance
 
+
April 22 - May 5 - student applications
== Your own Project Ideas ==
+
 
+
We have come up with some ideas for cool Summer of Code projects. These are projects that we think can be managed in the short period of GSoC, and they cover areas where coreboot is trying to reach new users and new use cases.
+
 
+
But of course your application does not need to be based on any of the ideas listed below. The opposite: Maybe you have a great idea that we just didn't think of yet. Please let us know!
+
 
+
Feel free to contact us at the email address or IRC channel above, and don't hesitate to suggest whatever you have in mind.
+
<br /><br />
+
 
+
== Previous Summer of Code projects ==
+
 
+
We successfully participated in Google's Summer of Code in 2007, 2008, 2009, 2010 and 2011. See our [[Previous GSoC Projects|list of previous GSoC projects]] or [http://code.google.com/soc/ Google's archive].
+
<br /><br />
+
 
+
= coreboot Summer of Code Application =
+
 
+
Please complete the standard Google SoC 2012 application and project proposal. Prospective corebot GSoC student should provide the following information as part of their application. If you are applying for a flashrom project use common sense when using the template below, this is part of the test ;)
+
 
+
:Name:
+
:Email:
+
:IM/IRC/Skype/other contact:
+
 
+
:Country/Timezone:
+
:School:
+
:Degree Program:
+
:Expected graduation date:
+
 
+
:Most students have some time off planned during GSoC. Do you have any vacations? When and how long?
+
 
+
 
+
:coreboot welcomes students from all backgrounds and levels of experience. To be seriously consider for coreboot GSoC, we recommend joining the mailing list and IRC channel. Introduce yourself and mention that you are a prospective GSoC student. Ask questions and discuss the project that you are considering. Community involvement is a key component of coreboot development. By the time you have submitted your application, you should have downloaded, built a and booted coreboot in QEMU, SimNow, or on real hardware. Please, email your serial output results to the mailing list.
+
 
+
:The following information will help coreboot match students with mentors and projects.
+
 
+
:Please comment on your software and firmware experience.
+
 
+
:Have you participated in the coreboot community before?
+
 
+
:Have you contributed to an open source project? Which one? What was your experience?
+
 
+
:Have you built and run coreboot? Did you have problems?
+
 
+
:Bonus, Did you find and fix a coreboot bug? Did you send a patch to gerrit (git push)?
+
 
+
 
+
:Please provide an overview of your project and a break down your project in small specific goals. Think about the potential timeline. Explain what risks or potential problems your project might experience. What would you expect as a minimum level of success? Do you have a stretch goal? 
+
 
+
<br /><br />
+
  
== How to apply ==
+
If you are interested in helping, please feel free to contact me and/or start updating the wiki and add yourself and/or project ideas.
  
The Drupal project has a great page on [http://drupal.org/node/59037 How to write an SOC application].
+
= People involved =
  
Please also read Google's [http://code.google.com/p/google-summer-of-code/wiki/AdviceforStudents Advice for Students].
+
{| class="wikitable"
 +
|-
 +
! Name !! Role !! Comms
 +
|-
 +
| Stefan Tauner || flashrom: organizer/possible mentor/wannabe student || IRC: stefanct, [http://www.flashrom.org/mailman/listinfo/flashrom flashrom ML]
 +
|-
 +
|}

Revision as of 16:23, 4 March 2013


Google Summer of Code 2013

Welcome to the coreboot's Google Summer of Code 2013 page.


We are preparing to apply for GSoC 2013. Please continue to add you ideas to the projects page.


If you have questions, comments, or concerns, please send them to the mailing list or join us in IRC.


The coreboot project may also host payload and flashrom projects.

Previous coreboot GSoC projects

Call for Mentors and Project Ideas

Google has announced the 2013 GSoC program. coreboot had been a GSoC participant in the past, but was not accepted in 2012 and we would like to change that this year. The GSoC project acceptance has become much more competitive and the project ideas and student recruitment pages has become key in getting accepted. Our project ideas were not flushed out enough in the application process and we didn't have a complete mentors list/assignment for those projects.

I think that coreboot has some extremely talented people involved in the project and students should be attracted to the experience of working with our mentors as much as the potential projects.


What we need to apply for GSoC 2013:

Project Admins - We need a person or two to be the main liaison between coreboot and GSoC. This person(s) register the project, fills out the application, leads and organizes the projects and mentors.

Mentors - We need a pool of mentors willing to support students on a number of levels; Helping them from the very beginning with project ideas and writing their applications, project and development time management, research, communication, documentation, drive deadlines.

Mentor biographies - To improve out GSoC recruitment, i would like to have a one paragraph biography for each of our mentors. It should contain what your coreboot experience and contributions. Something about your work and/or education experience and maybe some other personal information. Maybe where you are located. It helps to have mentors can be matched with the students culture.

Project ideas - We also need complete project ideas with pointers to background data and what the expected outcome would be. We need a list of potential mentors for each project idea.

coreboot GSoC support roles - Even if you can't commit to being a full time mentor, we could use your help with the coreboot promotion, student recruitment, wiki, project ideas, blog postings, and code reviews , and encouragement and advice to students and mentors.

Important dates: March18 - 29 - Org applications. We should have a list of mentors and suitable project ideas, policies, etc by this date. April 1 - 5- GSoC application review April 8 - Org acceptance April 22 - May 5 - student applications

If you are interested in helping, please feel free to contact me and/or start updating the wiki and add yourself and/or project ideas.

People involved

Name Role Comms
Stefan Tauner flashrom: organizer/possible mentor/wannabe student IRC: stefanct, flashrom ML