Page tree
Skip to end of metadata
Go to start of metadata

DSpace Committers Group

DSpace Committers have autonomous control over the code and are also the primary support team for DSpace. The primary responsibilities of Committers are:

  • Maintain the codebase; Committers are the only individuals who can actively change/commit to the codebase
  • Review all code contributions/changes to ensure stability, etc
  • Merge/accept community code contributions
  • Help to resolve bugs or security issues within codebase
  • Help to provide ongoing support to community developers and users (via IRC, mailing lists, etc.)
  • Perform and manage new releases based on the roadmap.

Anyone may be nominated as a Committer by anyone else. Typically, nominations are made by existing Committers on the basis of sustained contribution to DSpace that indicates an ability to fulfill Committer responsibilities. Examples of such contribution are participation in discussions on the DSpace mailing lists, IRC etc, participation in developer meetings, reporting bugs, help with testing, and contribution of code via pull requests. Only existing Committers may vote to add a nominated person to the Committers group.

Committers

The following individuals are current Committers for DSpace open source software:

Emeritus Committers

Emeritus Committers are those who, for one reason or another, are no longer able to contribute code or time to DSpace on a regular basis. They are still members of the Committers Group, but are currently acting in an advisory role within the DSpace development community. As such, while Emeritus Committers may participate in active votes, their votes are considered advisory in nature.

We wish to recognize the contributions each of these individuals has made to DSpace software over the years. Their code contributions and guidance have played an integral part in helping to make DSpace what it is today.

Committer Discussions / Meetings

As much as possible, Committers ensure that all DSpace technology decisions are transparent to the developer community. (The only exception is when security issues require us to resolve them before they are publicly reported)

  • All Developer Meetings are open to anyone to attend. The meeting minutes are automatically logged and publicly available.
  • Technology discussions take place in the following places:
    • Weekly developer meetings
    • dspace-devel Mailing List
    • DSpace Issue Tracker (When discussion is related to a specific ticket. NOTE: You can subscribe to all ticket updates via the dspace-tickets mailing list.)
    • GitHub (When discussion is related to a specific GitHub pull request)
    • Occasionally on the Wiki itself, if a feature/change is just being proposed for early feedback.
  • All technology decisions are made following our Developer Voting Procedures.
  • No labels