-
Notifications
You must be signed in to change notification settings - Fork 85
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 editorship to @npm #546
Conversation
Well deserved! Great job @npm1 👍 |
Awesome, thank you for taking this on officially @npm1! |
You've got this, @npm1 ! |
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.
Happy to help here!
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.
r+!
Neat, thanks for all of the reviews! Merging! |
SHA: 42bebc1 Reason: push, by pull[bot] Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Sam Goto <[email protected]>
As FedCM becomes more mature, this PR proposes that we start moving editorship of FedCM to @npm1 (and, ideally, a non-chrome co-editor, that we are actively looking for), to formalize an existing norm (@npm1 has been submitting more spec PR changes than myself for a considerable amount of time).
I'm still going to be around and help @npm1 through this transition, but I expect to fully transition at some point (say, by the end of the year?) out of editorship.
This PR signals that more concretely to set the expectations that @npm1 can (and should) be the primary reviewer of PRs going forward (and I can act as a secondary while @npm1 still ramps up).
Preview | Diff