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

From eLinux.org
Jump to: navigation, search
Line 3: Line 3:
 
* Weekly reports.
 
* Weekly reports.
 
* Reminders and Google Calendar.  Any volunteers to help with the calendar?
 
* Reminders and Google Calendar.  Any volunteers to help with the calendar?
* Boards.
+
* Boards and equipment.
 
* Coding style.
 
* Coding style.
  
Line 31: Line 31:
 
* Weekly reports should include roughly 2 or 3 of each:
 
* Weekly reports should include roughly 2 or 3 of each:
 
** Status or accomplishments
 
** Status or accomplishments
** Plans or tasks or
+
** Plans or tasks
 
** Risks or issues or blockers
 
** 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."
 
* 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."
 +
* Deadline is before the weekly all-hands meeting
 +
 +
==Calendar==
 +
* jkridner to work with Jefro and drinkcat on making a better public calendar.
 +
 +
==Boards==
  
 
==Actions==
 
==Actions==

Revision as of 14:51, 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 and equipment.
  • 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
    • 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."
  • Deadline is before the weekly all-hands meeting

Calendar

  • jkridner to work with Jefro and drinkcat on making a better public calendar.

Boards

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