Developers Meeting on Weds, April 4, 2012

Agenda

Regular Items

• JIRA Catch-Up – starting with issue DS-970
  • Search for all Unresolved Issues (since DS-970)

Discussion Topics

1. GitHub Migration
   • Latest status?
   • Do we want to start any sort of "GitHub Best Practices" (for how Committers will work together in GitHub)
     • E.g. Take a look at Fedora's Git Guidelines and Best Practices
2. 3.0 Release Planning
   • Features to add to the "possible features" list?
   • We still need a "team leader" for our Release Team.
     • Current Release Team (all volunteered in Fall): Hardy P, Sands F, Kim S, Robin T
3. Revisiting Virtual Summit idea
   • Still need to get to many of our "Actionable Takeaways"
   • Any thoughts on how many times would we like to hold this Summit per year? Once (Jan/Feb)? Twice (Jan and May/June)? Three times (Jan, May & Sept)?
4. Other topics?

Additional Ongoing Topics

1. Brainstorming Features/Changes for 3.0. 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)
   • 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

Individual Status Updates

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

Meeting Notes

Meeting Transcript

• Full IRC Transcript is available at - http://irclogs.duraspace.org/index.php?date=2012-04-04

Action Items

Action items coming out of this meeting go here, if any.

• TODO - Update the ReleaseCoordinating page to better outline Release Processes
  • Add "Update this document with lessons learned" as the final task of any release.