Skip to content
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

Closed
mhdawson opened this issue Nov 17, 2017 · 8 comments · Fixed by nodejs/create-node-meeting-artifacts#73
Closed

Strategic Initiatives - Tracking Issue #423

mhdawson opened this issue Nov 17, 2017 · 8 comments · Fixed by nodejs/create-node-meeting-artifacts#73

Comments

@mhdawson
Copy link
Member

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
Copy link
Member

Trott commented Dec 4, 2017

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
Copy link
Contributor

MylesBorins commented Dec 4, 2017 via email

@mhdawson
Copy link
Member Author

mhdawson commented Dec 4, 2017

@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
Copy link
Member Author

mhdawson commented Dec 5, 2017

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

@Trott
Copy link
Member

Trott commented Dec 5, 2017

@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.

@Trott
Copy link
Member

Trott commented Mar 30, 2018

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.

@mhdawson
Copy link
Member Author

mhdawson commented Apr 2, 2018

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.

Trott added a commit to Trott/create-node-meeting-artifacts that referenced this issue Jul 29, 2019
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants