Automatic tweet for WG meetings

[sheplu]

Following the discussion on the issue #110 I think it would be better to discuss that in a separate issue

Main topic

A lot of discussions are being help by the Working Groups daily in a synchronous manner (on top of asynchronous discussion through various media). Most of the time the same people are both in the meetings and in PR/Issue.

I think this would be great to have more communication to try to

• display what we do to a broader audience
• have more people following the meeting or checking the replay after
• provide more feedback to contributors / WG from external sources
• raise awareness and interest from the community to contribute

Proposition

I don't know what's really possible but here is a few main ideas

• Weekly tweet thread with all the WG events with some basics information: Date / zoom link / github repo (or issue repo)
• daily tweet with all WG meetings of the day with the same information

Also as meeting are recorded, maybe it can be a good idea to tweet about the record the day after the meeting and/or include that on the next meeting tweet

what do you think @nodejs/next-10 ?

[kyliewd]

Hi @sheplu - Given the volume of our audience on our social handles, would recommend that we only do social communications on this monthly, or on an ad hoc basis. Too many tweets on the topic buries other news that we want to pop.

The foundation team recommends using Slack channels for daily/weekly communications regarding meetings. Thanks!

[sheplu]

Indeed I didn't though of that. What would you recommande as a monthly basis to tweet about ? A list of the current Active Working groups maybe ?

[mhdawson]

@kyliewd can you outline what you see as our audience? I'm trying to understand how a once a week tweet about the core work of the project would be too much?

[mhdawson]

Wondering that if we have multiple audiences maybe some segmentation might help if we think some subset of followers won't be interested in what is going on in the community?

[rginn]

+1 to Kylie's recommendation, which we discussed as a team.

As you know, there are nearly 840k Node.js Twitter followers. We want to be strategic about content and not create additional noise when other targeted communication channels and direct outreach would be best.

[mhdawson]

I'm just trying to understand how the core community work is noise, but lets discuss off line.

[mhdawson]

Based on a suggestion from some discussion, this is a concrete example of what it might look like:

Interested in contributing to Node.js,? Working groups getting together this week include Loaders at Tues 2 ET, next-10 on Wed 10ET, Security Thurs 10 ET, Package maintenance Thurs 1 ET, Node-API Friday 11ET. Hope to see you there. For more details https://nodejs.org/calendar.

The hope that it would be beneficial in getting more people involved,helping people get to discussions they are interested and can contribute to.

[mhdawson]

Not advocating for ET of course, we'd probably want to use UTC to be world friendly.

[sheplu]

I do like this tweet example ! Short with all key information for everyone to know and join if they want to

[Qard]

I would leave out the date/time from the message. Just include which groups have meetings that week and the link to the calendar can tell them more if they're interested.

[Trott]

Discussion here stalled out. Rather than try to argue against the reasons provided for not doing a weekly tweet, can we create the Slack channel reminders as suggested by @kyliewd? That seems to have no obstacles. There's an #openjs-calendar channel already. Maybe we can do something similar with a #nodejs-calendar channel and/or get our calendar added to the existing #openjs-calendar channel.

I'm kind of OK with reducing our Twitter activity given the events of the last few months on that platform, but if we want to keep trying to make that happen, maybe we can think about an appropriate monthly tweet or a way to do it ad hoc, as suggested?

[sheplu]

I do think this could be nice to follow up on that.

The idea of the Node.js calendar inside slack seems a good start and we could have this channel added by default to people (I guess ?)