Strategic Initiatives - Tracking Issue

[mhdawson]

Tracking issue tagged with tsc-agenda so that we have entry to review status of the initiatives in the weekly TSC call.

https://github.com/nodejs/TSC/blob/master/Strategic-Initiatives.md

[Trott]

Should we consider paring down strategic initiatives that aren't really strategic? Collab onboarding is important, but I'm not sure it's strategic. I don't mind giving a weekly quick update on who was onboarded during the announcements section of the TSC meeting, but I wonder if we lose signal on truly strategic things by including everything here.

[MylesBorins]

+1 on pairing down. This was one of my original critiques

…

On Dec 4, 2017 9:20 AM, "Rich Trott" ***@***.***> wrote: Should we consider paring down strategic initiatives that aren't really strategic? Collab onboarding is important, but I'm not sure it's strategic. I don't mind giving a weekly quick update on who was onboarded during the announcements section of the TSC meeting, but I wonder if we lose signal on truly strategic things by including everything here. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#423 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAecV3ubF1QFb-66tolIVB7Oa9eC3zEyks5s8_-TgaJpZM4QimBF> .

[mhdawson]

@Trott I'd agree that if the collab onboarding is going to be an update about who was onboarded as opposed to a specific effort to improve onboarding (as an example) we can remove it.

[mhdawson]

@Trott should I open a PR to remove collab onboarding and Moderation ?

[Trott]

@mhdawson Moderation can probably stay until the team is fully spun up. We need to figure out how to give that team the necessary privileges across the various repositories. Onboarding of collaborators can definitely be removed, in my opinion. I'll open a pull request.