Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Section
Column
width30%
Panel

Table of Contents

Page Tree
rootDSPACE:Developer Meetings
searchBoxtrue
Column
width70%
Table of Contents
outlinetrue
stylenone
excludeTable of Contents

Meeting Schedule and Attendance

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

DSpace Committer Developer 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.

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.