Difference between revisions of "GCI2010"
From coreboot
| Line 5: | Line 5: | ||
See http://www.flashrom.org/GCI2010 for a huge list of flashrom related tasks. | See http://www.flashrom.org/GCI2010 for a huge list of flashrom related tasks. | ||
| − | = Code: | + | = Code: writing or refactoring code = |
| − | = Documentation: | + | = Documentation: creating/editing documents = |
* Update the FAQ wiki page, maybe restructure it | * Update the FAQ wiki page, maybe restructure it | ||
| − | |||
| − | |||
| − | = Outreach: | + | = Outreach: community management and outreach/marketing = |
| − | = Quality Assurance: | + | = Quality Assurance: testing and ensuring code is of high quality = |
* Design a coreboot tester product, hardware and software | * Design a coreboot tester product, hardware and software | ||
The test system is severely under-utilized. It would likely help to have a simple tester product or package that can be used to hook up mainboards to the test system. FPGA + ARM with Ethernet? | The test system is severely under-utilized. It would likely help to have a simple tester product or package that can be used to hook up mainboards to the test system. FPGA + ARM with Ethernet? | ||
| − | = Research: | + | = Research: studying a problem and recommending solutions = |
| − | = Training: | + | = Training: helping others learn more = |
| + | * Create a FAQ entry with a high-level overview of coreboot code | ||
| + | * Create a wiki page about devicetree.cb files | ||
| − | = Translation: | + | = Translation: localization = |
| − | = User Interface: | + | = User Interface: user experience research or user interface design and interaction = |
Revision as of 06:57, 31 October 2010
We hope to participate in Google Code-in 2010 (basically Google Summer of code for 13-18 year old students)
Please note that the task list is not finished, and we will add more tasks once we know how long individual tasks are supposed to take.
See http://www.flashrom.org/GCI2010 for a huge list of flashrom related tasks.
Code: writing or refactoring code
Documentation: creating/editing documents
- Update the FAQ wiki page, maybe restructure it
Outreach: community management and outreach/marketing
Quality Assurance: testing and ensuring code is of high quality
- Design a coreboot tester product, hardware and software
The test system is severely under-utilized. It would likely help to have a simple tester product or package that can be used to hook up mainboards to the test system. FPGA + ARM with Ethernet?
Research: studying a problem and recommending solutions
Training: helping others learn more
- Create a FAQ entry with a high-level overview of coreboot code
- Create a wiki page about devicetree.cb files
