-
Notifications
You must be signed in to change notification settings - Fork 166
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
Onboarding F3n67u to the build wg #3003
Comments
I added |
We should probably fix that onbording guidance there are probably a number of teams which require more than just showing interest as a prereq for being added. |
Maybe the docs should link to https://github.com/orgs/nodejs/teams/core/teams for a list of what we consider "subsystem teams" |
That page is not visible to people who are not members of the org, so they would have lesser time to decide which teams they would like to join. Previously, they had days to decide but if we do this, it would be a 15 minute window. This might not be a problem but I thought we should take this into consideration. |
I don't think it should be a big deal if they have 15 mins to decide, they would have access after being a org member and could later ask to join a team? |
There are a number of teams (for example, the build team) which require more than just showing interest as a prerequisite for being added, so this change adds a link to the set of subsystem teams where new Collaborators can be added directy. Also, the doc didn't actually mention if the new Collaborator should be added to the team. This change also clarifies that. Refs: nodejs/build#3003 Signed-off-by: Darshan Sen <[email protected]>
Sent nodejs/node#44024 to fix the onboarding doc. |
@RaisinTen thanks! |
There are a number of teams (for example, the build team) which require more than just showing interest as a prerequisite for being added, so this change adds a link to the set of subsystem teams where new Collaborators can be added directy. Also, the doc didn't actually mention if the new Collaborator should be added to the team. This change also clarifies that. Refs: nodejs/build#3003 Signed-off-by: Darshan Sen <[email protected]> PR-URL: #44024 Reviewed-By: Feng Yu <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Matteo Collina <[email protected]>
There are a number of teams (for example, the build team) which require more than just showing interest as a prerequisite for being added, so this change adds a link to the set of subsystem teams where new Collaborators can be added directy. Also, the doc didn't actually mention if the new Collaborator should be added to the team. This change also clarifies that. Refs: nodejs/build#3003 Signed-off-by: Darshan Sen <[email protected]> PR-URL: #44024 Reviewed-By: Feng Yu <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Matteo Collina <[email protected]>
There are a number of teams (for example, the build team) which require more than just showing interest as a prerequisite for being added, so this change adds a link to the set of subsystem teams where new Collaborators can be added directy. Also, the doc didn't actually mention if the new Collaborator should be added to the team. This change also clarifies that. Refs: nodejs/build#3003 Signed-off-by: Darshan Sen <[email protected]> PR-URL: #44024 Reviewed-By: Feng Yu <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Matteo Collina <[email protected]>
There are a number of teams (for example, the build team) which require more than just showing interest as a prerequisite for being added, so this change adds a link to the set of subsystem teams where new Collaborators can be added directy. Also, the doc didn't actually mention if the new Collaborator should be added to the team. This change also clarifies that. Refs: nodejs/build#3003 Signed-off-by: Darshan Sen <[email protected]> PR-URL: #44024 Reviewed-By: Feng Yu <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Matteo Collina <[email protected]>
There are a number of teams (for example, the build team) which require more than just showing interest as a prerequisite for being added, so this change adds a link to the set of subsystem teams where new Collaborators can be added directy. Also, the doc didn't actually mention if the new Collaborator should be added to the team. This change also clarifies that. Refs: nodejs/build#3003 Signed-off-by: Darshan Sen <[email protected]> PR-URL: nodejs#44024 Reviewed-By: Feng Yu <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Matteo Collina <[email protected]>
There are a number of teams (for example, the build team) which require more than just showing interest as a prerequisite for being added, so this change adds a link to the set of subsystem teams where new Collaborators can be added directy. Also, the doc didn't actually mention if the new Collaborator should be added to the team. This change also clarifies that. Refs: nodejs/build#3003 Signed-off-by: Darshan Sen <[email protected]> PR-URL: #44024 Reviewed-By: Feng Yu <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Matteo Collina <[email protected]>
There are a number of teams (for example, the build team) which require more than just showing interest as a prerequisite for being added, so this change adds a link to the set of subsystem teams where new Collaborators can be added directy. Also, the doc didn't actually mention if the new Collaborator should be added to the team. This change also clarifies that. Refs: nodejs/build#3003 Signed-off-by: Darshan Sen <[email protected]> PR-URL: #44024 Reviewed-By: Feng Yu <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Matteo Collina <[email protected]>
There are a number of teams (for example, the build team) which require more than just showing interest as a prerequisite for being added, so this change adds a link to the set of subsystem teams where new Collaborators can be added directy. Also, the doc didn't actually mention if the new Collaborator should be added to the team. This change also clarifies that. Refs: nodejs/build#3003 Signed-off-by: Darshan Sen <[email protected]> PR-URL: nodejs/node#44024 Reviewed-By: Feng Yu <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Matteo Collina <[email protected]>
There are a number of teams (for example, the build team) which require more than just showing interest as a prerequisite for being added, so this change adds a link to the set of subsystem teams where new Collaborators can be added directy. Also, the doc didn't actually mention if the new Collaborator should be added to the team. This change also clarifies that. Refs: nodejs/build#3003 Signed-off-by: Darshan Sen <[email protected]> PR-URL: nodejs/node#44024 Reviewed-By: Feng Yu <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Matteo Collina <[email protected]>
As agreed in #3299 I will close this issue. |
While I was onboarding @F3n67u as a collaborator yesterday, I followed the onboarding guide in the core repo and it mentions this:
https://github.com/nodejs/node/blob/main/onboarding.md#fifteen-minutes-before-the-onboarding-session
Feng expressed interest in joining the Build WG, so I assumed that I was supposed to add him there and I did so. However, now I realize that the build repo has its own governance and onboarding documents, so I feel that maybe that was not the right thing to do, so I have removed Feng from the build team.
I wanted to know what should be done here. Is anyone else from the @nodejs/build team going to onboard Feng to this group or is there anything else that we should do first?
The text was updated successfully, but these errors were encountered: