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 public 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 Slack, Mailing Lists, IRC, 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 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:
- Pascal-Nicolas BECKER - Technische Universität Berlin / The Library Code
- Andrea BOLLINI - 4Science
- Ben BOSMAN - Atmire
- Terry BRADY - Georgetown University
- Tom DESAIR
- Mark DIGGORY - Atmire
- Tim DONOHUE - DuraSpace (Project Tech Lead)
- Claudia JÜRGEN - University Library of Dortmund
- Art LOWEL - Atmire
- Bram LUYTEN - Atmire
- Ivan MASÁR (aka helix84)
- Luigi Andrea PASCARELLI - 4Science
- Hardy POTTINGER - UCLA Library
- Andrea SCHWEER - University of Waikato ITS
- Kim SHEPHERD - http://shepherd.nz/
- Robin TAYLOR - University of Edinburgh
- Kevin VAN DE VELDE - Atmire
- Mark WOOD - Indiana University-Purdue University Indianapolis
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.
- Peter DIETZ - (previously at Longsight)
- Jim DOWNING - (previously at University of Cambridge)
- Sands FISH - (previously at MIT libraries)
- Keith GILBERTSON - Virginia Tech University Libraries
- Richard JONES - Cottage Labs
- Stuart LEWIS - University of Edinburgh (previously at University of Auckland)
- Brad MCLEAN - (previously at DuraSpace)
- João MELO - Lyncode
- Gabriela MIRCEA - University of Toronto
- Scott PHILLIPS - (previously at Texas Digital Library)
- Richard RODGERS - (previously at MIT Libraries)
- James RUTHERFORD - (previous at HP)
- Kostas STAMATIS - The National Documentation Centre (EKT)
- Larry STONE - Harvard University
- Keiji SUZUKI
- Robert TANSLEY - Google
- Graham TRIGGS - (previously at Symplectic)
- Jeffrey TRIMBLE - Youngstown State University
- Scott YEADON - The Australian National University
- Aaron ZECKOSKI - Unicon
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.