Developers Meeting on Weds, December 12, 2012

Agenda

Regular Items

Discussion Topics

3.0 Release
1. Any thoughts on dspace-release thread around how we may wish to change the release processes in 4.0?
  1. Do we want to change our "deadlines"?
2. Any new thoughts on 3.1 timelines?
Revisiting JIRA Workflow Improvements
1. Tim is thinking of implementing this sometime in the next few weeks (if possible). Any final suggestions thoughts?
2. JIRA Backlog – any thoughts on how to try to catch up? "JIRA Backlog Bash" for a few days (almost like a Testathon but to quickly review old JIRA tickets)?
Other topics?

Additional Ongoing Topics

How can we "catch up" with JIRA Backlog?
- Do we need to "split up" the tickets & do quick reviews on our own? Or perhaps just split up tickets & do a very quick ranking & schedule ones with patches for 3.0?
- Perhaps we schedule a "JIRA Backlog Bash" event (via IRC or similar) where we work together to decrease the backlog over a few days or a week (think of this like a "Test-a-thon" but instead we'd be working to just clear out the backlog as best we can).
Brainstorming Features/Changes for future. Can we work towards development teams around any of these projects?
- Larger DSpace projects which seem to have a lot of recent support:
  - Moving towards a Common "Business Logic" / Business Services API. (I.e. avoiding duplication of business logic in all UIs)
  - Metadata For All (i.e. metadata on all objects), SubTopic: Getting us up-to-date how we use Dublin Core / DCMI. (Support from DCAT)
  - AuthN & AuthZ issues, including: DS-994, DS-1006, DS-1007, DS-1088, and developer meeting on May 2, 2012
- Other DSpace projects receiving mention recently
  - Migrate Search and Browse to DSpace Discovery
  - "Change which UIs come out-of-the-box" (and which are optionally installed later)
  - Move configurations to DB or similar (so they can be managed/edited from Admin UI)
  - Context Guided Ingest (or Item Type based submissions)
  - Other Development Proposals

If you have status items to report, please enter them below at least 1 hour before the meeting starts.

Reviewing how 3.0 release process went, brainstorms of 4.0 release processes, revisiting JIRA Workflow improvements

Getting Code Reviewed - general consensus around the following:
1. developers should be encouraged to locate a reviewer themselves, if possible
2. if a reviewer cannot be found or is not self-selected, that is where either the RT (during a release) or Committers in general can help to locate an appropriate reviewer. (And we all prefer that #1 happen as much as we can)
4.0 Release processes / scheduling features. Some general consensus/brainstorms around the following:
1. We all agree it'd be best for all development to be more open in general (share code/ideas/plans early & often)
2. We'd like it if we could work with contributors to schedule a time that their (larger) feature will be ready for review. (Code need not all be completed by date of first review, but should be in a reviewable state)
3. We may or may not want to mess around with different "final chance" deadlines...to perhaps get the "last minute pile-up of features" to happen earlier & give the RT/Committers time to work through it. The brainstorm was that the "final chance" for large features to be submitted as a pull request could be 2 months before the "freeze".
4. We may be able to combine #2 & #3 above
Discussion of JIRA Workflow Improvements

(Action items go here, if any)