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

From eLinux.org
Jump to: navigation, search
(Added to category BeagleBoard and GSOC)
(9 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
==Agenda==
 
==Agenda==
* Placing links to repositories and blogs at [[BeagleBoard/GSoC]].
+
* Links to repositories and blogs.
 
* Weekly reports.
 
* Weekly reports.
* Reminders and Google Calendar. Any volunteers to help with the calendar?
+
* Reminders and Google Calendar.
* Boards.
+
* Boards and equipment.
 
* Coding style.
 
* Coding style.
  
Line 23: 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
 +
** 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.
 +
** Best calendar link is now http://www.google.com/calendar/hosted/beagleboard.org/embed?src=beagleboard.org_20sa2k7jbjpc612ujl7bg3frgs%40group.calendar.google.com&ctz=UTC
 +
 +
==Boards==
 +
* ppoudel has a board.
 +
* maltanar has a board.
 +
* topfs2 is expecting his board very soon.  Needs a serial adapter and cable.
 +
* varun has a board.
 +
* drinkcat should have a board by tomorrow.
 +
* cfriedt did not attend.
 +
 +
==Style==
 +
* Use one and be consistent.  Better consistent than "right".
 +
* Discuss coding style with your mentors.
  
 
==Actions==
 
==Actions==
* '''jkridner''': register this channel
+
* '''jkridner''': register #beagleboard-gsoc channel
*
+
* '''jkridner''': create a beagleboard-gsoc-specific feed and use it to send e-mails of the weekly reports to beagleboard-gsoc mailing list
 +
* '''Jefro''': coordinate project documentation requirements with students
 +
* '''students''': create source repo links and links to build instructions at [[BeagleBoard/GSoC/2010_Projects]] per Jefro
 +
 
 +
 
 +
[[Category:BeagleBoard]]
 +
[[Category:GSOC]]

Revision as of 05:39, 13 April 2011

Agenda

  • Links to repositories and blogs.
  • Weekly reports.
  • Reminders and Google 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

Boards

  • ppoudel has a board.
  • maltanar has a board.
  • topfs2 is expecting his board very soon. Needs a serial adapter and cable.
  • varun has a board.
  • drinkcat should have a board by tomorrow.
  • cfriedt did not attend.

Style

  • Use one and be consistent. Better consistent than "right".
  • Discuss coding style with your mentors.

Actions

  • jkridner: register #beagleboard-gsoc channel
  • jkridner: create a beagleboard-gsoc-specific feed and use it to send e-mails of the weekly reports to beagleboard-gsoc mailing list
  • Jefro: coordinate project documentation requirements with students
  • students: create source repo links and links to build instructions at BeagleBoard/GSoC/2010_Projects per Jefro