-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Strategic Initiatives - Tracking Issue #423
Strategic Initiatives - Tracking Issue #423
Comments
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. |
+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>
.
|
@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. |
@Trott should I open a PR to remove collab onboarding and Moderation ? |
@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. |
This isn't really a tracking issue. This is a permanently-opened issue to keep this in the agenda. Can we simply update the template for the meeting to include strategic initiative updates as a thing we always do (just like Announcements, Q&A, Upcoming Meetings, etc.)? Then we can close this issue. |
Its more complicated than that since there is only a template for for the minutes, not for the issue. Its on the todo list to add a template for the issue as well but its not there right now. If we change the underlying module used to generate the issue, then we'll get it for other meetings which we don't want, so we should wait until there is a template to generate the issue. |
Instead of having permanently open issues just so the tooling can add stuff to the agenda, include permanent standing issues in the templates. While we're at it, get rid of "Q&A, Other" from TSC meeting because we don't do Q&A anymore and "Other" seems lose-able. Closes: nodejs/admin#395 Closes: nodejs/TSC#423
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
The text was updated successfully, but these errors were encountered: