Hello! We are excited that you want to learn how to get involved with the CNF Test Suite! This contributor ladder outlines the different contributor roles within the project, along with the responsibilities and privileges that come with them. Community members generally start at the first levels of the "ladder" and advance up it as their involvement in the project grows. Our project members are happy to help you advance along the contributor ladder.
Each of the contributor roles below is organized into lists of three types of things. "Responsibilities" are things that contributor is expected to do. "Requirements" are qualifications a person needs to meet to be in that role, and "Privileges" are things contributors on that level are entitled to.
You will need to gain people's trust, demonstrate your competence and understanding, and meet the requirements of the role.
Everyone is a community member! 😄 You've read this far so you are already ahead. 💯
How you can learn more?
- Read the install guide, usage guide, FAQ, and other documentation
- Request a live demonstration and introduction of the test suite (book a time on Calendly)
- Come chat with us in Slack or start a discussion
A Community Participant engages with the project and its community, contributing their time, thoughts, etc. Community participants are usually users who have stopped being anonymous and started being active in project discussions.
Responsibilities:
- Follow our Code of Conduct
How you can be more involved and participate in the community:
- Participating in community discussions
- Helping other users
- Commenting on issues
- Trying out new releases
- Attending community meetings and events
Contributors have the following capabilities:
- Have issues and pull requests assigned to you
- Apply labels, milestones and projects
- Mark issues as duplicates
- Close and assign issues and pull requests
We ask that Contributors agree to and follow this Contributing Guide.
To become a contributor, the maintainers of the project would like to see you:
- Comment on issues with your experiences and opinions
- Add your comments and reviews on pull requests
- Contribute pull requests
- Open issues with bugs, enhancement ideas, and questions
Contributors and maintainers will do their best to watch for community members who make good contributors. But don’t be shy, if you feel that this is you, please reach out to one or more of the contributors or maintainers.
Maintainers are members with extra capabilities:
- Be a Code Owner and have reviews automatically requested
- Review pull requests
- Merge pull requests
Maintainers also have additional responsibilities beyond just merging code:
- Help foster a safe and welcoming environment for all project participants This will include understanding and enforcing our Code of Conduct
- Organize and promote pull request reviews, e.g. prompting community members, contributors, and other maintainers to review
- Triage issues, e.g. adding labels, promoting discussions, finalizing decisions
- Help organize our development meetings, e.g. schedule, organize and execute agenda
To become a maintainer, we would like to see you be an effective contributor, and show that you can do some of the things maintainers do. Maintainers will do their best to regularly discuss promoting contributors. But don’t be shy, if you feel that this is you, please reach out to one or more of the maintainers.
Admins are maintainers with extra responsibilities:
- Manage repositories
- Manage CODEOWNERS file
- Manage GitHub Actions infra (eg. runners)
- Manage teams
It isn't expected that all maintainers will need or want to move up to admin. If you are a maintainer, and find yourself often asking an admin to do certain tasks for you and you would like to help out with administrative tasks, please reach out to one or more of the admins.
Former maintainers are recognized with an honorary Emeritus Maintainer status, and have their names permanently listed in the contributors file as a form of gratitude for their contributions.