-
Notifications
You must be signed in to change notification settings - Fork 17
Committer Approvement Process
This page documents the process of electing and approving a new committer.
The committer is proposed by an existing committer and elected according to the openECTS Development process. The project lead notifies the project office about the new committer, including the following information:
- Full name
- Affiliation
- Github Account
- Reason for nomination
- Existing contributions to the projects (e.g. bug report numbers)
- +?
The project office checks if the committer nomination follows the rules and goals of the openECTS Development process, especially in terms of transparency, openess and diversity. The project office reviews the gitHub account of the committer, the account should contain the full name and the affiliation. The project office gets aprovement for the new committer by the representative of the PMB.
The project office sends the committer agreement to the committer and receives the signed version of it.
The project office:
- Checks if the committer has joined the project's mailing list and adds him/her otherwise
- Adds the committer to the internal committer database (including all provided information from step 1)
- The project office grant write access to the project's repository
- The project office notifies the committer about the approvement