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 59 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. If you are unsure how to connect to IRC, see our list of IRC Resources & Clients

This meeting schedule is also available via the DuraSpace Public Events Calendar (iCal, RSS Feed).

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, February 2, 2011

Agenda

  • 1.8.0 Release Discussion
    • Discuss whether we want to switch to a new version numbering scheme for 1.8? Past suggestions include:
      • Drop the "1.", so that "1.8" would be "DSpace 8" (This is similar to Java, where 1.6 is also called Java 6)
      • Change release number to be based on release date, so Oct 2011 release would be numbered 11.10 (YY.MM) – this is similar to Ubuntu Release numbers
      • Other ideas? Or, do we just stick with "1.8" for now?
  • Next Week (Feb 9) - Special Topics Meeting on git / DCVS, led by Peter Dietz
    • (NOTE: Tim may be unable to attend, as he'll be at code4lib conference. It all depends on wireless stability at the conference.)
  • Other ideas for upcoming "Special Topics" Meetings
    • Discuss improving how DSpace handles Metadata (From past meetings discussions, this seems popular). Several ideas mentioned recently:
      • Updating to current DCMI standards: DS-805
      • Creating a new "dspace" internal usage schema (for administrative, or non-DC metadata)? Formalize the "dc" schema to be strictly valid QDC/DC?
      • Metadata on all DSpace objects (not just Items)
    • Discuss forming a "Documentation Management Team"? Or reworking our procedures for managing/reviewing/approving Docs on the Wiki.

Meeting Notes

Collaboration with DCAT group, Release Numbering Discussions, Jira Review

  • JIRA Review, ended with DS-676
  • Discussion of Proposal for a New "Feature Request" Review Process / Collaboration with DCAT
    • Most in attendance seemed to be generally in favor of this proposal
    • Suggestions of finding ways for DCAT to help "pool resources" (how is up for discussion)
    • See the full transcript below for details of discussion.
  • Discussion of Version Numbering for DSpace.
    • Talked about the two initial proposals for changing numbering (see above: "dropping the "1.", and a YY.MM numbering scheme)
    • Overall, there was no definitive majority in favor of any new numbering scheme. So, by default, we will continue to call the next version "1.8". If in the future we change our minds (and reach a majority), we can always announce a numbering change.
    • Thoughts on Version Numbering wiki page created, where individuals can add their proposals for why we may or may not want to change our version numbering. Anyone is welcome to add suggestions there. This may eventually be posted to mailing lists for more comments / ongoing discussion.
  • Next Week (Feb 9) - Special Topics Meeting on git / DCVS, led by Peter Dietz

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.