137 lines (98 sloc) 9.1 KB

PowerShell Governance


  • PowerShell Committee: A committee of project owners who are responsible for design decisions, approving RFCs, and approving new maintainers/committee members
  • Repository maintainer: An individual responsible for merging pull requests (PRs) into master when all requirements are met (code review, tests, docs, and RFC approval as applicable). Repository Maintainers are the only people with write permissions into master.
  • Area experts: People who are experts for specific components (e.g. PSReadline, the parser) or technologies (e.g. security, performance). Area experts are responsible for code reviews, issue triage, and providing their expertise to others.
  • Corporation: The Corporation owns the PowerShell repository and, under extreme circumstances, reserves the right to dissolve or reform the PowerShell Committee, the Project Leads, and the Corporate Maintainer. The Corporation for PowerShell is Microsoft.
  • Corporate Maintainer: The Corporate Maintainer is an entity, person or set of persons, with the ability to veto decisions made by the PowerShell Committee or any other collaborators on the PowerShell project. This veto power will be used with restraint since it is intended that the community drive the project. The Corporate Maintainer is determined by the Corporation both initially and in continuation. The initial Corporate Maintainer for PowerShell is Jeffrey Snover (jpsnover).
  • RFC process: The "review-for-comment" (RFC) process whereby design decisions get made.

PowerShell Committee

The PowerShell Committee and its members (aka Committee Members) are the primary caretakers of the PowerShell experience, including the PowerShell language, design, and project.

Current Committee Members

Committee Member Responsibilities

Committee Members are responsible for reviewing and approving PowerShell RFCs proposing new features or design changes.

Changes that require an RFC

The following types of decisions require a written RFC and ample time for the community to respond with their feedback before a contributor begins work on the issue:

  • new features or capabilities in PowerShell (e.g. PowerShell classes, PSRP over SSH, etc.)
  • anything that might require a breaking changes as defined in our Breaking Changes Contract
  • new modules, cmdlets, or parameters that ship in the core PowerShell modules (e.g. Microsoft.PowerShell.*, PackageManagement, PSReadLine)
  • the addition of new PowerShell Committee Members or Repository Maintainers
  • any changes to the process of maintaining the PowerShell repository (including the responsibilities of Committee Members, Repository Maintainers, and Area Experts)

Changes that don't require an RFC

In some cases, a new feature or behavior may be deemed small enough to forgo the RFC process (e.g. changing the default PSReadline EditMode to Emacs on Mac/Linux). In these cases, issues marked as 1 - Planning require only a simple majority of Committee Members to sign off. After that, a Repository Maintainer should relabel the issue as 2 - Ready so that a contributor can begin working on it.

If any Committee Members feels like this behavior is large enough to warrant an RFC, they can add the label RFC-required and the issue owner is expected to follow the RFC process.

Committee Member DOs and DON'Ts

As a PowerShell Committee Member:

  1. DO reply to issues and pull requests with design opinions (this could include offering support for good work or exciting new features)

  2. DO encourage healthy discussion about the direction of PowerShell

  3. DO raise "red flags" on PRs that haven't followed the proper RFC process when applicable

  4. DO contribute to documentation and best practices

  5. DO maintain a presence in the PowerShell community outside of GitHub (Twitter, blogs, StackOverflow, Reddit, Hacker News, etc.)

  6. DO heavily incorporate community feedback into the weight of your decisions

  7. DO be polite and respectful to a wide variety of opinions and perspectives

  8. DO make sure contributors are following the contributor guidelines

  9. DON'T constantly raise "red flags" for unimportant or minor problems to the point that the progress of the project is being slowed

  10. DON'T offer up your opinions as the absolute opinion of the PowerShell Committee. Members are encouraged to share their opinions, but they should be presented as such.

PowerShell Committee Membership

The initial PowerShell Committee consists of Microsoft employees. It is expected that over time, PowerShell experts in the community will be made Committee Members. Membership is heavily dependent on the level of contribution and expertise: individuals who contribute in meaningful ways to the project will be recognized accordingly.

At any point in time, a Committee Member can nominate a strong community member to join the Committee. Nominations should be submitted in the form of RFCs detailing why that individual is qualified and how they will contribute. After the RFC has been discussed, a unanimous vote will be required for the new Committee Member to be confirmed.

Repository Maintainers

Repository Maintainers are trusted stewards of the PowerShell repository responsible for maintaining consistency and quality of PowerShell code. One of their primary responsibilities is merging pull requests after all requirements have been fulfilled.

For more information on Repository Maintainers--their responsibilities, who they are, and how one becomes a Maintainer--see the README for Repository Maintainers.

Area Experts

Area Experts are people with knowledge of specific components or technologies in the PowerShell domain. They are responsible for code reviews, issue triage, and providing their expertise to others.

They have write access to the PowerShell repository which gives them the power to:

  1. git push to all branches except master.
  2. Merge pull requests to all branches except master (though this should not be common given that masteris the only long-living branch).
  3. Assign labels, milestones, and people to issues.

Area Expert Responsibilities

If you are an Area Expert, you are expected to be actively involved in any development, design, or contributions in your area of expertise.

If you are an Area Expert:

  1. DO assign the correct labels

  2. DO assign yourself to issues labeled with your area of expertise

  3. DO code reviews for issues where you're assigned or in your areas of expertise.

  4. DO reply to new issues and pull requests that are related to your area of expertise (while reviewing PRs, leave your comment even if everything looks good - a simple "Looks good to me" or "LGTM" will suffice, so that we know someone has already taken a look at it).

  5. DO make sure contributors are following the contributor guidelines.

  6. DO ask people to resend a pull request, if it doesn't target master.

  7. DO ensure that contributors write Pester tests for all new/changed functionality

  8. DO ensure that contributors write documentation for all new-/changed functionality

  9. DO encourage contributors to refer to issues in their pull request description (e.g. Resolves issue #123).

  10. DO encourage contributors to create meaningful titles for all PRs. Edit title if necessary.

  11. DO verify that all contributors are following the Coding Guidelines.

  12. DON'T create new features, new designs, or change behaviors without following the RFC or approval process

Issue Management Process

See our Issue Management Process

Pull Request Process

See our Pull Request Process