One Of The Team¶
The Hyper project is interested in fostering as much community as possible, to encourage people interested in HTTP and HTTP/2 to get involved and get their hands dirty.
For that reason, the Hyper project has a policy: if you have made a commit to any of the Hyper sub-projects, you are automatically entitled to be made a member of the GitHub organisation: specifically, the contributors team. This team is empowered to create branches, merge pull requests, close bug reports, and generally to get involved with the ongoing maintenance of all of the hyper projects.
Membership of this team is not mandatory: if you’re not interested in being a part of the project, that’s totally ok! Additionally, if you become a member but later decide you aren’t interested, that’s fine too: you don’t owe us any of your time.
However, if you want a corner of the open source ecosystem to feel at home, we want you to feel that way here. You should get as involved as you feel comfortable with.
Becoming a contributor grants you quite a lot of power: in particular, you can merge pull requests and close bug reports. These can potentially give mischievous or malicious individuals the ability to cause a great deal of annoyance for everyone else.
That’s not a reason not to share these powers: we believe our community is full of reasonable people who care about working well together. However, it does mean we need to provide some guidance about how to work together.
Here is what we expect of our contributors:
Please don’t merge pull requests unless a maintainer or administrator has OK’d the change. We want to work as a team, but the maintainers are responsible for the ‘spirit’ of the project, and often have a better understanding of its needs than new contributors.
Please don’t merge your own pull requests. Code review is important, and skipping it is bad.
You need to follow our code of conduct, as outlined in our Contributing policy.
Contributors who repeatedly fail to meet these three points will have their contribution privileges removed. The goal here is to build a team of people who work together to a common end: people who aren’t interested in that will need to find a home elsewhere.
If you establish a record of valuable contribution and an understanding of the workflow involved with the Hyper project, then you may be made a sub-project maintainer. These members have additional authority over their sub-projects: specifically, they are able to push directly to the master branch and to manage the permissions of other contributors to their repository.
Maintainers have more authority to go along with their record of contribution, and also have more responsibility for the continued good health of their project. Good maintainership is a vital part of the ongoing health of these sub-projects: it’s the most important role in any open source project.
Maintainers are expected to be familiar with our Contributing policy and our Security policy, as they’ll be responsible for enforcing those policies. They’re also responsible for ensuring that as many of the contributors as possible feel like they’re making important contributions. Maintainers are stewards of culture, as much as they are of code.