Anyone may be nom=
inated as a Committer by anyone else. Typically, nominations are made b=
y existing Committers on the basis of sustained contribution to DSpace that=
indicates an ability to fulfill Committer responsibilities. Examples of su=
ch contribution are participation in discussions on mailing lists, Sla=
ck, IRC etc, participation in developer meetings, reporting bugs, help with testing/reviewing of co=
de, and contributi=
on of code via pull requests. A majority of current Committers must app=
rove any nominations to the Committers group.

Emeritus Committers

Emeritus Committers are those who, for one reason or another, are no lon=
ger 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 advis=
ory role within the DSpace development community. As such, while Emeritus C=
ommitters may participate in active votes, their votes are considered advisory in nature. =

We wish to recognize the contributions each of these individuals ha=
s made to DSpace software over the years. Their code contributions and guid=
ance have played an integral part in helping to make DSpace what it is toda=
y.

Committer Discu=
ssions / Meetings

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

Contributors

This is a list of all known general contributors to DSpace software. The=
se people and institutions have contributed to at least one version of DSpa=
ce. Contributions may have been in the form of: reporting a bug, fixing a b=
ug, providing a new feature, helping with documentation, or otherwise contr=
ibuting to the software product.