Pants community Maintainers are contributors who have been recognized by the project as stewards of Pants. They have a proven record of contributions, are committed to ensuring the continued success of our project, and through their actions help to grow our Community.
Maintainers are the core group of trusted people with a long-term interest in Pants, who have made regular contributions for some time, and plan to continue to do so. Maintainers are entrusted to make decisions on the future and direction of Pants. In doing so, it is their responsibility to uphold the health, culture, and quality of the project.
We do not expect a minimum commitment of time from Maintainers, nor do we expect maintainers to contribute in specific ways, rather, we expect them to act in a way that makes Pants better whenever they interact with the project and our community.
Every Maintainer contributes to the health of Pants in ways that are valuable. We don't need each Maintainer to do all of the things needed to sustain the project, as long as we collectively have those skills. If your track record as a Contributor includes any of the following, you will be valuable as a Maintainer, and you do not need to change how you contribute to the project unless you enthusiastically choose to do so.
Maintainers shape the features and capabilities of Pants, and how we present and explain them to our users:
- They approve code and documentation changes from other maintainers and contributors, especially in their area of expertise
- They ensure the contributions they approve meet our project's quality standards
Maintainers set the direction for the future of Pants:
- They participate in Pants' design process, offering their expertise and opinions when appropriate, or if they are called upon
- They understand the current and future needs and goals of the project, and provide informed context that justifies accepting or rejecting a proposal
- They contribute expertise in an important area of concern for the project; for example, performance, security, maintainability, product management, user experience, documentation, or open source governance
Maintainers set the tone and establish the culture of the Pants Community, and foster its growth:
- They are welcoming when they interact with current and prospective members of the community
- They maintain a courteous and professional demeanor when participating in the community, upholding the standards set in our Code of Conduct
- They help steward changes through our contribution process, especially by helping new contributors identify where changes fit into Pants, or by giving context for why certain features do not, or should not exist
- They are active participants in one or more of our communication channels as they are able, or as they are called on
- They help sustain the project's long-term growth and sustainability by seeking ways to make contributing to the project more enjoyable, engaging, and educational for others
Most Maintainers perform the role as a volunteer commitment, without direct support from their employer. We understand everyone's availability can vary from day to day, and that we can't really make demands on your time. We appreciate the generosity you are able to show to the project, and value what you bring to it.
We expect Maintainers to be able to answer questions about their areas of expertise as they are called upon. If you are unable to respond to a question in a timely manner, we'd appreciate it if you could make that clear, so someone else can offer help, or a decision can be made in your absence.
If there are demands on your time that prevent you from participating in the Pants community, that's OK! We can usually cope with this, especially if you can let other maintainers know in advance. That way, we can prioritize work that you might have otherwise taken on, and ensure there isn't a daunting pile of issues and pull requests awaiting you when you return.
If you no longer feel that you are able to contribute effectively as a maintainer, you may request to be converted to a Maintainer Emeritus.
Some maintainers also accept responsibility for being on the Maintainer of the Week (MOTW) rotation, which has three main responsibilities, in no particular order:
- Shepherding the week’s releases:
- This includes updating the release documentation, creating release builds, and stewarding them through the review, as well as flagging (not necessarily fixing) any problems
- This will typically involve one dev release from
main, and possibly one or more release candidates or stable releases (feel free to ask in #development for guidance on which releases).
- Greeting newcomers on the #welcome channel in Slack:
- The same script can be copy-pasted once or twice per week, depending on the number of newcomers.
- Triaging incoming GitHub PRs, issues and discussions. This includes:
- Ensuring that PRs have a
- Approving CI runs for first-time contributors.
- Assigning code reviewers for incoming PRs if not done so by the author.
- Responding to issues and/or assigning them to appropriate owners.
- Ensuring that approved PRs are merged, if the author isn’t a Maintainer and so doesn’t have merge permissions.
- Ensuring that PRs have a
The MOTW will also make a best-effort attempt to ensure that questions on Slack are responded to by someone. The MOTW is not personally expected to respond to every question thread, but to make sure things don’t fall through the cracks.
The MOTW rotation is opt-in, and a maintainer is not required to join it, although we do encourage this. Please ask for help with any part in #development or #maintainers-confidential
The MOTW rotation is managed on a dedicated Google calendar.
Maintainer candidates are nominated by existing Maintainers from among the wider contributor base. Criteria for nomination include:
- Candidate has a record of good contributions to Pants
- Candidate has a record of collaboration with Pants community members
- Candidate understands the principles described on this page
- Candidate is committed to upholding Pants community standards, including the Code of Conduct
Candidates will only be publicly nominated after one Maintainer has determined they are willing to become a Maintainer.
If a contributor has been nominated, and is willing to become a Maintainer, then their candidacy will be discussed and voted on by the existing Maintainers.
New maintainers should be:
New Contributors should be:
Updated 30 days ago