-
-
Notifications
You must be signed in to change notification settings - Fork 4
Add web-infra onboarding docs #17
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
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: flakey5 <[email protected]>
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.
Perhaps make an ONBOARDING.md, with a # @nodejs/web-infra section?
|
@flakey5 I also believe we could document our Slack channels on the onboarding doc and what they server for. (there's the website one, alerts one, i18n one for website, and others I gues?) |
|
OOC, why is the PR blocked? |
|
@flakey5 I forgot, we also have this list for Crowdin: https://github.com/nodejs/email/blob/main/iojs.org/aliases.json#L175 Can you also add this to the onboarding docs, we also need the current remaining members of web-infra added there! |
Per the PR description,
|
Co-authored-by: Aviv Keller <[email protected]> Co-authored-by: Matt Cowley <[email protected]>
|
Hey @flakey5 just wondering if you're still OOO (vacations); Should we take over this PR or? |
Signed-off-by: flakey5 <[email protected]>
Apologizes got side tracked, updated from reviews but I think this should still be blocked since nodejs/admin#984 is still open |
Agreed |
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.
Looks good. These changes make this uniform with the @nodejs/nodejs-website onboarding guide.
| # @nodejs/web-infra Onboarding | ||
|
|
||
| This document is an outline of the tasks necessary to onboard a new member of the Web Infrastructure team (@nodejs/web-infra). | ||
|
|
||
| Please note these tasks should only be performed after an individual's nomination has passed. | ||
| To start the nomination process, see [GOVERNANCE.md](../GOVERNANCE.md). | ||
|
|
||
| ## Tasks |
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.
| # @nodejs/web-infra Onboarding | |
| This document is an outline of the tasks necessary to onboard a new member of the Web Infrastructure team (@nodejs/web-infra). | |
| Please note these tasks should only be performed after an individual's nomination has passed. | |
| To start the nomination process, see [GOVERNANCE.md](../GOVERNANCE.md). | |
| ## Tasks | |
| ## @nodejs/web-infra Onboarding |
Let's make this uniform w/ https://github.com/nodejs/web-team/blob/main/onboarding/nodejs-website.md?plain=1
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.
I think we should keep the two paragraphs since it gives a general outline and explicitly states when these steps should happen. While both can be inferred implicitly, I still think it's better to explicitly state these so avoid confusion or misinterpretation regardless of how unlikely
onboarding/web-infra.md
Outdated
| - [ ] The nominee should open an issue in [nodejs/admin](https://github.com/nodejs/admin) requesting access to the Web Infra 1Password vault. | ||
| - [ ] A Web Admin should invite the nominee to Node.js' Sentry account. | ||
| - [ ] The nominee should enable physical or passkey 2FA on their Sentry account. | ||
| - [ ] A Web Admin should invite the nominee to Node.js' Vercel account. |
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 we also give access to Cloudflare even if in a read-only capacity?
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.
I have admin read-only, I had assumed that was something all of web-infra has so we can see what's going on there
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.
I think that is up to the build team, I do think admin read only would be nice but right now there's no set level of access (i.e. I have workers read and R2 read atm)
|
@flakey5 If all of my comments are merged, it'll unblock this PR, since, it removes any references to "Web Admins". IMO, while they do exist (@ovflowd and @bmuenzenmeyer), they don't need to be explicitly stated as the ones to perform the action. This is also consistent with other onboarding guides:
For example,
This can also be performed by members of the TSC.
This is a general recommendation, it doesn't really need to come from a specific person (Feel free to disagree with me tho) |
Co-authored-by: Aviv Keller <[email protected]>
|
For the latter of the examples I agree, but still I think the former should be explicitly stated as to whom should perform the action to avoid any potential confusion. There are cases like you pointed out where it's not just Web Admins that can perform an action, but still it still should generally be Web Admins doing it. Regardless, if the rule we're going with is
then that's explicit enough for me at least |
Co-authored-by: Aviv Keller <[email protected]>
|
Re nodejs/build#4127, what would the process be for getting added to search console? |
Whatever you think is best, it's your PR :-) |
Re #5
Note: blocked until nodejs/admin#984 goes through since this mentions the
web-adminsteam.