-
Notifications
You must be signed in to change notification settings - Fork 826
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
Move Googlers no longer actively reviewing code to emeritus owners #1116
Move Googlers no longer actively reviewing code to emeritus owners #1116
Conversation
Build Succeeded 👏 Build Id: 77ec9ca0-66ff-425b-929d-65f5a0d4ea1f The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
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.
What will be the process to become an active reviewer? Modify this file ?
I assume we can't approve any change while we are emeritus_approver, right?
Build Failed 😱 Build Id: 1720b7be-bee8-4786-bd1f-7c573dbe402c To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
e9f110e
to
f05c40c
Compare
Build Succeeded 👏 Build Id: dfbf8a1b-1ee5-4e52-ac29-e1590f6fc55e The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
Right now, the owners file is really only used by prow to auto-assign PRs to reviewers. Being moved out of the approvers section means that you won't get PRs assigned to you. If/when we switch to using prow to automatically merge PRs (rather than click the button) then not being an approver means you can't approve PRs for prow to merge them. In the current state, you will still be an owner of the repo, still be able to approve PRs, and still be able to manually merge them. You won't lose any permissions (yet). But you bring up a good question which is that we have a process for promoting folks to be project approvers while we don't have a written policy about the process for becoming emeritus and/or regaining approver powers. https://github.com/googleforgames/agones/blob/master/docs/governance/community_membership.md#responsibilities-and-privileges says that we expect approvers to "be responsive to review requests in a timely manner". If folks aren't actively reviewing PRs, then I think it's reasonable to say that they are not acting an a project approver any longer. |
@joeholley / @jkowalski - any thoughts? |
f05c40c
to
e8cbaeb
Compare
Build Succeeded 👏 Build Id: 7e86ddd0-6d42-4a32-8650-bde3aee5cd18 The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
e8cbaeb
to
ccd596b
Compare
Build Succeeded 👏 Build Id: 47950b67-0456-4a36-86b4-6eb9f50293c9 The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: markmandel, roberthbailey 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 |
Split out of #1113.
/assign @jkowalski @joeholley @ilkercelikyilmaz