Remove @nodejs/web-standards from @nodejs/web

[avivkeller]

In my view, these teams are fundamentally different in purpose and focus.

The @nodejs/web-standards team consists of core collaborators dedicated to implementing and supporting Web Standards within Node.js core.

In contrast, the other @nodejs/web teams are made up of both core and non-core collaborators focused on maintaining and developing the Node.js website infrastructure.

Although both groups fall under the umbrella of "web," they interpret the term differently: @nodejs/web-standards refers to the W3C Web Standards, while the other teams deal with the infrastructure behind the Node.js website itself.

[MattIPv4]

👍 +1, I agree with web-standards becoming an independent team, they aren't involved in the operation/development of Node.js' web presence.

[AugustinMauroy]

+1

[GeoffreyBooth]

There's also @nodejs/nodejs-website. I think that's the primary group for the folks maintaining the website.

I think we don't need @nodejs/web anymore, unless it serves some purpose besides web standards and the website. To wind it down, someone could compile a list of whoever is in @nodejs/web who's not in either of @nodejs/web-standards or @nodejs/nodejs-website, and ask if they'd like to join either or both of those other teams. Once all the 'orphans' on @nodejs/web have been migrated to any other teams they want to be a part of (if any) then we can remove @nodejs/web.

[MattIPv4]

We should keep @nodejs/web -- that is the overarching grouping for all the folks involved in the web presence.

@nodejs/nodejs-website and @nodejs/web-infra are the two key sub-teams under that, all involved in the web presence, but with different focuses (day-to-day website development + infrastructure for said website).

As far as I can see, there are no 'orphans' in @nodejs/web, the only direct members are @ovflowd + @bmuenzenmeyer, who lead the team.

This is just about spinning out @nodejs/web-standards separate from the @nodejs/web grouping, as they aren't part of maintaining Node.js' web presence.

[GeoffreyBooth]

@nodejs/nodejs-website and @nodejs/web-infra are the two key sub-teams under that, all involved in the web presence, but with different focuses (day-to-day website development + infrastructure for said website).

Okay, so let's split out @nodejs/web-standards from @nodejs/web, and perhaps @nodejs/web could get a new name that's more specific to "website plus website infrastructure"? It would help avoid confusion. I would guess that web-standards got put under web because someone (maybe me) assumed the web team had a different purpose than it does.

[avivkeller]

I don't think there is any confusion right now? Internally, we could give the team a description that emphasizes that it's only for Node.js's Web Presence, but I think @nodejs/web accurately conveys what we want to convey.

[MattIPv4]

Yeh, I'd just make sure we set a description on the team, smth along the lines of "Responsible for Node.js' web presence (design + dev + infra for nodejs.org et al)".

[ovflowd]

So to clarify what @nodejs/web was supposed to be (as I created the team), it is not a placeholder team for the website and web Infra teams, it is a team encompassing web related efforts on the Node.js project, that's why a web standards team, an UX Team, a website team and a web Infra team. It unironically mixes teams with different purposes and scope.

We can remove it from the web team of course if we want, but just wanted to clarify this.

[avivkeller]

I still feel like these teams have different definitions of "web related efforts" (presence vs standards), and so they should be separate from one-another.

Especially now that we are adding governance files to this repository, it feels wrong for them to include @nodejs/web-standards.

(Something told me it was you who created the team when I saw the Netscape logo 😆)

[ovflowd]

I still feel like these teams have different definitions of "web related efforts" (presence vs standards), and so they should be separate from one-another.

Especially now that we are adding governance files to this repository, it feels wrong for them to include @nodejs/web-standards.

Fine by me.

(Something told me it was you who created the team when I saw the Netscape logo 😆)

I don't even recall if that was me, but sounds smth I'd do

[ljharb]

Sorry I missed this issue. It's fine to move "web standards" out of "web", but i'm not sure why that translates to removing the team entirely?

[MattIPv4]

I don't think anyone here is saying the team should be removed completely, just made independent of web.

[ljharb]

Great! The linked PR isn't moving the team description anywhere tho, only re moving it - does it already live somewhere else too?

[MattIPv4]

It doesn't to my knowledge, that'd be up to the folks within web-standards as to where they want to document themselves I imagine.