Community-committee: Current Strategic Initiatives Review

Created on 22 Jan 2018  Â·  5Comments  Â·  Source: nodejs/community-committee

Now that we've got a documented set of Strategic Initiatives, I'd like to propose that we review the Initiatives and prune any that may need to be retired for various reasons.

Of the initiatives listed in "Current Initiatives", there are two that are relatively inactive:

  • nodejs/community-events: Originally kicked off in the very early days of the Community Committee, it doesn't seem like there has been much/any activity since its initial launch.
  • nodejs/evangelism: Originally chartered as a WG of the TSC, it's initial purpose was very similar to that of the CommComm. Unfortunately, the repository and team have been inactive for an extended period. As much as it pains me to say it, I think the Evangelism WG may need to be retired in favor of focusing other CommComm efforts.

Additionally, there's an initiative that I personally took on and would like to discuss the future of a bit more–if members are _interested_ in there being a future for it:

  • Office Hours: I initially talked with @hackygolucky about this, and decided to try to kick it off. I did a personal stream to see if there was any interest in it before moving it to an official property, and didn't get much engagement. I think this could be a very valuable initiative, but I think having it framed as an open Q&A with CommComm members may not be the best approach with the current stage the CommComm is in. An alternative approach may be to have it be an open and optional working session Q&A for CommComm members to jump in and have a more casual session to work on CommComm projects and help lower barriers for observers in addition to Q&A, but that's just one idea. Would very much like to hear others thoughts on this one.

Additionally, there's the task of reviewing the "Need Champion for" initiatives–not sure if we want to discuss those here, or in another issue.

Most helpful comment

One thing we did for the TSC was to have an open issue tagged tsc-agenda so that it showed up on the agenda for each meeting. We then have each of the champions provide an update (if appropriate). I think its a good way to keep the initiatives top of mind and keep the members aware of whether they are progressing or not. We might want to do the same for CommComm.

All 5 comments

I think this should be discussed in the next meeting (today?), just to be sure.

Other than that, LGTM! I particularly like the new approach on the Office Hours

@Tiriel yes, you're right. Adding the cc-agneda label and moving it to the agenda.

One thing we did for the TSC was to have an open issue tagged tsc-agenda so that it showed up on the agenda for each meeting. We then have each of the champions provide an update (if appropriate). I think its a good way to keep the initiatives top of mind and keep the members aware of whether they are progressing or not. We might want to do the same for CommComm.

@bnb Do you think we can close this as resolved?

Closing since I recently merged in a README refactor that I think updated strategic initiatives section to reflect current state 🙂 Please feel free to re-open if thats inaccurate!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

amiller-gh picture amiller-gh  Â·  3Comments

SMotaal picture SMotaal  Â·  3Comments

hackygolucky picture hackygolucky  Â·  4Comments

amiller-gh picture amiller-gh  Â·  4Comments

mhdawson picture mhdawson  Â·  3Comments