Difference between revisions of "DiscoverEd Sprint (June, 2010)"

From Creative Commons
Jump to: navigation, search
(Overview)
m (Attendees: fix minor typo)
Line 9: Line 9:
 
== Attendees ==
 
== Attendees ==
  
* Asheesh Laroia (Open Hatch / Creative Commons)
+
* Asheesh Laroia (OpenHatch / Creative Commons)
* Raphael Krut-Landau (Open Hatch / Creative Commons)
+
* Raphael Krut-Landau (OpenHatch / Creative Commons)
 
* [[User:Nathan Yergler|Nathan Yergler]] (Creative Commons)
 
* [[User:Nathan Yergler|Nathan Yergler]] (Creative Commons)
 
* Alex Kozak (Creative Commons)
 
* Alex Kozak (Creative Commons)

Revision as of 16:34, 14 June 2010


Overview

Attendees

  • Asheesh Laroia (OpenHatch / Creative Commons)
  • Raphael Krut-Landau (OpenHatch / Creative Commons)
  • Nathan Yergler (Creative Commons)
  • Alex Kozak (Creative Commons)
  • Ali Asad Lotia (open.michigan)
  • Kevin Coffman (open.michigan)
  • add your name and affiliation here

Travel & Accommodations

Agenda

This is a draft, subject to change.

Tuesday

  • 9:00 AM - Welcome
  • DiscoverEd Context: Why, When, Where are we going? (10 min)
  • Introductions
    Developers introduce themselves, give brief statement on what they've done with DiscoverEd, what they're interested in working on. (5 min ea.)
  • MSU Context: AgShare, FSKN, etc (Chris Geith, 10-15 min)
  • 10:30 AM - Identify Themes, Possible Blocks of Work
  • 11:30 AM - Pair up and begin work
  • 4:45 PM - Brief report back from each group: unexpected issues, things to bring to the group as a whole, etc.

Wednesday

No schedule; work as pairs.

Thursday

  • 3:30 PM - Pairs begin to make sure work is pushed to Gitorious, determine next steps
  • 4:00 PM - Full report back: pairs report on progress and state of their code. Pairs are encouraged to identify follow up steps they will take post sprint to see tasks to completion.

Preparation

In order to minimize time spent configuring laptops, etc, please try to do the following before arriving at the sprint:

  1. Make sure you have prerequisite software installed and working:
  2. Generate an SSH public key (if needed; see http://progit.org/book/ch4-3.html for some instructions)
  3. Create a Gitorious account and add your SSH key to it

Code Preparation

TBD