Strategic Initiatives - Tracking Issue #423

Activity

1. mhdawson

   added

   tsc-agenda

   on Nov 17, 2017
2. Trott commented on Dec 4, 2017

   

   Trott

   on Dec 4, 2017

   Member

   More actions

   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.
3. MylesBorins commented on Dec 4, 2017

   

   MylesBorins

   on Dec 4, 2017 via email

   Contributor

   More actions

   +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> .
4. mhdawson commented on Dec 4, 2017

   

   mhdawson

   on Dec 4, 2017

   MemberAuthor

   More actions

   @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.
5. mhdawson commented on Dec 5, 2017

   

   mhdawson

   on Dec 5, 2017

   MemberAuthor

   More actions

   @Trott should I open a PR to remove collab onboarding and Moderation ?
6. Trott commented on Dec 5, 2017

   

   Trott

   on Dec 5, 2017

   Member

   More actions

   @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.
7. Trott commented on Mar 30, 2018

   

   Trott

   on Mar 30, 2018

   Member

   More actions

   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.

   👍React with 👍1Reacted by mary marchini
8. mhdawson commented on Apr 2, 2018

   

   mhdawson

   on Apr 2, 2018

   MemberAuthor

   More actions

   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.
9. Trott commented on Apr 2, 2018

   

   Trott

   on Apr 2, 2018

   Member

   More actions

   If we change the underlying module used to generate the issue, then we'll get it for other meetings

   Isn't the underlying module make-node-meeting? If so, then you can edit examples/tsc.sh and/or $HOME/.make-node-meeting/tsc.sh and it will only affect the TSC meeting.
10. Trott

    added a commit that references this issue on Jul 29, 2019

    Update meeting templates for standing issues

    ...

    5f50180
11. mhdawson

    closed this as completedin create-node-meeting-artifacts#73on Aug 16, 2019