Nodejs.dev: Merge website redesign teams

[keywordnew]

Summary

There are two teams focused on this initiative. We should have just one.

a. https://github.com/orgs/nodejs/teams/website-redesign/members
b. https://github.com/orgs/nodejs/teams/nodejs-dev/members

AFAIK, it's a legacy of having the original https://github.com/nodejs/website-redesign/ repo and the newer https://github.com/nodejs/nodejs-dev/ repo. The older was used to kick off the initiative, and the newer was where development began. The older repo was then used for admin, until it was archived, and the newer repo used for both admin and development.

Proposed next actions

• [ ] Investigate impact on development process
• [ ] Select one team, and merge the other in

[keywordnew]

@MylesBorins 👋🏽 Would you know of any permission impacts to gcbrun, if the teams were to be merged?

[jonchurch]

FWIW Members of nodejs-dev are currently able to kick off gcbrun (that's the team I've been a member of).

[MylesBorins]

The permissions model for gcb is based on who has access to the repo, not
specific teams. So as long as the merged team maintains the permissions it
will be fine.

I will point out that there are a number of folks, including myself,
helping to maintain .dev but are not active in the redesign initiative. As
such it might not entirely make sense to merge. But consider this a +/- 0

On Thu, Feb 20, 2020, 12:53 PM Jonathan Church [e-mail]
wrote:

FWIW Members of nodejs-dev are currently able to kick off gcbrun (that's
the team I've been a member of).

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nodejs/nodejs.dev/issues/412?email_source=notifications&email_token=AADZYVYIWZQC7FOSIWUZC5LRD27STA5CNFSM4KYTWR22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMPNSJI#issuecomment-589224229,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADZYVZIXHRP56M2NJ66T63RD27STANCNFSM4KYTWR2Q
.

[SMotaal]

@MylesBorins I think what we are trying to do as we are mostly new to the team, we're trying to size the joint to make sure where we are stepping, documenting things (@benhalverson) in https://github.com/benhalverson/nodejs.dev/blob/docs/CONTRIBUTING.md — see #397.

We are basically not sure we know enough about how gcbrun and other workflow aspects are managed:

1. Who is involved on admin aspects.
2. What those admin aspects look like.
3. What to do when we run into unknowns.

Obviously not asking to give access, merely to fill the void so we can see the landscape and know if and when it is time to loop others in as needed.

[MylesBorins]

I see the discussion about merging teams and operations as orthogonal tbh.

I spun up all the existing infrastructure and am the sole admin at the
moment. We can either extend access to others, or switch to another tool
such as netlify which might be easier to maintain.

We could also see about the build team taking ownership of the operations.

On Sat, Feb 22, 2020, 10:47 AM Saleh Abdel Motaal [e-mail]
wrote:

@MylesBorins https://github.com/MylesBorins I think what we are trying
to do as we are mostly new to the team, we're trying to size the joint to
make sure where we are stepping, documenting things (@benhalverson
https://github.com/benhalverson) in
https://github.com/benhalverson/nodejs.dev/blob/docs/CONTRIBUTING.md —
see #397 https://github.com/nodejs/nodejs.dev/pull/397.

We are basically not sure we know enough about how gcbrun and other
workflow aspects are managed:

1. Who is involved on admin aspects.
2. What those admin aspects look like.
3. What to do when we run into unknowns.

Obviously not asking to give access, merely to fill the void so we can see
the landscape and know if and when it is time to loop others in as needed.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nodejs/nodejs.dev/issues/412?email_source=notifications&email_token=AADZYVZR3RDUUNKCLVL3LNLREFCKHA5CNFSM4KYTWR22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMVDHZA#issuecomment-589968356,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADZYV6TSCS6CJHTTKAEQK3REFCKHANCNFSM4KYTWR2Q
.

[amiller-gh]

I'll do this today 👍

[amiller-gh]

Well, I spoke too soon without reading Myles' comment above!

@MylesBorins, what permissions concerns do we have with merging the two teams? If you have no significant ones, I'm happy to do the migration if you add me as a manager.

[amiller-gh]

(Also, welcome @tstreamDOTh to the team! Once we get this teams issue figured out I'll be sure to add you to the correct list 👍)

[MylesBorins]

@amiller-gh I think it shouldn't be an issue anymore

[saulonunesdev]

teams were merged

thanks @bnb <3