Page History

...

• 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

1. 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: LynCodeFeedback on the DSpace Developers Meeting at OR12 draft agenda?
2. Should we schedule more time in for "3.0 Discussions"?
3. Did we want to schedule in 1/2 hr or so for Jonathan Markow (DuraSpace Chief Strategy Officer) to talk / answer questions on DSpace + Fedora and DuraSpace roadmaps?
Is there anything that you feel could be "cut" from the agenda, or discussed instead as a "Special Topic" Meeting or as a "Developers Summit" in late Summer / early Fall?
4. 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.)?
5. 3.0 Release Updates / Possible feature updates or ideas
   • REMINDER: Add your planned 3.0 contributions to the 3.0 Wiki Page
   • 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
   • 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
6. 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.)?
7. Other topics?

Additional Ongoing Topics

...