Evergreen has a "core team" of experienced developers who work within the community and vet patches from other developers and each other (see: How to participate in development). Core committers have additional responsibilities. Some of these people work for commercial companies, some work directly for libraries, and some are simply volunteers. This team has write access to the official(*) Git (formerly Subversion) repository containing the Evergreen source code and its history, yet others are able to clone and maintain their own branches of the software. For software to be open source software, anyone with the code must be allowed to use, modify, and distribute it, but that does not mean its users are subject to the whim of others. Ultimately, it is the community as a whole that determines what Evergreen is, what goes into it, and who the committers are.
The list of active committers with Git user name and current affiliation. "Active" is defined as committing code within the last six months (last updated 2015-11-09):
|Name||Git user name||Email address||Affiliation|
|Galen Charltonemail@example.com||Equinox Open Library Initiative|
|Bill Ericksonfirstname.lastname@example.org||King County Library System|
|Jason Etheridgeemail@example.com||Equinox Open Library Initiative|
|Jeff Godinfirstname.lastname@example.org||Traverse Area District Library|
|Mike Rylanderemail@example.com||Equinox Open Library Initiative|
|Dan Scottfirstname.lastname@example.org||Laurentian University / CoffeeCode Consulting|
|Jason Stephensonemail@example.com||Independent / CWMARS / Merrimack Valley Library Consortium|
|Dan Wellsfirstname.lastname@example.org||Calvin College|
Inactive committers, with Git/Subversion user name. "Inactive" is defined as having last committed a patch over six months ago:
|Name||Git/Subversion user name||Affiliation|
|Thomas Berezanskyemail@example.com||Merrimack Valley Library Consortium|
* A note on the word "official": Evergreen is currently trademarked by the Software Freedom Conservancy, which controls the name "Evergreen". The copyrights are spread amongst many people and organizations. Because the software is open source, it may be "forked" by others as long as they do not use the trademark without permission.
The following individuals have contributed at least one patch to Evergreen and/or OpenSRF. Patches include bug fixes, new functionality, and translations.
Note: this list was compiled from the commit logs on the trunk branches of Evergreen and OpenSRF, so any patches that were made to one of the version branches (e.g., rel_1_4) but not forward ported for some reason are not included. If you contributed a patch that was committed to Evergreen and your name was not listed, feel free to edit this page.
The Documentation Interest Group roster lists the contributors to the official Evergreen documentation effort.
In addition, there are many contributors to the Evergreen wiki, for which we unfortunately don't have a good way of automatically generating a listing.