|
| 1 | +# Overview |
| 2 | + |
| 3 | +This project aims to be governed in a transparent, accessible way for the benefit of the community. All participation in this project is open and not bound to corporate affilation. Participants are bound to the project's [Code of Conduct]. |
| 4 | + |
| 5 | +# Project roles |
| 6 | + |
| 7 | +## Contributor |
| 8 | + |
| 9 | +The contributor role is the starting role for anyone participating in the project and wishing to contribute code. |
| 10 | + |
| 11 | +# Process for becoming a contributor |
| 12 | + |
| 13 | +* Review the [Contribution Guidelines] to ensure your contribution is inline with the project's coding and styling guidelines. |
| 14 | +* Submit your code as a PR with the appropriate DCO signoff |
| 15 | +* Have your submission approved by the committer(s) and merged into the codebase. |
| 16 | + |
| 17 | +## Committer |
| 18 | + |
| 19 | +The committer role enables the contributor to commit code directly to the repository, but also comes with the responsibility of being a responsible leader in the community. |
| 20 | + |
| 21 | +### Process for becoming a committer |
| 22 | + |
| 23 | +* Show your experience with the codebase through contributions and engagement on the community channels. |
| 24 | +* Request to become a committer. To do this, create a new pull request that adds your name and details to the [Committers File] file and request existing committers to approve. |
| 25 | +* After the majority of committers approve you, merge in the PR. Be sure to tag the whomever is managing the GitHub permissions to update the committers team in GitHub. |
| 26 | + |
| 27 | +### Committer responsibilities |
| 28 | + |
| 29 | +* Triage GitHub issues and perform pull request reviews for other committers and the community. |
| 30 | +* Make sure that ongoing PRs are moving forward at the right pace or closing them. |
| 31 | +* In general continue to be willing to spend at least 25% of ones time working on the project (~1.25 business days per week). |
| 32 | + |
| 33 | +### When does a committer lose committer status |
| 34 | + |
| 35 | +If a committer is no longer interested or cannot perform the committer duties listed above, they |
| 36 | +should volunteer to be moved to emeritus status. In extreme cases this can also occur by a vote of |
| 37 | +the committers per the voting process below. |
| 38 | + |
| 39 | +# Conflict resolution and voting |
| 40 | + |
| 41 | +In general, we prefer that technical issues and committer membership are amicably worked out |
| 42 | +between the persons involved. If a dispute cannot be decided independently, the committers can be |
| 43 | +called in to decide an issue. If the committers themselves cannot decide an issue, the issue will |
| 44 | +be resolved by voting. The voting process is a simple majority in which each committer receives one vote. |
| 45 | + |
| 46 | +# Communication |
| 47 | + |
| 48 | +This project, just like all of open source, is a global community. In addition to the [Code of Conduct], this project will: |
| 49 | + |
| 50 | +* Keep all communication on open channels ( mailing list, forums, chat ). |
| 51 | +* Be respectful of time and language differences between community members ( such as scheduling meetings, email/issue responsiveness, etc ). |
| 52 | +* Ensure tools are able to be used by community members regardless of their region. |
| 53 | + |
| 54 | +If you have concerns about communication challenges for this project, please contact the committers. |
| 55 | + |
| 56 | +[Code of Conduct]: CODE_OF_CONDUCT.md |
| 57 | +[Committers File]: COMMITTERS.csv |
| 58 | +[Contribution Guidelines]: CONTRIBUTING.md |
0 commit comments