s434730/RandomSec
3
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

clarify role and list of committer

Browse Source
This commit is contained in:
Martin Magdinier 2018-11-19 20:18:05 -05:00 committed by GitHub
parent 4a6c430b48
commit 66c4706ca4
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
GOVERNANCE.md
View File

@ -40,7 +40,7 @@ Therefore committers:
- Have direct access to the code base - Have direct access to the code base
- Nominate and vote for new committers - Nominate and vote for new committers
Committers also participate in strategic planning, release planning, and approving changes to the governance model. Committers participate in the Project Management Committee (PMC). They engage in strategic planning, release planning, and approving changes to the governance model. The list of committers is available here: https://github.com/orgs/OpenRefine/people
How to become an OpenRefine Committers? Be a contributor and be nominated as a committer. OpenRefine selects and elects new committers using the [Apache model](https://community.apache.org/newcommitter.html). You may nominate yourself. Nomination should be sent to the [developer discussion list](https://groups.google.com/forum/?fromgroups#!forum/openrefine-dev) How to become an OpenRefine Committers? Be a contributor and be nominated as a committer. OpenRefine selects and elects new committers using the [Apache model](https://community.apache.org/newcommitter.html). You may nominate yourself. Nomination should be sent to the [developer discussion list](https://groups.google.com/forum/?fromgroups#!forum/openrefine-dev)