semver
/
semver
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Spell out the list of maintainers 

The @semver/maintainers team member list is not publicly displayed even though the team is public. It's only public to members of the org. This PR spells out the list of members and their affiliations.
master
Phil Haack 2019-02-11 09:29:51 -08:00 committed by GitHub
parent 694701e999
commit 5809cd382e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 10 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
CONTRIBUTING.md
View File

@ -23,7 +23,16 @@ all team members (see below) to merge.
We welcome feedback from anyone on the direction of SemVer. However, a group of people, "the SemVer team," are responsible for making decisions about RFC PRs. The SemVer team is made up of representatives from package managers that use SemVer.
Team members are added and removed based on the consensus of the existing team members. The [@maintainers](https://github.com/orgs/semver/teams/maintainers) team on GitHub contains the official list of the members of "the SemVer team."
Team members are added and removed based on the consensus of the existing team members. The @maintainers team on GitHub contains the official list of the members of "the SemVer team."
The maintainers are:
* anangaur (NuGet)
* dherman (Notion)
* indirect (Bundler)
* isaacs (NPM)
* segiddins (CocoaPods)
* steveklabnik (Cargo)
## Participation commitment
@ -34,7 +43,6 @@ Participation in the SemVer governance process requires a commitment to maintain
* With the understanding that implementation may present challenges and require time to complete, refusal on principle to implement approved RFCs will result in removal from the group.
* Implementations may add functionality in advance of an approved RFC (in fact, they have to!) but all such functionality must be flagged as "experimental", so that users understand it may change in the future. (Maintainers are encouraged to perform these experimental changes on forks rather than the implementation in use by their package management communities, to reduce the chance of users coming to rely on experimental functionality.)
## The lifecycle of an RFC
Once a PR is tagged as an RFC: