...
- Discuss/prioritize initial list of High-level Requirements
- Pick a list of requirements that could potentially drive first sprint(s)
- See comments on high-level requirements page:
- Are deployment-related issues appropriate as requirements, or are they goals?
- If they are goals, do we have other items that are also goals, but not requirements?
- Is it appropriate for an API-X extension to use native java APIs such as fcrepo-kernel-api, or should they use standardized and codified fedora HTTP APIs?
- Are deployment-related issues appropriate as requirements, or are they goals?
- Discuss list of potential Proof of Concept ideas. Do we want to pursue one or more of these as a team? Individually?
- Rough implementation timeline
Minutes
Agenda Item 1: Review initial list of High Level Requirements
...
E.M./A.B. proposed HTTP RFC compatability compatibility as a design decision consideration *ACTION*
A.C. Clarified that the items in #2 Patterns are not exclusive
...
A.B. *ACTION* to add this clarifying language to the high level reqirementsrequirements.
A.B. Review item 3, now Service Discovery & Binding
...
E.M. Suggested a high-level roadmap would be useful
A.B. Proposed assembing assembling the details/goals of the first sprint and then discussing them at the next meeting
...