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.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 25 Next »

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, May 5, 2010

Agenda

  • Any Announcements / Additional Agenda Items?
  • DSpace 1.6.1 Updates (Kim Shepherd)
  • DSpace 1.7.0 Scheduling (Tim Donohue)
    • No volunteer Release Coordinator has come forward
    • Proposal: As 1.7.0 is a scheduled, time-based release, we may not need a full-fledged "release coordinator". Instead of a coordinator, we could release 1.7.0 based on which features/fixes are ready & documented and have been deemed "acceptable" by the DSpace Committer Group.
      • Tim can help keep everything running on schedule as we get near release time. However, the actual "coordination" would happen amongst various ad-hoc "feature teams" (of interested developers). Those teams would have to work to meet the required schedule in order to get their proposed feature(s) into 1.7.0.
      • See the DSpace Release 1.7.0 Notes for more details on this Proposal
    • Proposed Timeline/Schedule for 1.7.0 : DSpace Release 1.7.0 Notes
  • JIRA Catch-Up – starting with issue DS-517 (and getting as far as we can).

Meeting Notes

Finalizing release schedule for 1.6.1, tentative schedule for 1.7.0, proposal to release 1.7.0 without an RC (unless one can be found)

  • Updates on 1.6.1 from Kim
    • Code Freeze: Friday, May 14
    • Release Date: Friday, May 21
    • Re-prioritized some issues – any issues/bugs not fixed by Code Freeze will need to be rescheduled for next release.
  • 1.7.0 Scheduling
    • General approval for the release schedule/timeline on DSpace Release 1.7.0 Notes
    • General approval for the "committing rules" detailed on DSpace Release 1.7.0 Notes
    • Some concerns about not having a Release Coordinator for 1.7.0 yet. But, general agreement that we need to move forward with 1.7.0 either way. If a Release Coordinator volunteer comes forward, great. Otherwise, we need to try and manage to release as a team.
    • We hope that Community Advisory Team (CAT) could potentially help handle PR announcements around 1.7.0, if a Release Coordinator is not in place to handle that PR / outreach.
    • Some concerns that a December release announcement could be "lost" or "missed" right before the holidays. Agreement that we should announce the release again in January (as a friendly reminder)

Action Items

  • Announce 1.6.1 Release Date and Tentative Release Schedule for 1.7.0

Meeting Transcript

Meeting Archives

Notes and Transcripts from all recent Developers Meetings are available off of the Developer Meeting Archives page.

  • No labels

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.