Standards for evaluating a potential Committer to the Apache Superset project
There are several ways to be a contributor to the Superset project and its surrounding community. While special exceptions may apply (see below) the general standards for Committers are based on code contributions and related involvement. Potential Committers will be held to these standards when put up for a [VOTE] thread on the private@superset.apache.org mailing list, as is standard Apache procedure.
- A track record of at least six months since their first commit was merged.
- A history of either significant code contribution volume AND/OR significant contribution impact.
- Quality code contributions that are simple, well-tested, and well-designed patches.
- An apparent or stated intent to contribute to the Superset project in an ongoing manner, in order to help represent, guide, and grow the Superset project and its developer community.
- Generally provides and promotes civil discourse and constructive conversations, acting in a helpful and diplomatic capacity in community conversations.
- Ongoing, supportive engagement in the Superset community's various fora (Mailing list, Github, Slack, etc.)
- A history of improving engineering best practices via documentation, tests, style guidelines, etc.
- A history of reviewing PRs, demonstrating adherence to best practices, and seeking to promote stability and maintainability.
- A history of responding to Issues in a constructive manner to either resolve them directly or help steer them on a path toward resolution.
- Testing and voting on releases
- Participation in discussions about roadmaps, architecture, developer experience, and long-term plans
- Assistance in improvements to the website, documentation, and the wiki
- Participation in community events such as meetups, talks, etc
- Improve project infrastructure in order to increase the efficiency of committers and other contributors
On a case-by-case basis, committership (i.e. write access to the Github repo) may be warranted for individuals who may not meet the above code contribution standards, but instead will be considered on the basis of other community-driven qualifications. The granularity of repo permissions currently is limited, meaning those who wish to help triage and manage Issues, Discussions, Projects, labels, and other parts of day to day repo operations, cannot be given those capabilities unless they are made a Committer. These contributors may provide sufficient merit via other efforts including (but not limited to) input on Design and Product decisions involving the community, driving issues and questions toward resolution on the mailing list, Slack and other fora, verifying release candidates, giving talks, organizing community events, and other forms of evangelism and community engagement. Superset, like all Apache projects, has a strong focus on the project community, and Committers may be considered for this merit when being put forth in a nomination on the mailing list.
Additions or revisions may be made to the above guidelines by making a proposal seeking lazy consensus to the dev mailing list, and applying any agreed-upon changes to this wiki page.
