-
Notifications
You must be signed in to change notification settings - Fork 703
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
Clarify who has website write access and why #1375
Conversation
@jimangel Once this merges, we can start adding release leads (@daminisatya) to |
+1 Thank you @zacharysarah |
Awesome. Thanks for adding these clarifications to the group name, @zacharysarah! |
/hold |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@zacharysarah -- Actually, one small nit. Looks like we're using the following nomenclature in other places, like kubernetes-sigs/
:
<repo>-admins
- admin access to<repo>
<repo>-write
- write access to<repo>
Examples:
org/config/kubernetes-sigs/sig-release/teams.yaml
Lines 22 to 23 in 06745b2
release-notes-admins: | |
description: admin access to release-notes |
org/config/kubernetes-sigs/sig-release/teams.yaml
Lines 29 to 30 in 06745b2
release-notes-maintainers: | |
description: write access to release-notes |
Would you mind changing the name to website-maintainers
and alpha-sorting the list?
Oh, one more thing! You could also move the admins team org/config/kubernetes/org.yaml Line 1726 in 06745b2
into the SIG Docs directory and rename to This will give y'all access to approve changes there without having to flag a |
8c2eb0f
to
3f4a038
Compare
@justaugustus 👋 Feedback incorporated, PTAL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@zacharysarah -- two more tiny nits!
privacy: closed | ||
sig-docs-vi-reviews: | ||
description: PR reviews for Vietnamese content | ||
website-write: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
website-write: | |
website-maintainers: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You'll need to place the renamed team above website-milestone-maintainers
list as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should the list not be alphabetical? Because right now teams are in alphabetical order:
309: website-admins
316: website-milestone-maintainers
372: website-write
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This still needs to be website-maintainers
instead of website-write
.
3f4a038
to
ec1c679
Compare
ec1c679
to
b0e9f81
Compare
b0e9f81
to
f39ebab
Compare
/assign @cblecker @mrbobbytables |
privacy: closed | ||
sig-docs-vi-reviews: | ||
description: PR reviews for Vietnamese content | ||
website-write: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This still needs to be website-maintainers
instead of website-write
.
f39ebab
to
3f85896
Compare
3f85896
to
b94c88c
Compare
/lgtm |
Needs rebase |
consolidate all access into sig-docs/teams.yaml
b94c88c
to
b976224
Compare
@cblecker Done! @justaugustus Ping, looks like @cblecker is busy. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cblecker, justaugustus, zacharysarah The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Clarify who has website write access and why Signed-off-by: huynguyennovem <[email protected]>
Based on this #sig-release Slack discussion, this PR changes the team name of
sig-docs-l10n-admins
tokubernetes-website-write
and adds comments for why each team member has write access.This PR also freshens team membership to the current SIG Docs chairs.
Many thanks to @justaugustus for the guidance!
/sig docs