Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Policy] Replace "code owners" with "maintainers" #107384

Merged
merged 5 commits into from
Sep 16, 2024

Conversation

AaronBallman
Copy link
Collaborator

This replaces the previous Code Owners section of our developer policy with a new section for Maintainers. It also updates most of the places we mention "code owner" in the documentation (it does not update the files named Code Owners.rst or similar because those should be updated when the subprojects add their Maintainers.rst file).

The wording was taken from what was proposed in the RFC (including all suggested amendments from folks on the thread).

Please see the RFC for more details:
https://discourse.llvm.org/t/rfc-proposing-changes-to-the-community-code-ownership-policy/80714/

This replaces the previous Code Owners section of our developer policy
with a new section for Maintainers. It also updates most of the places
we mention "code owner" in the documentation (it does not update the
files named `Code Owners.rst` or similar because those should be
updated when the subprojects add their `Maintainers.rst` file).

Please see the RFC for more details:
https://discourse.llvm.org/t/rfc-proposing-changes-to-the-community-code-ownership-policy/80714/
Copy link
Contributor

@nikic nikic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Some nits, but I think this is basically good as-is.

@@ -328,17 +328,17 @@ Release Patch Rules
Below are the rules regarding patching the release branch:

#. Patches applied to the release branch may only be applied by the release
manager, the official release testers or the code owners with approval from
manager, the official release testers or the maintainers with approval from
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unrelated side note: I think that nowadays only release managers can merge to release branches.

llvm/docs/HowToReleaseLLVM.rst Outdated Show resolved Hide resolved
llvm/docs/DeveloperPolicy.rst Outdated Show resolved Hide resolved
llvm/docs/DeveloperPolicy.rst Outdated Show resolved Hide resolved
Copy link
Collaborator

@shafik shafik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Member

@JDevlieghere JDevlieghere left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks again @AaronBallman for driving this.

llvm/docs/DeveloperPolicy.rst Outdated Show resolved Hide resolved
llvm/docs/DeveloperPolicy.rst Outdated Show resolved Hide resolved
@AaronBallman AaronBallman merged commit c0719d8 into llvm:main Sep 16, 2024
9 checks passed
@AaronBallman AaronBallman deleted the aballman-maintainers-dev-policy branch September 16, 2024 17:05
nikic added a commit to nikic/llvm-project that referenced this pull request Sep 27, 2024
Following https://discourse.llvm.org/t/rfc-proposing-changes-to-the-community-code-ownership-policy/80714 and llvm#107384,
this PR moves the llvm CODE_OWNERS.txt to the Maintainers.rst file.

The format of the Maintainers.rst file follows the current
CodeOwners.rst from clang, with some minor changes to account
for the code owners -> maintainers migration.

This change is intended to be a pure format change, without
changing any actual code owners / maintainers. The list is still
very badly outdated. The intent here is to get the format change
out of the way, so we can get proper diffs when replacing no longer
active maintainers. If we mix both together, it will be hard to
follow what actually changed.

I've tried to categorize things as best as I could, and filled in
GitHub handles for people where I knew them or could determine them
with some confidence.
nikic added a commit to nikic/llvm-project that referenced this pull request Sep 27, 2024
Following https://discourse.llvm.org/t/rfc-proposing-changes-to-the-community-code-ownership-policy/80714 and llvm#107384,
this PR moves the llvm CODE_OWNERS.txt to the Maintainers.rst file.

The format of the Maintainers.rst file follows the current
CodeOwners.rst from clang, with some minor changes to account
for the code owners -> maintainers migration.

This change is intended to be a pure format change, without
changing any actual code owners / maintainers. The list is still
very badly outdated. The intent here is to get the format change
out of the way, so we can get proper diffs when replacing no longer
active maintainers. If we mix both together, it will be hard to
follow what actually changed.

I've tried to categorize things as best as I could, and filled in
GitHub handles for people where I knew them or could determine them
with some confidence.
nikic added a commit that referenced this pull request Oct 4, 2024
Following
https://discourse.llvm.org/t/rfc-proposing-changes-to-the-community-code-ownership-policy/80714
and #107384, this PR moves the
llvm CODE_OWNERS.txt to the Maintainers.md file.

The general format of the Maintainers.md file follows the current
CodeOwners.rst from clang, with some minor terminology changes to
account for the code owners -> maintainers migration.

This change is intended to be a pure format change, without changing any
actual code owners / maintainers. The list is still very badly outdated.
The intent here is to get the format change out of the way, so we can
get proper diffs when replacing no longer active maintainers. If we mix
both together, it will be hard to follow what actually changed.

I've tried to categorize things as best as I could, and filled in GitHub
handles for people where I knew them or could determine them with some
confidence.
DavidSpickett added a commit that referenced this pull request Oct 14, 2024
To align with the new policy:
https://llvm.org/docs/DeveloperPolicy.html#maintainers

I've assumed that Jonas will be the "Lead Maintainer" as he was the
default Code Owner.

I know the past Code Owners weren't "Maintainers" but it's the same
energy so I've changed it there too.

See also: #107384 /
https://discourse.llvm.org/t/rfc-proposing-changes-to-the-community-code-ownership-policy/80714
DanielCChen pushed a commit to DanielCChen/llvm-project that referenced this pull request Oct 16, 2024
To align with the new policy:
https://llvm.org/docs/DeveloperPolicy.html#maintainers

I've assumed that Jonas will be the "Lead Maintainer" as he was the
default Code Owner.

I know the past Code Owners weren't "Maintainers" but it's the same
energy so I've changed it there too.

See also: llvm#107384 /
https://discourse.llvm.org/t/rfc-proposing-changes-to-the-community-code-ownership-policy/80714
bricknerb pushed a commit to bricknerb/llvm-project that referenced this pull request Oct 17, 2024
To align with the new policy:
https://llvm.org/docs/DeveloperPolicy.html#maintainers

I've assumed that Jonas will be the "Lead Maintainer" as he was the
default Code Owner.

I know the past Code Owners weren't "Maintainers" but it's the same
energy so I've changed it there too.

See also: llvm#107384 /
https://discourse.llvm.org/t/rfc-proposing-changes-to-the-community-code-ownership-policy/80714
EricWF pushed a commit to efcs/llvm-project that referenced this pull request Oct 22, 2024
To align with the new policy:
https://llvm.org/docs/DeveloperPolicy.html#maintainers

I've assumed that Jonas will be the "Lead Maintainer" as he was the
default Code Owner.

I know the past Code Owners weren't "Maintainers" but it's the same
energy so I've changed it there too.

See also: llvm#107384 /
https://discourse.llvm.org/t/rfc-proposing-changes-to-the-community-code-ownership-policy/80714
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants