Attendees
General
- Indicates who took minutes -
- Call-in: Google-hangout at:
Goals
- Finalize versioning
- Triplestore/Solr
- Rebuild
- Support multiple repositories
- Clustering potential: HA and Scalability
- Performance: hierarchy
- Resource locking
Minutes
- High level: Honing in and focusing on feature completeness for Fedora 4.0 Feature Set
- Loose ends: versioning, triple store, and performance
- Introduction for new sprint developers:
- Bug tracking done in Pivotal (documentation for it is on the wiki at Story Management)
- Tickets for the current sprint are listed in "Current" (their order indicates priority)
- You're the "Owner" for your tickets; click "Start" when you start a ticket and "Finish" when you finish
- Put a link to a pull request into the ticket, and wiki documentation if applicable, before you click "Finish"
- Finished tickets that need more work go temporarily into "Rejected" state
- Developers can click "Finish" again after additional work has been done
- Tickets for features are assigned points to indicate level of effort
- 3 points equals an ideal workday
- 1 point equals a trivial amount of work
- 5 points equals a multi-day task
- 8 points means a ticket needs to be broken into smaller tasks
- GitHub
- You can create a branch in the fcrepo4 repo, but it's probably best to fork and create branches in your fork for the work you do
- If, after submitting a pull request (PR), additional work in the branch is done, the PR is automatically updated with the new work
- Generally, all commits on a branch are squashed before merged to master; talk to Andrew if there is value in keeping multiple commits
- Unit tests and displayed in Sonar http://sonar.fcrepo.org/dashboard/index/org.fcrepo:fcrepo
- New code should contain unit tests (examples are in the code base)
- Would be nice to have integration tests as well, if applicable (examples are in the code base)
- IRC channel is used for ongoing/daily project communication (#duraspace-ff on irc.freenode.net (IRC logs))
- Ticket Highlights