Contribute to the DSpace Development Fund
The newly established DSpace Development Fund supports the development of new features prioritized by DSpace Governance. For a list of planned features see the fund wiki page.
Developers Meeting on Weds, May 16, 2012
Agenda
Regular Items
- JIRA Catch-Up – starting with issue DS-1008
Quick Notes
- Reminder: The (Face-to-Face) DSpace Developers Meeting at OR12 in Edinburgh will more than likely be on Monday, July 9.
- OR12 Meeting Wiki Page now up at: DevMtg 2012-07-09 - OR12 Meeting Please sign up if you plan to attend.
- New DSpace Developer Office Hours : Every Weds from 17:00 UTC - 20:00 UTC in #duraspace (just before this meeting)
- GitHub + JIRA Connections: This week, Tim properly configured JIRA to connect to GitHub (previously it wasn't configured right). So, JIRA should now find related GitHub Commits/Pull Requests as long as the JIRA ticket number is entered in the comments.
- For example, see the Git Commits associated with DS-1072 (a recently merged pull request)
Discussion Topics
- 3.0 Release Planning
- Main Points/Summary from last week's 3.0 Planning Meeting
- There are some concerns about the long-term 'viability' of Cocoon (which XMLUI is based on). It has served us well, but it doesn't seem to be as supported as it once was. This makes us all wonder if it's time to encourage new UI development or if we want to take a more active role in Cocoon's future. (NOTE: Currently nothing specific is in the works, though we do have several recent UI projects in: WebMVC and SkylightUI.)
- Sounds like most of us prefer the "gradual evolution" model that we've had with DSpace, as it lets us stick to our release schedules easier. So, 3.0 should be a gradual evolution from 1.8, just like 1.8 was a gradual evolution from 1.7.
- That being said, we can and should make DB changes or API changes as needed to support that evolution
- Sounds like none of us are against others starting to do re-architecture work with DSpace. However, there are obviously concerns that the work needs to be done openly so that we get buy-in from all. This work could happen parallel to 3.0.
- We still need more discussions on what exactly will be in 3.0.
- Main Points/Summary from last week's 3.0 Planning Meeting
Additional Ongoing Topics
- 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
- Larger DSpace projects which seem to have a lot of recent support:
Individual Status Updates
If you have status items to report, please enter them below at least 1 hour before the meeting starts.
Meeting Notes
JIRA Review, outcomes/summary of 3.0 Planning Mtg, Cocoon concerns, possible 3.0 features, brainstorms around supporting more metadata schemas / metadata stored as bitstreams, Fedora Inside
Meeting Transcript
- Full IRC Transcript is available at - http://irclogs.duraspace.org/index.php?date=2012-05-16
Action Items
Action items coming out of this meeting go here, if any.