* boards
* repositories
* blogging and weekly reports - how, where and what
* future meetings
* shirt sizes
* bonding - enough and how to improve, including best practices
from other orgs
* wrap-up - review any missed agenda items
Boards
* Goal was to have C4 boards and cables to all students by last week.
* maltanar got a board.
* Pramod got a board, but was not in attendance to confirm.
* drinkcat (Nicolas) already has a 5V adapter and IDC10-DB9 cable.
* varunPWM needs a 5V adapter, IDC10-DB9 cable and a XDS100v2 (if possible).
* TobiasArrskog needs a 5V adapter.
* cfriedt already has the needed power adapter and cables.
* Action: jkridner: provide e-mail of all shipping addresses
summarized to cwicks
* Action: jkridner: see if we can get some XDS100v2's, especially
for students doing kernel work
Repositories
* Ultimately, all projects need to have a final release loaded on code.google.com.
* Students should align with their mentors on the best working
place for their code.
* Students should publish their repository and bug tracking links
on their blog.
* Future meetings will be held at the same time every week
(Mondays, 14:00UTC) on #beagleboard-gsoc until further notice.
* Action: jkridner: will provide wiki link and agenda outline
ahead of every meeting.
* Action: jkridner: will send out reminder e-mail on
beagleboard-gsoc 1 hour ahead of the meeting.
* Action: jkridner: will create a sharable Google Calendar entry.
Shirt sizes
* Action: jkridner: log here what was reported on IRC
* Action: ALL: review this page in 24 hours for accuracy/completeness
* drinkcat: L
* cmurillo: XS
* av500: XXL
* maltanar: S
* topfs2: S
* mru: S
* koen: L
* SSC: L
* varunPWM: M
* cfriedt: M
* notzed: L
* jkridner: L
* katie: M
Thanks for the minutes.
The proposed time works out only so-so for me, but at least I try to
be in the channel and backread the conversation.
Wrt the issue on IDC10/DB9M cables
What I did was making my own. Fairly simple.
Find a piece of flat cable (10 wires, or make one 10 wires). If it
already has a 10 pin connector that is nice (actually perhaps 12 would
also work just make sure you have the 2 that are unused at the same
side). If there is no 10 pin connector add one (use the ones that you
just can clamp on (if that is the right term))
Then add a 9 pin rs232 connector at the other side. Make sure the
orientation is right and that you drop the 10th line, not the 1st.
With a small razorblade or so in the middle of the flat cable free the
2 and 3 lines, cut these, strip, connect 2 to 3 and 3 to 2, solder and
off you go.
Of course you could also solder the rs232 connector.
Wrt the Tshirt sizes:
- I've added mine to the wiki.
* boards
* repositories
* blogging and weekly reports - how, where and what
* future meetings
* shirt sizes
* bonding - enough and how to improve, including best practices
from other orgs
* wrap-up - review any missed agenda items
Boards
* Goal was to have C4 boards and cables to all students by last week.
* maltanar got a board.
* Pramod got a board, but was not in attendance to confirm.
* drinkcat (Nicolas) already has a 5V adapter and IDC10-DB9 cable.
* varunPWM needs a 5V adapter, IDC10-DB9 cable and a XDS100v2 (if
possible). * TobiasArrskog needs a 5V adapter.
* cfriedt already has the needed power adapter and cables.
* Action: jkridner: provide e-mail of all shipping addresses
summarized to cwicks
* Action: jkridner: see if we can get some XDS100v2's, especially
for students doing kernel work
Repositories
* Ultimately, all projects need to have a final release loaded on
code.google.com.
* Students should align with their mentors on the best working
place for their code.
* Students should publish their repository and bug tracking links
on their blog.
* Future meetings will be held at the same time every week
(Mondays, 14:00UTC) on #beagleboard-gsoc until further notice.
* Action: jkridner: will provide wiki link and agenda outline
ahead of every meeting.
* Action: jkridner: will send out reminder e-mail on
beagleboard-gsoc 1 hour ahead of the meeting.
* Action: jkridner: will create a sharable Google Calendar entry.
Will review meeting minutes from each week as that time does not work for me
to attend live. Will also try to respond comment to agenda/issues if they can
be posted before 0800 UTC.