Nodejs.dev: Onboarding: @SauloNunes and @BenHalverson

[SMotaal]

# 👋
TODO

Foremost

• [x] Add @SauloNunes to @nodejs/website-redesign or @nodejs/nodejs-dev
• [x] Add @BenHalverson to @nodejs/website-redesign or @nodejs/nodejs-dev

Then

• [ ] Figure out why there are two separate teams and if consolidation would be reasonable
  > There seems to be two teams @nodejs/website-redesign and @nodejs/nodejs-dev

Finally

• [ ] Make sure all active members are on the same team

---

/cc @nodejs/website-redesign @keywordnew @jonchurch

[jonchurch]

Hmmm, I just realized, I'm not even a part of this team. I'm part of @nodejs/nodejs-dev...

Likely because we merged two repos a while ago, website-redesign (which was a purely admin repo) and this repo nodejs.dev (which was where the code lived).

[SMotaal]

@keywordnew can we raise this in tomorrow's @nodejs/community-committee meeting please.

[keywordnew]

Looks like this is resolved.

Sparked another issue about the purpose of two teams: #412

[keywordnew]

Actually, I'll leave this open. The action decided in CommComm was to add to the newer team and to start merging the teams. In the meantime, if there are any issues from not being on the older team, we can resolve that here.

[SMotaal]

I think it is hard to know from my end if there are privileges missing in @nodejs/nodejs-dev compared to @nodejs/website-redesign… @jonchurch may be more insightful.

[bnb]

There should not be. The only difference is between the two teams is that @nodejs/website-redesign has access to the website-redesign repo in addition to this repo, which is now archived. We can add that relatively "useless" ownership to nodejs.dev, but it's a trivial difference.

[SMotaal]

@bnb — I think I was maybe wondering more about CI aspects, have no clue if for instance Google Cloud permission to see the actual build logs… etc, would be different, obviously talking from the point of view of uncertainty since I only see "access denied" and not sure to what exactly 😉

Note — this is not asking for admin access, just pondering about matters of access is all!

[bnb]

cc @mylesborins - do you have context on the above?

[MylesBorins]

Automation is all based on the repo not the team. I had chimed in another
thread that it wasn't entirely clear why the two teams should be merged.
myself and others who are not involved in the broader redesign effort are
helping to maintain the nodejs.dev website but not participating in
meetings or the team. Seems like an over optimization to me.

On Sun, Feb 23, 2020, 11:22 AM Tierney Cyren [e-mail]
wrote:

cc @MylesBorins https://github.com/MylesBorins - do you have context on
the above?

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

[benhalverson]

We're onboarded now and this can be closed.

[SMotaal]

@benhalverson sorry for not staying on top of my issues… I'm trying to find ways to avoid them creeping all over the project 😅

[designMoreWeb]

Any way i can get involved with the website redesign as well.I know that i need to be on the look out for redesign issues but i have not spotted many. Please do let me know as I would like to be a part and help where needed