| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| contributing:contributors [2024/09/04 16:25] – Congrats Ruth on your first commit! Bug1622358 klussier | contributing:contributors [2025/02/25 14:20] (current) – tmccanna |
|---|
| ====== Core Committers ====== | ====== Core Committers ====== |
| |
| Evergreen has a "core team" of experienced developers who work within the community and vet patches from other developers and each other (see: [[:contributing|How to participate in development]]). Core committers have [[:contributing:core_committer_responsibilities|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 [[dev:git|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. | Evergreen has a "core team" of experienced developers who work within the community and vet patches from other developers and each other (see: [[:contributing|How to participate in development]]). Core committers have [[:contributing:core_committer_responsibilities|additional responsibilities]] and follow a [[:contributing:core_committer_process|standard processs]]. 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 [[dev:git|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 2024-02-20): | 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 2024-02-20): |
| | Blake Graham-Henderson | Bmagic | blake@mobiusconsortium.org | MOBIUS | | | Blake Graham-Henderson | Bmagic | blake@mobiusconsortium.org | MOBIUS | |
| | Stephanie Leary | sleary | stephanie.leary@equinoxOLI.org | Equinox Open Library Initiative | | | Stephanie Leary | sleary | stephanie.leary@equinoxOLI.org | Equinox Open Library Initiative | |
| | | Tiffany Little | tlittle | tlittle@georgialibraries.org | Georgia Public Library Service | |
| | Terran McCanna | terranm | tmccanna@georgialibraries.org | Georgia Public Library Service | | | Terran McCanna | terranm | tmccanna@georgialibraries.org | Georgia Public Library Service | |
| | Michele Morgan | mmorgan | mmorgan@noblenet.org | NOBLE | | | Michele Morgan | mmorgan | mmorgan@noblenet.org | NOBLE | |
| * Chris Sharp | * Chris Sharp |
| * Benjamin Shum | * Benjamin Shum |
| | * Ian Skelsky |
| * Remington Steed | * Remington Steed |
| * Jason Stephenson | * Jason Stephenson |
