Difference between revisions of "GSoC"

From coreboot
Jump to: navigation, search
(People involved)
(Important dates)
(38 intermediate revisions by 8 users not shown)
Line 1: Line 1:
__FORCETOC__
+
Welcome to coreboot [http://www.google-melange.com/gsoc/homepage/google/gsoc2013 Google Summer of Code, 2013].
  
= Google Summer of Code 2013 =
+
coreboot has many [[Project Ideas]] for various firmware ability levels. The coreboot project also hosts [http://flashrom.org/GSoC flashrom] and [http://serialice.com/GSoC SerialICE] projects.
  
Welcome to the coreboot's [http://www.google-melange.com/gsoc/homepage/google/gsoc2013 Google Summer of Code 2013] page.
+
__FORCETOC__
  
 +
== coreboot contact ==
  
We are preparing to apply for GSoC 2013. Please continue to add your ideas to the [[Project Ideas|projects page]].  
+
If you are interested in becoming a GSoC student, please contact the coreboot [[Mailinglist|mailing list]] or visit our [[IRC]] channel <code>#coreboot</code> on [https://webchat.freenode.net irc.freenode.net].
  
 +
If you need to contact someone directly, [mailto:marcj303@gmail.com Marc Jones] is the GSoC admin for coreboot.
 +
<br/><br/>
  
If you have questions, comments, or concerns, please send them to the [[Mailinglist|mailing list]] or join us in [[IRC]].
+
= Why work on coreboot for GSoC 2013? =
  
 +
* coreboot offers you the opportunity to work with modern technology “right on the iron”. coreboot supports current silicon from AMD and Intel.
 +
* coreboot has a worldwide developer and user base.
 +
* We are a very passionate team – so you will interact directly with the project initiators and project leaders.
 +
* We have a large, helpful community. coreboot has some extremely talented and helpful experts in firmware involved in the project. They are ready to assist and mentor students participating in GSoC 2013.
 +
* One of the last areas where open source software is not common is firmware. Running proprietary firmware can have severe effects on user's freedom and security. coreboot changes that by providing a common framework for initial hardware initialization and you can help us succeed.
 +
<br/><br/>
  
The coreboot project may also host payload and [http://flashrom.org/GSoC flashrom] projects.
+
= GSoC Student requirements =
<br /><br />
+
  
[[Previous GSoC Projects|Previous coreboot GSoC projects]]
+
What will be required of you to be a coreboot GSoC student?
  
= Call for Mentors and Project Ideas =
+
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 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.  
+
# Prior to project acceptance, you have demonstrated that you can work with the coreboot codebase.
 +
#* By the time you have submitted your application, you should have downloaded, built and booted coreboot in QEMU, SimNow, or on real hardware. Please, email your serial output results to the mailing list.
 +
#* Send a patch to Gerrit for review. Check [[Easy projects]] or ask for simple tasks on the mailing list or on IRC.
 +
# To pass and to be 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.
 +
#* 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/
 +
# Student must be active on IRC and the mailing list.  
  
 +
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/>
  
What we need to apply for GSoC 2013:
+
= Projects =
 +
There are many development tasks available in coreboot. Please visit the following pages for some ideas or come up with your own idea.
 +
* [[Project Ideas|coreboot project ideas]]
 +
* [http://www.flashrom.org/GSoC flashrom project ideas]
 +
* [http://serialice.com/GSoC SerialICE project ideas]
  
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.
+
We keep a list of [[previous GSoC Projects]] which might be of interest to you to see what others have accomplished.
 +
Similarly the [http://blogs.coreboot.org/blog/category/gsoc/ blog posts related to previous GSoC projects] might give some insights to what it is like to be a coreboot GSoC student.
 +
<br/><br/>
  
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.
+
== Your own Project Ideas ==
  
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.
+
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.
  
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.  
+
But of course your application does not need to be based on any of the ideas listed. The opposite: Maybe you have a great idea that we just didn't think of yet. Please let us know!
 +
<br/><br/>
  
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.
+
= Mentors =
  
Important dates:
+
The following coreboot developers have volunteered to be GSoC mentors. Please stop by IRC and say hi to them and ask them questions about coreboot.
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 =
+
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 49: Line 64:
 
! Name !! Role !! Comms
 
! Name !! Role !! Comms
 
|-
 
|-
| David Hendricks || flashrom: possible mentor || IRC: dhendrix, [http://www.flashrom.org/mailman/listinfo/flashrom flashrom ML]
+
| [[User:MJones|Marc Jones]] || coreboot: co-organizer and mentor || IRC: marcj
 
|-
 
|-
| Stefan Tauner || flashrom: organizer/possible mentor/wannabe student || IRC: stefanct, [http://www.flashrom.org/mailman/listinfo/flashrom flashrom ML]
+
| [[User:PatrickGeorgi|Patrick Georgi]] || coreboot: co-organizer and mentor || IRC: patrickg, pgeorgi
 
|-
 
|-
| Patrick Georgi || coreboot: possible co-organizer, possible co-mentor ("co-" since on vacation during GSoC period) || IRC: patrickg, pgeorgi
+
| [[User:Stepan|Stefan Reinauer]] || coreboot/serialice: mentor || IRC: stepan
 
|-
 
|-
| Marc Jones || coreboot: co-organizer and mentor || IRC: marcj
+
| [[User:Dhendrix|David Hendricks]] || flashrom: possible mentor || IRC: dhendrix, [http://www.flashrom.org/mailman/listinfo/flashrom flashrom ML]
 
|-
 
|-
| Kyösti Mälkki || serialice: wannabe student || IRC: kmalkki, [http://www.serialice.com/mailman/listinfo/serialice SerialICE ML]
+
| [http://www.flashrom.org/User:Roysjosh Joshua Roys] || flashrom: possible mentor || IRC: roysjosh
 
|-
 
|-
| Stefan Reinauer || coreboot: mentor || IRC: stepan
+
| [[User:ruik|Rudolf Marek]] || coreboot: possible mentor || IRC: ruik
 
|-
 
|-
| Alexandru Gagniuc || wannabe student || IRC: mrnuke
+
| [[User:Jason Wang|QingPei Wang]] || coreboot: possible mentor || IRC:QingPei
 +
|-
 +
| [[User:MartinRoth|Martin Roth]] || coreboot: possible mentor || IRC: martinr
 +
|-
 +
| [http://www.flashrom.org/User:Hailfinger Carl-Daniel Hailfinger] || flashrom: possible mentor || IRC: carldani
 
|-
 
|-
 
|}
 
|}
 +
 +
'''Note to mentors:''' Each accepted project will have a lead mentor and a backup mentor. We will match mentors and students based on the project, experience level, and geographic location (native language, culture and time zone).
 +
<br/><br/>
 +
 +
= coreboot Summer of Code Application =
 +
 +
Please complete the standard Google SoC application and project proposal. Prospective coreboot GSoC student should provide the following information as part of their application. If you are applying for a flashrom or SerialICE 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 considered 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?
 +
 +
Did you find and fix a coreboot bug? Did you send a patch to Gerrit? Please provide a link to the Gerrit page.
 +
 +
Please provide an overview of your project and a break down of 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/>
 +
 +
== Advice on how to apply ==
 +
 +
Your application should include a complete project proposal. You should document that you have the knowledge and the ability to complete your proposed project. This may require a little research and understanding of coreboot prior to sending your application. Mentors are your best resource in flushing out your project ideas and helping with a project timeline. We recommend that you get feedback and recommendations on your proposal before the application deadline.
 +
 +
The Drupal project has a great page on [http://drupal.org/node/59037 how to write an SOC application].
 +
 +
Please also read Google's [http://code.google.com/p/google-summer-of-code/wiki/AdviceforStudents Advice for Students].
 +
<br/><br/>
 +
 +
== Important dates ==
 +
 +
* April 1–5: Google program administrators review organization applications.
 +
* April 8: List of accepted mentoring organizations published on the Google Summer of Code 2013 site.
 +
* April 9–21: Would-be student participants discuss application ideas with mentoring organizations.
 +
* April 22: Student application period opens.
 +
* May 3: Student application deadline.
 +
 +
The official timetable can be found [http://www.google-melange.com/gsoc/events/google/gsoc2013 here].
 +
 +
<font size= 1>All deadlines end at 19:00 [http://en.wikipedia.org/wiki/UTC UTC].</font size>
 +
 +
=== Past deadlines ===
 +
* March 29: Mentoring organization application deadline.

Revision as of 15:01, 3 April 2013

Welcome to coreboot Google Summer of Code, 2013.

coreboot has many Project Ideas for various firmware ability levels. The coreboot project also hosts flashrom and SerialICE projects.


coreboot contact

If you are interested in becoming a GSoC student, please contact the coreboot mailing list or visit our IRC channel #coreboot on irc.freenode.net.

If you need to contact someone directly, Marc Jones is the GSoC admin for coreboot.

Why work on coreboot for GSoC 2013?

  • coreboot offers you the opportunity to work with modern technology “right on the iron”. coreboot supports current silicon from AMD and Intel.
  • coreboot has a worldwide developer and user base.
  • We are a very passionate team – so you will interact directly with the project initiators and project leaders.
  • We have a large, helpful community. coreboot has some extremely talented and helpful experts in firmware involved in the project. They are ready to assist and mentor students participating in GSoC 2013.
  • One of the last areas where open source software is not common is firmware. Running proprietary firmware can have severe effects on user's freedom and security. coreboot changes that by providing a common framework for initial hardware initialization and you can help us succeed.



GSoC Student requirements

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.

  1. Prior to project acceptance, you have demonstrated that you can work with the coreboot codebase.
    • By the time you have submitted your application, you should have downloaded, built and booted coreboot in QEMU, SimNow, or on real hardware. Please, email your serial output results to the mailing list.
    • Send a patch to Gerrit for review. Check Easy projects or ask for simple tasks on the mailing list or on IRC.
  2. To pass and to be 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.
    • You must have made progress and committed significant code before the mid-term point and by the final.
  3. 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/
  4. Student must be active on IRC and the mailing list.

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.

Projects

There are many development tasks available in coreboot. Please visit the following pages for some ideas or come up with your own idea.

We keep a list of previous GSoC Projects which might be of interest to you to see what others have accomplished. Similarly the blog posts related to previous GSoC projects might give some insights to what it is like to be a coreboot GSoC student.

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. The opposite: Maybe you have a great idea that we just didn't think of yet. Please let us know!

Mentors

The following coreboot developers have volunteered to be GSoC mentors. Please stop by IRC and say hi to them and ask them questions about coreboot.

Name Role Comms
Marc Jones coreboot: co-organizer and mentor IRC: marcj
Patrick Georgi coreboot: co-organizer and mentor IRC: patrickg, pgeorgi
Stefan Reinauer coreboot/serialice: mentor IRC: stepan
David Hendricks flashrom: possible mentor IRC: dhendrix, flashrom ML
Joshua Roys flashrom: possible mentor IRC: roysjosh
Rudolf Marek coreboot: possible mentor IRC: ruik
QingPei Wang coreboot: possible mentor IRC:QingPei
Martin Roth coreboot: possible mentor IRC: martinr
Carl-Daniel Hailfinger flashrom: possible mentor IRC: carldani

Note to mentors: Each accepted project will have a lead mentor and a backup mentor. We will match mentors and students based on the project, experience level, and geographic location (native language, culture and time zone).

coreboot Summer of Code Application

Please complete the standard Google SoC application and project proposal. Prospective coreboot GSoC student should provide the following information as part of their application. If you are applying for a flashrom or SerialICE 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 considered 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?

Did you find and fix a coreboot bug? Did you send a patch to Gerrit? Please provide a link to the Gerrit page.

Please provide an overview of your project and a break down of 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?

Advice on how to apply

Your application should include a complete project proposal. You should document that you have the knowledge and the ability to complete your proposed project. This may require a little research and understanding of coreboot prior to sending your application. Mentors are your best resource in flushing out your project ideas and helping with a project timeline. We recommend that you get feedback and recommendations on your proposal before the application deadline.

The Drupal project has a great page on how to write an SOC application.

Please also read Google's Advice for Students.

Important dates

  • April 1–5: Google program administrators review organization applications.
  • April 8: List of accepted mentoring organizations published on the Google Summer of Code 2013 site.
  • April 9–21: Would-be student participants discuss application ideas with mentoring organizations.
  • April 22: Student application period opens.
  • May 3: Student application deadline.

The official timetable can be found here.

All deadlines end at 19:00 UTC.

Past deadlines

  • March 29: Mentoring organization application deadline.