Please note that User Registration has been temporarily disabled due to a recent increase in automated registrations. If anyone needs an account, please request one here: RequestAccount. Thanks for your patience!--Wmat (talk)
Please email User:Wmat if you experience any issues with the Request Account form.

Difference between revisions of "BeagleBoard/GSoC/Meetings/20100524"

From eLinux.org
Jump to: navigation, search
(Actions)
Line 17: Line 17:
 
* av500
 
* av500
 
* notzed
 
* notzed
 
==Repositories==
 
* Students should create a wiki page for each project with the location of their blog, source repository, bug tracker, and build/test instructions.
 
  
 
===Students===
 
===Students===
Line 26: Line 23:
 
* drinkcat
 
* drinkcat
 
* ppoudel
 
* ppoudel
 +
 +
==Repositories==
 +
* Students should create a wiki page for each project with the location of their blog, source repository, bug tracker, and build/test instructions.
 +
 +
==Reports==
 +
* Issues/ideas should be blogged when encountered and discussed with the mentors, folks on #beagle, etc., rather than waiting for the weekly report.
 +
* Weekly reports should include roughly 2 or 3 of each:
 +
** Status or accomplishments
 +
** Plans or tasks or
 +
** Risks or issues or blockers
 +
* Message should be "I've stepped back and looked where I'm at in my project and here is where I need to focus and where I need help."
  
 
==Actions==
 
==Actions==

Revision as of 14:37, 24 May 2010

Agenda

  • Placing links to repositories and blogs at BeagleBoard/GSoC.
  • Weekly reports.
  • Reminders and Google Calendar. Any volunteers to help with the calendar?
  • Boards.
  • Coding style.

Attendees

Mentors

  • koen
  • jkridner
  • eFfeM
  • cmurillo
  • Jefro
  • Crofton
  • mru
  • av500
  • notzed

Students

  • topfs2
  • maltanar
  • drinkcat
  • ppoudel

Repositories

  • Students should create a wiki page for each project with the location of their blog, source repository, bug tracker, and build/test instructions.

Reports

  • Issues/ideas should be blogged when encountered and discussed with the mentors, folks on #beagle, etc., rather than waiting for the weekly report.
  • Weekly reports should include roughly 2 or 3 of each:
    • Status or accomplishments
    • Plans or tasks or
    • Risks or issues or blockers
  • Message should be "I've stepped back and looked where I'm at in my project and here is where I need to focus and where I need help."

Actions

  • jkridner: register #beagleboard-gsoc channel
  • students: create source repo links and links to build instructions at BeagleBoard/GSoC
  • Jefro: coordinate project documentation requirements with students