Developers Meeting on Weds, June 20, 2012

Agenda

Regular Items

JIRA Reviews – starting with issue DS-1048
- Search for all Unresolved Issues (since DS-1048)
REMINDER: Sign up for DSpace Developers Meeting at OR12 if you plan to attend!
- If you have any further feedback on the OR12 Meeting Agenda, get in touch with Tim Donohue or Richard Rodgers

Discussion Topics

Possible code contributions from LynCode: a LynCode developer will be present to offer us an alternative configurable OAI interface with DRIVER and OpenAIRE support and other possible contributions. Summary: LynCode
3.0 Release Updates / Possible feature updates or ideas (REMINDER: Add your planned 3.0 contributions to the 3.0 Wiki Page)
1. Where should translations of individual modules like Discovery go? Including them in the main messages.xml currently works. This should be answered before freeze time, it already poses another barrier for commiting of translations, see DS-1049, DS-1054. This is a subproblem of i18n Improvements Proposal, but let us not divert this discussion too much to broad topics. ~~helix84
2. DS-531: ETD-MS schema out of the box. Again, the larger problem is that our metadata schema should be brought up-to-date with DCMI, but maybe we could tackle this smaller issue of ETDs. I suggest we add a "thesis" schema with 5 fields mentioned in this table to support ETD-MS out-of-the-box. ~~helix84
Need to review Guidelines for Committing based on GitHub/Git?
- Thoughts on how we rework these polices to our new GitHub development environment (with Pull Request policies, etc.)?
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 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)
  - 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.

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