DSpace Committers have autonomous control over the code and are also the primary support team for DSpace. The primary responsibilities of Committers are:
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 mailing lists, Slack, IRC etc, participation in developer meetings, reporting bugs, help with testing/reviewing of code, and contribution of code via pull requests. A majority of current Committers must approve any nominations to the Committers group.
The following individuals are active Committers for DSpace open source software:
DSpace committers attending the Open Repositories Conference 2018 in Bozeman, MT.
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.
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)