SB Discovery Meeting

Discovery Switchback-Open.Michigan meeting

Discovery Switchback-Open.Michigan meeting 2.10.10 - Open.Michigan's office, Catherine St., 11:30am-1:30pm

--

Attendees
Open.Michigan:
 * Ali Asad Lotia - software engineer
 * Susan Topol - publications manager
 * Kevin Coffman - software engineer
 * Pieter Kleymeer - project manager
 * Bob Riddle (by phone) - software engineer

Switchback:
 * Marla Sokolowski - project manager (contact point, reports, deliverables, time-management)
 * Mike Monan - co-founder (peripheral role)
 * Ken Rorick - software engineer (code changes, supporting Victor and Jamie)
 * Victor Kareh - software engineer (Drupal)
 * Jamie Larsen - designer & software engineer (front-end developer, designer, usability)

Initial Questions + Answers

 * O.M. - What is your style of development? (i.e., how do you intend to interact with us?)
 * SB - We use a development site on our internal servers, through a project management database we track cases as a task manager, as tasks are accomplished we conduct QA testing and we use SVN (Github) for version control.
 * O.M. - How many developers of yours will be working on this?
 * SB - We will have 2 developers and 1 designer/developer on your project along with myself.


 * O.M. - Who is the main liaison from Switchback? (from Open.Michigan: Piet - I will try to handle as much of the communication as possible)
 * SB - I your friendly buckeye will be the main liaison. (Marla)


 * O.M. - How will you track bugs we find? How can we follow along with their progress and give input on priorities?
 * SB - I will issue you access to the Project Management database where you can follow along with the progress and enter and track bugs.


 * O.M. - How will you track billable hours? How can we stay posted on hours billed?
 * SB - I have a separate database which tracks billable hours per employee.  I will prepare and distribute a report to you bi-monthly on the hours billed.  Unless you would prefer sooner.


 * O.M. - On what server/system will you do the development? How will we sync up with your code for testing? Will you put code out on something like Github?
 * SB - We conduct development on our internal servers and through Github or SVN we will sync up the code. We normally use SVN for software source code.  We will evaluate using Github if you feel it would be more beneficial.


 * O.M. - Are you interested in having some work space available at our office?
 * SB - Absolutely. Thanks.  We feel it would be beneficial for our developers to be  on-site with access to your team

Timeline

 * start: February 10th (an initial meeting to go over the timeline and expectations is probably a good start)
 * phase 0: 2/10 - 2/16
 * phase 0 review: week of 2/15-2/22 -> spill over possible to 2/22 w/adjustments
 * phase 0 adjustments: week of 2/15-2/22
 * phase 1a: 2/22-3/12 (there will most likely be some overlap with Phase 0)
 * phase 1a review: week of 3/15
 * phase 1a adjustments: week of 3/15
 * phase 1b: 3/22-4/2 (Open.Michigan start looking at data migration, some overlap with Phase 1a)
 * phase 1b review: week of 4/5
 * phase 1b adjustments: week of 4/5

Topics of Discussion
Hosting - O.M. will host locally at MSIS. Bob has an extra 60GB of space for us on the VM - will put a Drupal instance up to reserve space. // to consider: hosting with Switchback? no, expertise in system design. can help us get caching layers and multiple VMs in place.

GitHub vs. SVN (or script SVN push to GitHub, GitHub pull from SVN) - we would prefer having code on GitHub (Ali has set up a GitHub ID for us: http://github.com/openmichigan)

O.M. will have access to SW dev server to test and grab code. SW will make a public-facing SVN for us.

O.M. will need some deployment instructions at various stages so we can implement the code.

IA - how will this actually look within Drupal. we don't need to stay with the Plone architecture. Drupal won't really lock us in to too much of the framing. - adding the static portion of the open.umich.edu site to Drupal.

O.M. will need to migrate the data from Plone to Drupal with some assistance/guidance from SW. We will also need to add new metadata for a lot of content, including EVERY SINGLE IMAGE AND DOCUMENT. ugh. - hire an undergrad?

Pressflow for MySQL? (updates to core will require reinstalling pressflow patches)

Logistics - who contacts whom? how?


 * weekly meeting and who will participate: everyone (5-10 people)
 * 1-1.5 hr meeting on Thursdays

Questions/Tasks

 * Piet - give access to SW for Google Analytics
 * Marla will send budget and progress reports to Piet, Ted
 * Mike will send SW the publishing wiki page (we can resend).
 * SW will set up our access to their PM Drupal site for bugs, etc.