Status of GitHub LTS team

[Trott]

Is the @nodejs/LTS team now supplanted by and/or absorbed by the @nodejs/Release team, similar to the way @nodejs/CTC is now supplanted by and/or absorbed by @nodejs/TSC?

Trying to figure out if LTS should be made a subteam of members or not.

[MylesBorins]

LTS could potentially be a sub team of Release. Please leave those teams for now and we can open an issue to discuss team setup in the release repo

…

On Mar 6, 2018, at 10:45 AM, Rich Trott ***@***.***> wrote: Is the @nodejs/LTS team now supplanted by and/or absorbed by the @nodejs/Release team, similar to the way @nodejs/CTC is now supplanted by and/or absorbed by @nodejs/TSC? Trying to figure out if LTS should be made a subteam of members or not. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#84>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAecV4BmOrazfgeU3qkZiU3nWtNJfW1xks5tbtlCgaJpZM4SfOtK>.

[Trott]

@MylesBorins OK, thanks. I'll make LTS a subteam of members for now. If it gets moved to be a subteam of Release, then it will be a sub-subteam of members, which is also fine.

[Trott]

(I'm guessing here, but you probably don't want LTS to be a subteam of Release. If you do that, then any @-mentioning of Release about release-related things will also @-mention LTS. And any access you give Release will also be granted to LTS. Permissions and access flow down to subteams.)

[MylesBorins]

Release is the working group, different from releasers which is the team... But ironing this out is part of the reason I think we need to discuss as a wg

…

On Tue, Mar 6, 2018, 11:39 AM Rich Trott ***@***.***> wrote: (I'm guessing here, but you probably don't want LTS to be a subteam of Release. If you do that, then any @-mentioning of Release about release-related things will also @-mention LTS. And any access you give Release will also be granted to LTS. Permissions and access flow down to subteams.) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#84 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAecV3UpRzsLV9RIWMEz5rZ09AwgH1OYks5tbuX9gaJpZM4SfOtK> .

[Trott]

@MylesBorins Hmmm.... The description for @nodejs/release is "Access to cut Node.js releases". Either the description wrong or @nodejs/release is not the Release WG but instead the releasers.

[gibfahn]

So we discussed this a lot previously, and decided to have:

• nodejs/Release, with subteams:
  • nodejs/LTS
  • nodejs/releasers (what is now nodejs/release)
  • nodejs/citgm

It's all documented in the readme, and was discussed exhaustively in nodejs/Release#223.

Unfortunately no-one actually did the renaming.

I think the crucial thing is the updating of CI to change access permissions for nodejs/release to nodejs/releasers. Other than that there shouldn't be anything that needs particular care.

[mhdawson]

@gibfahn are you going to handle the updates?

[gibfahn]

I guess I can do that, sure.