We welcome additional contributors to Minder, including maintainers. Minder currently has a two-tier contributor structure:
Role | Description | Privileges |
---|---|---|
Contributor | Anyone who participates in the project! | Send / update PRs |
Maintainer | Consistent contributors who have shown commitment to the project | Review and merge PRs, manage issues |
See CONTRIBUTING.md for a description of how to get started contributing to Minder.
To become a maintainer, you must meet the following criteria:
- Account Security
- Must have enabled two factor authentication on their GitHub account
-
Demonstrated Contribution:
- Have made multiple significant contributions to Minder's GitHub
repositories. This can include:
- PR contributions to at least one Minder subystem
- PR reviews of at least one Minder subsystem
- Documentation and issue triage
- Have made multiple significant contributions to Minder's GitHub
repositories. This can include:
-
Sponsorship:
- Sponsored by at least one existing maintainer.
Maintainers
As a maintainer, you will have the following responsibilities:
-
Code Review and Merging:
- Review pull requests for quality, correctness, and alignment with the
project direction.
- When in doubt, assign pull requests to subject matter experts in the relevant subsystem.
- Merge reviewed pull requests when satisfactory.
- Review pull requests for quality, correctness, and alignment with the
project direction.
-
Set Technical Direction:
- Where appropriate, participate in authoring and reviewing technical design
documents.
- Note: many project documents are currently in the Stacklok Google Drive instance. We are working to open the relevant documents for community review and feedback.
- Where appropriate, participate in authoring and reviewing technical design
documents.
See https://github.com/mindersec/community/tree/main/MAINTAINERS.md for the current list of maintainers.