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.
Table of Contents
The root page DSPACE:Developer Meetings could not be found in space DSpace.
Meeting Schedule and Attendance
DSpace Developer meetings are a time when Committers and interested Developers can discuss new software features, upcoming releases of DSpace software, and generally plan out the roadmap of DSpace. All meetings are public. We welcome anyone and everyone to attend, speak their opinions or just listen in on the discussions. Please note that we archive all discussions (see Meeting Archives), as a service for those who are unable to attend.
DSpace Developer meetings take place on the following schedule:
- Every Wednesday at 20:00 UTC/GMT in #duraspace IRC channel
- All meetings are held for 1 hour (although, admittedly, discussion sometimes extends beyond that)
See the world clock to determine the meeting time where you live.
Meeting topics often include:
- Recent updates on upcoming DSpace releases, bug fixes or features
- Reviewing of recent reported issues/bugs/feature requests (see JIRA Cleanup Sessions for more info)
- Occasionally we vote or make decisions on upcoming DSpace technology plans/roadmap (see Developer Voting Procedures for more info)
If you are unable to attend a meeting, please feel free to add your own notes/comments to the meeting's wiki page.
Developers Meeting on Weds, September 8, 2010
Agenda
- JIRA Catch-Up (for first 20 mins or so of meeting) – starting with issue DS-612
- DSpace 1.7 Features/Updates
- Unclaimed 1.7 Issues/Potential Features in JIRA
- Other updates ???
- Test Driven Development / Committer Policies
- As Committers, should we now require Unit Testing changes as part of our Guidelines for Committing?
- These would be similar to Documentation requirements, though may be slightly looser early on (as our Unit Test coverage is only currently limited to the core API). For example:
- "All changes to core API must pass existing Unit Tests. Existing Unit Tests must also be updated when new methods are added to core API."
- "New features are highly recommended to provide Unit Tests where plausible."
Meeting Notes
JIRA Catchup, 1.7 Updates & Schedule Reminder, Test Driven Development Policies
- JIRA Catchup – ended with issue DS-616
- DSpace 1.7 Updates & Schedule
- Schedule: Feature Freeze in 6 weeks (Oct 22)
- Many unclaimed issues still. Volunteer if you can!
- Richard Rodgers working on Curation code & XMLUI inteface (see branch at: http://scm.dspace.org/svn/repo/dspace/branches/dspace-curation/)
- Mark Diggory working on Async Release Process changes (see discussion on DevMtg 2010-09-01 as well as prototype at: http://scm.dspace.org/svn/repo/sandbox/dspace-async-prototype/ )
- Brief mention of Test Driven Development & Committer Polices. Some positive feedback, but needs to be voted on.
- Tim will be out of the office next week. Peter Dietz will lead meeting.
Meeting Transcript
- Full IRC Transcript available at - http://www.duraspace.org/irclogs/index.php?date=2010-09-08
Meeting Archives
Notes and Transcripts from all recent Developers Meetings are available off of the Developer Meeting Archives page.
Overview
Content Tools
All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license
, unless otherwise noted.