Skip to content

Latest commit

 

History

History
41 lines (23 loc) · 2.45 KB

GOVERNANCE.md

File metadata and controls

41 lines (23 loc) · 2.45 KB
Raw

Project Governance

The development and community management of the project will follow the governance rules described in this document.

Project Maintainers

Project maintainers have admin access to the GitHub repository. The team of project maintainer is the following:

1. Roles

This project includes the following roles.

1.1. Maintainer. Maintainers are responsible for organizing activities around developing, maintaining, and updating the Project. Project maintainers will review and merge pull requests.

1.2. Collaborator. Any member willing to participate in the development of the project will be considered as a collaborator. Collaborators may propose changes to the project's source code. The mechanism to propose such a change is a GitHub pull request. A collaborator proposing a pull request is considered a contributor.

2. Issue governance

2.1. Both collaborators and project maintainers may propose issues. The participation in the issue discussion is open and must follow the Code of Conduct.

2.2. The group of project maintainers will be responsible for assigning labels to issues, as well as assign the issue to a project maintainer or contributor.

2.3. The group of project maintainers commit to give an answer to any issue in a period of time of 48 hours.

3. Pull Request governance

3.1. Both collaborators and project maintainers may propose pull requests. When a collaborator proposes a pull request, is considered contributor.

3.2. Pull requests should comply with the template provided. The assignment of labels and assignees to the pull request is the responsibility of the project maintainers.

3.3. The group of project maintainers commit to give an answer to any pull request in a period of time of 48 hours.

3.4. The decision of accepting (or rejecting) a pull request will be taken by the group of project maintainers. The decision will be based on the following criteria:

  • Two project maintainers must approve a pull request before the pull request can be merged.
  • One project maintainer approval is enough if the pull request has been open for more than 14 days.
  • Approving a pull request indicates that the contributor accepts responsibility for the change.
  • If a project maintainer opposes a pull request, the pull request cannot be merged (i.e., veto behavior). Often, discussions or further changes result in collaborators removing their opposition.