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 6 Next »

The root page DSPACE:Developer Meetings could not be found in space DSpace.

Meeting Schedule and Attendance

DSpace Committer 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 below), as a service for those who are unable to attend.

DSpace Committer meetings take place on the following schedule:

  • Every Wednesday at 20:00 UTC/GMT in #duraspace IRC channel (unless announced otherwise on the dspace-devel listserv)
  • 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.

Jira Cleanup Sessions

When the agenda for a meeting allows for it, occasionally a DSpace Committers meeting will begin with a quick review and cleanup of recent issues logged in DSpace JIRA. We use the following process for a quick review of JIRA issues.

The session (usually 15-30 minutes) is led by two developers:

  • A 'feeder' to copy and paste the next issue and link in, to start the review of that issue
  • A 'completer' to analyse the votes and comments at the end of the minute to draw it to a consensus

Each new issue will be introduced by the 'feeder' once the previous issue has been concluded. A new issue will be introduced in this general format:

http://jira.dspace.org/jira/browse/DS-245 - Checksum Checker reports on bitstreams which do not have "in_archive" status]

Each participant will then have approximately one minute to read that page, and decide how they think the issue should be dealt with. There are three options for voting:

  • +1: If you think the issue is important and should stay in JIRA.
  • 0: If you do not know, or are not well-enough informed about the issue
  • -1: If you think the issue should be closed. If you vote -1, please append a reason such as:
    • -1 Out of scope: If the issue is out of scope for core DSpace
    • -1 Out of date: If the issue is not now pertinent to the community
    • -1 Duplicate DS-xxx: If the issue is is a duplicate of another issue
    • -1 Won't fix: If the issue does not need fixing

If you require more time to read and understand the issue, please say 'more time'. If several people say this, the time allocated to the issue can be extended at the discretion of the 'completer'.

Please vote with a '0' rather than staying silent if you have no opinion on an issue. That way the completer knows that, rather than waiting for a vote.

Last Issue Reviewed

  • From JIRA Search (of issues created in last 6 weeks that are still "Open")

Voting Procedures

Occasionally during meetings, larger decisions need to be made or small disagreements will occur. In these cases, the DSpace Committers will attempt to come to a consensus by bringing the topic to a vote. Currently, the following voting procedures are in place, as decided unanimously by the DSpace Committers in the Spring of 2009.

The DSpace Committers follow the Apache Voting Process.

Votes can be called either during meetings or via email. There are three main votes that can be made:

  • +1 : positive, "I agree"
  • 0 : neutral, "I'm undecided, or unsure"
  • -1 : negative, "I disagree" (should always include a reason why you disagree)

In a general sense, there are three types of votes that may take place:

  1. Votes on code modifications - proposals require at least three positive (+1) votes, and no negative votes (-1) to pass
  2. Votes on a new release - proposals require a majority are in favor (and at least three +1 votes have been cast)
  3. Votes on procedural/policy changes - proposals require more positive (+1) than negative (-1) votes

Further details of some of the intricacies of these voting procedures can be found in the Apache Voting Process.

Meeting Archives

All DSpace Committer meetings and the discussions pertaining within are archived. Below is an archive of the discussions which took place during each meeting.

Old Archives

  • No labels

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