Meeting Goals
Achieve shared understanding of:
The proposal, at least at the high level
Participant’s roles and commitments
Development process
Process for reviewing, prioritizing, and accepting use cases and requirements
Discuss (time permitting):
Current use cases
Scope
Attendees
Agenda
Introduction and Proposal Review
Roles and Commitments
Identify Stakeholders, Designers, Developers
Development Process(es)
Sprint-based? Two-weeks in length? For design and development?
Process for identifying what tasks go in a sprint
Communication modes (IRC, Slack, list email, etc?)
Does every role have to be at every meeting? Sensitive to the time commitments of Stakeholders, especially
Location for documents, code (Duraspace wiki? Fedora GitHub?)
Process for reviewing and accepting use cases, scope, and requirements
Do we vote on them?
Prioritize them in some way?
Discuss Use Cases
Are they adequately described?
Do we have all the use cases we need or want? Are there more?
Discussion of scope
Related Resources
Fedora API Extension Architecture Proposal (original proposal, Google doc)
Design Page for the proposal on the Duraspace Wiki
Minutes of the introduction of the proposal, Fedora Committers Meeting June - OR ‘15