This document describes the responsibilities, permissions and criteria for membership for each of the Teams associated with the pandas project. The Teams are:
- Core library Team
- pandas-stubs Team
- Finance Team
- Infrastructure Team
- Documentation Team
- Code of Conduct Team
- Triage Team
- Contributor Community Team
- Website Team
- Outreach Team
Individuals may be on more than one Team. If it is difficult to find enough people for any particular Team, the Steering Committee may assign the responsibilities of that underserved Team to another Team.
- Maintain and develop the pandas library (the https://github.com/pandas-dev/pandas/ repository)
- Review and Approve or Reject Pull Requests
- Current guidelines on merging PRs: https://pandas.pydata.org/docs/dev/development/maintaining.html#merging-pull-requests
- Finalizes Releases of the pandas library
- Has permission to merge anything to the main branch of the pandas repository
- Only Team with PDEP voting rights
- New Members are nominated after a period of sustained and qualitative contributions
- Joining heuristic: "is there some aspect of pandas where we trust this person to get something in without anyone's help?".
- An existing Member of the Team proposes to promote a new member
- https://pandas.pydata.org/docs/dev/development/maintaining.html#becoming-a-pandas-maintainer
- Maintenance of
pandas-stubs
repository (https://github.com/pandas-dev/pandas-stubs)- Triage of issues
- Reviews of pull requests
- Merges
- Releases
- Delegated to 2 or 3 members
- Only Team with permission to merge to the main branch of the pandas-stubs repository
- New Members are nominated after a period of sustained and qualitative contributions
- Joining heuristic: "is there some aspect of _pandas-stubs _where we trust this person to get something in without anyone's help?".
- An existing Member of the Team proposes to promote a new member
- Manage Applications for Grant Proposals for Funding
- Approve Project Expenses
- Ensure that finances are effectively used
- Find funding opportunities from appropriate, ethical sources
- No specific technical permissions
- Permissions to make all financial decisions on behalf of the Project
- Determines rates for any paid contributors
- Member of one Team for at least three years
- Unanimous Approval of Steering Committee
- Limited to 5 Members
- Keep the pandas infrastructure up and working, including the servers for the website, benchmarks, CI and others as needed.
- Build and Distribute Releases of the pandas library
- Decisions on platform support
- Manage the 1Password repository
- Usernames and Passwords for various servers
- New Members are nominated after a period of sustained and qualitative contributions
- Joining heuristic: "is there some aspect of the infrastructure where we trust this person to manage that part of the infrastructure without assistance?".
- An existing Member of the Team proposes to promote a new member
- Maintain the pandas documentation and its (building, e.g. Sphinx) infrastructure
- Permission to merge to the main branch of the pandas repository, with the criteria that it is a DOC only PR.
- New Members are nominated after a period of sustained and qualitative contributions to the documentation
- Make sure the pandas community is a welcoming and inclusive community.
- Keeping the Code of Conduct (https://pandas.pydata.org/community/coc.html) updated
- Addressing reports of violations of the Code of Conduct
- Administering the Code of Conduct
- At most one Member of another Team can be on the Code of Conduct Team
- Volunteers from the Community are welcome
- Approval by the Steering Committee
- Help triage issues on the pandas repository (respond to new issues, verify reproducibility and ensure a clear description, …)
- “Triage” permissions for the pandas repository (ability to manage issues without write access)
- New Members are nominated by a Core Library Team member after a period of sustained and qualitative contributions
- Support and enable Individual Contributors to make contributions to the Project
- Encourage continued contributions from Individual Contributors so that they become future members of Teams
- Lead Biweekly New Contributor Meetings
- Organize sprints
- No special permissions exist for this team
- At least 2 members of the Core Library Team should be on this team
- Appointed by the Core Library Team
- Maintain the website; in particular:
- The active maintainers
- The institutional partners and sponsors of the project
- The advertised books
- Design and technical implementation
- At least two Stewards should be on this team.
- Joining heuristic: Would you trust this person to make decisions about the pandas website?
- Permission to merge to the main branch of the pandas repository, with the criteria that it is a WEBSITE only PR.
- Login credentials for the web server
- Announce new pandas releases on social channels
- Announce other pandas-related news, such as:
- Recurring meetings
- Events (such as sprints)
- Blog posts (related to pandas) by pandas members
- Keep communication on-topic. It doesn’t all have to be completely serious, but it should be on-topic - let’s not use the social accounts for political soapboxing
- Be respectful of other projects: open source, closed source, etc…they all have real humans behind them
- Usernames and Passwords for various social accounts
- Twitter/X account
- Mastodon account
- LinkedIn group management