"Fossies" - the Fresh Open Source Software Archive
Member "PowerShell-7.2.6/docs/maintainers/README.md" (11 Aug 2022, 6854 Bytes) of package /linux/misc/PowerShell-7.2.6.tar.gz:
As a special service "Fossies" has tried to format the requested source page into HTML format (assuming markdown format).
Alternatively you can here view
the uninterpreted source code file.
A member file download can also be achieved by clicking within a package contents listing on the according byte size field.
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.
They have write
access to the PowerShell repositories which gives them the power
git push to the official PowerShell repository
- Merge pull
- Assign labels, milestones, and people to issues and pull
Table of Contents
Repository Maintainers enable rapid contributions while maintaining a
high level of quality in PowerShell by ensuring that all development
processes are being followed correctly.
If you are a Repository Maintainer, you:
- MUST ensure that each contributor has signed a
valid Microsoft Contributor License Agreement (CLA)
- MUST verify compliance with any third party code
license terms (e.g., requiring attribution, etc.) if the contribution
contains third party code.
- MUST make sure that any change
requiring approval from the PowerShell Committee has gone through
the proper RFC or approval
- MUST validate that code reviews have been conducted
before merging a pull request when no code is written
- MUST validate that tests and documentation have
been written before merging a pull request that contains new
- SHOULD add the
correct labels to issues and pull requests
- SHOULD make sure the correct Area Experts are
assigned to relevant pull requests and issues. This includes adding
extra reviewers when it makes sense (e.g. a pull request that adds
remoting capabilities might require a security expert)
- SHOULD validate that the names and email addresses
in the git commits reasonably match identity of the person submitting
the pull request
- SHOULD make sure contributors are following the contributor guidelines
- SHOULD ask people to resend a pull request, if it
- SHOULD wait for the CI
system build to pass for pull requests (unless, for instance, the
pull request is being submitted to fix broken CI)
- SHOULD encourage contributors to refer to issues in
their pull request description (e.g.
Resolves issue #123).
If a user did not create an issue prior to submitting their pull
request, their pull request should not be rejected. However, they should
be reminded to create an issue in the future to frontload any potential
problems with the work and to minimize duplication of efforts.
- SHOULD encourage contributors to create meaningful
titles for all PRs. Edit the title if necessary to provide clarity on
- SHOULD encourage contributors to write meaningful,
descriptive git commits
- SHOULD NOT merge pull requests with a failed CI
build (unless, for instance, the pull request is being submitted to fix
- SHOULD NOT merge pull requests without the status
check passing from the Microsoft CLA bot (unless the CLA bot is broken,
and CLA signing can be confirmed through other means)
- SHOULD NOT merge pull requests too quickly after
they're submitted. Even if the pull request meets all the requirements,
people should have time to give their input (unless the pull request is
particularly urgent for some reason)
- SHOULD NOT merge your own pull requests. If a
Repository Maintainer opens a pull request, another Maintainer should
merge it unless there are extreme, short-term circumstances requiring a
merge or another Maintainer has given explicit sign-off without
Issue Management Process
Please see Issue Management
Pull Request Workflow
Please see Contributing
Maintainer Best Practices
Please see Best Practices
Becoming a Repository
Repository Maintainers currently consist mostly of Microsoft
employees. It is expected that over time, regular trusted contributors
to the PowerShell repository will be made Repository Maintainers.
Eligibility is heavily dependent on the level of contribution and
expertise: individuals who contribute consistently in meaningful ways to
the project will be recognized accordingly.
At any point in time, the existing Repository Maintainers can
unanimously nominate a strong community member to become a Repository
Maintainer. Nominations are brought to the PowerShell Committee to
understand the reasons and justification. A simple majority of the
PowerShell Committee is required to veto the nomination. When a nominee
has been approved, a PR will be submitted by a current Maintainer to
update this document to add the nominee's name to the Current Repository
Maintainers with justification as the description of the PR to serve
as the public announcement.