Infrastructure Lifecycle Meeting August 30th 2007

2:00PM EST, Thursday, August 30th, 2007

Meeting Agenda:

• Determine voting process
• Decide on meeting protocols, agenda, and notification
• Establish a work approval process
• Establish a quality and review process
• Clarify and adjust the working group charter
• Determine and assign short term action items.
• Set a time/date/agenda for next meeting.

Basically, we need to get together to set the ground rules, make sure we all agree on what it is we're trying to do and then make a plan to achieve our objective.

The teleconference info is:

Toll Free: 1-877-421-0033
Local: 770-615-1250
Passcode: 583191

---

Meeting Minutes

Attendees: Jim Galarowicz, Darius Buntinas, Rich Graham, Dorian Arnold,, Greg Watson, John Robb, Steve Cooper

• Determine voting process
  • The first step is to attempt to establish consensus.
  • If consensus can not be reached then every member of the working group gets one vote.

• Decide on meeting protocols, agenda, and notification
  • Quorum
    • a simple majority of the working group members must be present and reach consensus;
    • otherwise the discussion will require a vote by all working group members executed via email.
  • Notification
    • At least one week notice is required.
  • Agenda
    • Outline to accompany notification, any additions should be added a.s.a.p. and will be dealt with as time permits.
    • Agenda should also be made available on the wiki at the same time.

• Establish a work approval process
  • Check-in to the main trunk (source of future release branches) repository must pass test suite.
  • Release branches are only open for bug fixes.
  • Development branches (work on features not part of any development track) is open.

• Establish a quality and review process
  • A regression test suite should be established and kept up to date.
  • Ideally, an automated test suite should be run every night.
  • The design coordinator is responsible for insuring that the components are consistent with design goals.
  • The design coordinator may assign a member of the working group to review any contribution.
  • All check-ins need to reference a development track that is estabished in advance.
  • For now, Steve Cooper will serve as the design coordinator for the working group.

• Clarify and adjust the working group charter
  • The Lifecycle of the infrastructure.
  • The transition from nothing to an infrastructure…
  • … the teardown of said infrastructure.
  • There was debate over whether installation was included or not.
  • Further clarification should result from the investigation into use cases.

• Determine and assign short term action items.
  • Select a Use Case from the master list (prepared by Rich) or come up with another use case and then generate a detailed description of the use case.

• Set a time/date/agenda for next meeting.
  • A joint meeting with the Data Exchange working group will be held Septemeber 12th.
  • The next meeting of this working group will be 2PM EST, September 13th
  • Preliminary Agenda
    • Review the joint meeting with the Data Exchange WG.
    • Verify use case coverage.
    • Confirm use case assignments
    • Establish time/date for next meeting.