Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision |
contributing:contributors [2024/02/20 11:20] – add Stephanie as a core committer gmcharlton | contributing:contributors [2024/02/29 11:39] – [Individuals] klussier |
---|
====== 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 (formerly Subversion) [[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]]. 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 2021-03-31): | 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 2021-03-31): |
| |
| |
Inactive committers, with Git/Subversion user name. "Inactive" is defined as having last committed a patch over six months ago: | Inactive committers, with Git user name. "Inactive" is defined as having last committed a patch over six months ago: |
| |
^ Name ^ Git/Subversion user name ^ Email ^ | ^ Name ^ Git user name ^ Email ^ |
| Joe Atzberger | atz | ohiocore@gmail.com | | | Joe Atzberger | atz | ohiocore@gmail.com | |
| Thomas Berezansky | tsbere | tsbere@mvlc.org | | | Thomas Berezansky | tsbere | tsbere@mvlc.org | |
* Pasi Kallinen | * Pasi Kallinen |
* Jim Keenan | * Jim Keenan |
| * Brian Kennedy |
* Codey Kolasinski | * Codey Kolasinski |
* Bradley M. Kunh | * Bradley M. Kunh |
* Dmitry Nechai | * Dmitry Nechai |
* Alexander O'Neill | * Alexander O'Neill |
* Ben Ostrowsky | * Bee Ostrowsky |
* Bill Ott | * Bill Ott |
* Fredrick Parks | * Fredrick Parks |