Difference between revisions of "BeagleBoard/GSoC/Meetings/20100802"
From eLinux.org
Peter Huewe (Talk | contribs) (Added to category BeagleBoard and GSOC) |
|||
| (One intermediate revision by one user not shown) | |||
| Line 28: | Line 28: | ||
===Documentation=== | ===Documentation=== | ||
* should be complete & correct | * should be complete & correct | ||
| − | * Jefro available for help | + | * Jefro available for help, do not hesitate to ask |
===Deliverables=== | ===Deliverables=== | ||
| Line 35: | Line 35: | ||
* jkdridner really wants "clean" deliverables - easy to reproduce, a clean conclusion, noting that work can continue later | * jkdridner really wants "clean" deliverables - easy to reproduce, a clean conclusion, noting that work can continue later | ||
* now is the time for fixing bugs & cleaning up, aka "feature freeze" | * now is the time for fixing bugs & cleaning up, aka "feature freeze" | ||
| + | * code review = set of patches, documentation for each patch & overall usage instructions, code comments, any other supporting materials deemed appropriate by the mentor | ||
| + | |||
| + | ===Blockers=== | ||
| + | * maltanar has useful code, but OE integration is blocked on TI build systems work, though c6run already modified; currently produces nonworking executables | ||
| + | * topfs2 is having some issues with sgx+alpha overlays | ||
| + | |||
| + | |||
| + | [[Category:BeagleBoard]] | ||
| + | [[Category:GSOC]] | ||
Latest revision as of 05:41, 13 April 2011
Contents |
Attendees
Students
- cfriedt
- drinkcat
- maltanar
- topfs2
- ppoudel
- neo01124
Mentors
- jkridner
- mru
- eFfeM_work
- Jefro
- koen
- av500
- katie
- Crofton
- notzed
Discussion
Final 2 weeks
- One week until recommended pencils-down date (Aug 9)
- Everyone ready for review on Monday?
- ANY issues preferred not to be discussed in public, please contact Jason Kridner ASAP.
- All 6 students report readiness for review by Monday Aug 9
Documentation
- should be complete & correct
- Jefro available for help, do not hesitate to ask
Deliverables
- projects must be checked into code.google.com
- what gets checked in? patches, docs - anything the student actually did
- jkdridner really wants "clean" deliverables - easy to reproduce, a clean conclusion, noting that work can continue later
- now is the time for fixing bugs & cleaning up, aka "feature freeze"
- code review = set of patches, documentation for each patch & overall usage instructions, code comments, any other supporting materials deemed appropriate by the mentor
Blockers
- maltanar has useful code, but OE integration is blocked on TI build systems work, though c6run already modified; currently produces nonworking executables
- topfs2 is having some issues with sgx+alpha overlays
