Contributor access

For people who make the occasional contribution to Flutter (filing an issue, submitting the occasional PR), the default set of permissions is fine. However, if you are a frequent contributor, whether helping us in triage, or often fixing bugs, or regularly improving our documentation, you may find your life is more pleasant with commit access (also know as "contributor access", "being a member of the flutter-hackers group", "being a member of the Flutter team").

We grant commit access (which includes full rights to the issue database, such as being able to edit labels) to people who have gained our trust and demonstrated a commitment to Flutter.

Specifically, if you meet one of the following criteria and you have a sponsor (someone who already has contributor access and agrees that you should be granted access), then please ask on the #server-support chat channel if you can be made a member of the team. The possible criteria are:

• You have submitted several PRs that have landed successfully (received an LGTM, PR was merged, no regressions reported, PR was not reverted).
• You have a history of participating productively in our chat channels, helping with Triage, helping other contributors track down problems, finding meaningful issues in submitted PRs.
• You are employed by a company with a history of contributing to Flutter, for the purpose of yourself regularly contributing to Flutter.
• You represent a development team that creates applications, plugins, or packages using Flutter and have a close relationship with our developer relations team, including having a customer label (see Issue hygiene, Customers).

Being granted access means that you will be added to the "flutter-hackers" group on GitHub and the "team" role on Discord. This privilege is granted with some expectation of responsibility: contributors are people who care about Flutter and want to help Flutter along our roadmap. A contributor is not just someone who can make changes or comment on issues, but someone who has demonstrated their ability to collaborate with the team, get the most knowledgeable people to review code, contribute high-quality code, follow through to fix bugs (in code or tests), and provide meaningful insights on issues.

We grant access optimistically based on a reasonably small volume of evidence of good faith. Correspondingly, we will remove access quickly if we find our trust has been violated. Contributors with commit access must still follow all our processes and policies, and must follow our code of conduct rigorously. (Please read it, it's stricter than most.)

Privileges

Being in the GitHub "flutter-hackers" group gives you the following:

• The ability to merge your own PRs once they are reviewed (see Tree Hygiene).

• The ability to add labels, milestones, etc, on issues on GitHub (see Issue Hygiene).

• PRs will run their tests slightly faster.

Being in the Discord "team" group gives you the following:

• The ability to talk without rate-limiting on the #hackers-* channels.

• The ability to kick people.

• The ability to manage the server emoji.

Process

The actual process (as followed by Flutter repo admins) is as follows:

1. Verify the identity of the person making the request.
2. Verify that they qualify under all the terms described above. If you know them, you can be their sponsor, otherwise, make sure they have one.
3. Click the "Add a member" button on the flutter-hackers team page on GitHub.
4. Type their name in the text field, select them, then click the "Invite" button.
5. If they are on Discord, add them to the "team" group there too. Be sure to verify that you are promoting the right person; multiple people can have the same nickname on Discord!