Create Communications Channel to JS Newsletters/Periodicals

[bmeck]

We should be able to announce requests for feedback / important announcements / specific online efforts so that these periodicals have a little easier time seeing things and potentially having a way to expose more people to events in the org.

The outlets include examples such as (comment to add more):

• JS Weekly
• Node Weekly
• ES.Next News
• Bytes

We could also figure out how to send emails via the org email to avoid spam filters.

[sheplu]

should we also think about a good way to communicate through articles more often ? an easy way (maybe bi monthly or monthly) to provide feedback on the work done by the teams

[mhdawson]

@mhdawson and @joesepi will take an action to reach out to Node and JS Weekly.

[mhdawson]

PR to doc how the OpenJS Foundation will support this - openjs-foundation/tech-strategy#4

[sheplu]

i see this is moving in the good way

but should we also plan to post some things directly ? if i remember correctly one of the target was to work/insensitive company to use Node.js.
Having our own way to communicate would be a good sign - or at least share the changes all WG are doing. maybe not the same content but something a bit more easy to read yet showing we are active

I doubt CxO will be reading Node Weekly to keep track.

[mhdawson]

@sheplu this is not meant to replace other communication channels, just leverage another one that is already targetting/building a Node.js audience.

[mhdawson]

@kyliewd as an FYI mentioning you on this issue as well in case the Foundation wants to help publicise the project news shared through the effort as well. You can read more in https://github.com/nodejs/node/blob/main/doc/contributing/sharing-project-news.md on how to find the news shared.

[sheplu]

Performance: nodejs/performance#98
Next-10: #217
Single-Executable: nodejs/single-executable#74

I will also open the PR here: https://github.com/nodejs/node/blob/main/doc/contributing/sharing-project-news.md

[peterc]

(Hi, I'm the lead editor on both JavaScript Weekly and Node Weekly.) I agree with an earlier commenter who implied that the Node project would do well to publish its own news somewhere in order to have more reach. I would rather link to a post on the official Node blog than stitch together a story from bits and pieces on GitHub, if possible, because readers prefer that sort of more easily digested information too.

There may be other discussions about this, so apologies if I'm repeating anything that's already been discussed, but I think you should also consider how you work with the folks writing for publications like LWN, The New Stack, and InfoQ. We frequently link to these sources and their journalistic approach works quite well in getting news out to a broader audience like the CxOs @sheplu mentioned above. The New Stack, in particular, seems to be going quite heavy on JavaScript recently, so perhaps this backchannel is already open.

[mhdawson]

@peterc thanks for chiming in. I can understand that something already written up is easier to consume, but that requires some volunteer who wil do that writeup which is why we are experimenting with at least making the news easier to share/discover.

@UlisesGascon is doing a great job on a tool that will generate an RSS feed that consolidates the info without adding to the overhead on collaborators to report it in https://github.com/nodejs/nodejs-news-feeder and its just about ready to share more broadly.

[mhdawson]

In terms of the LWN, The New Stack, and InfoQ its a good idea to reach out to them as well to share the work so far.

[UlisesGascon]

I just created a PR to render the feed as a website nodejs/nodejs-news-feeder#59. Feedback super welcome 🎉