Create Communications Channel to JS Newsletters/Periodicals

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.

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.

doc: add initial section on how OpenJS helps projects

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

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.

@sheplu

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

doc: add initial section on how OpenJS helps projects (#4)

@mhdawson

Following up on this topic it seems the repository nodejs/social-team#8 is now archived.

I think on top of the JS newsletter it would be great to try to push this effort / initiative for the next year (it seems also that we do have new WG being created recently - like SEA and Performances).

Do you know what would be the good place to ask about this tweet calendar bot @mhdawson ?

@kyliewd

@kyliewd can you help with that?

hi! i can help. can you please provide any information you'd like me to include in the tweet? this will help me accurately get this out each time! thank you.

@kyliewd

The main idea was to raise awareness about the Working Groups and have more people joining us.
So maybe a weekly tweet about the meeting planned with a small introduction and like of the zoom / github repos / github issue ? I don't know what could be done by a bot easily ?

It could also be a daily tweet with the daily meeting ?

I am not sure what could be the easiest way to communicate about that ? I opened another issue specific to this topic but I cannot tag you there @kyliewd #175

Hi there - I will comment on the other issue regarding this. Thanks!

What a few people were curious about are:

what are important PRs being worked on at the minutes
what are the WGs up to?
what is coming in the future?
how can they help/participate

The problem is syndicating all that info into a "summary" and delivering it every week.
It's a lot of work also, but maybe it could be feasible?

Issue created in TSC repo to get feedback on alternate approach - nodejs/TSC#1333

PR created to document in node core repo - nodejs/node#47189

PR landed next step is to promote to working groups/teams

Michael
- will open for Node core (Done)
- Michael will ask uvwasi team (Done)
- Michael will ask Diagnostic team
- Michael Security team
Jean - will reach out to
- Performance team
- will create for Next-10 team
- will reach out to SEA team

Created these issues to make sure we close on the Diagnostic team and the Security team

nodejs/diagnostics#614
nodejs/security-wg#1006

Emailed what I believe are the publishers of

JS Weekly
Node Weekly
ES.Next News

With variations on:

The Node.js Next-10 team is working to get more visibility of project related news as outlined in https://github.com/nodejs/node/blob/main/doc/contributing/sharing-project-news.md.

The goal is to build a low overhead way for teams across the project to share news and for publishers to find/publish what they find interesting.

The next-10 team is still onboarding project teams(https://github.com/nodejs/next-10/issues/110#issuecomment-1505416598) and I expect that the amount of news posted will slowly ramp up over time.

I believe you are one of the publishers of XXX and I wanted to give you a heads up in case you are interested in periodically checking out the updates as potential content.

If you have any questions please let me know.

@kyliewd

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

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

@sheplu

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

@peterc

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

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.

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

We have the communication channel in place, but remaining issue to is to incentivise people to generate content.

Closing this issue we can possibly open a new issue to encourage people to generate content.

nodejs/nodejs.org#6930

I put that here so it's can be discuss on meeting

Navigation Menu

Repository navigation

Create Communications Channel to JS Newsletters/Periodicals #110

3 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Create Communications Channel to JS Newsletters/Periodicals #110

Description

Activity

sheplu commented on Jan 20, 2022

mhdawson commented on Mar 2, 2022

mhdawson commented on Mar 30, 2022

sheplu commented on Apr 19, 2022

mhdawson commented on Apr 19, 2022

sheplu commented on Nov 15, 2022

mhdawson commented on Nov 15, 2022

kyliewd commented on Nov 15, 2022

sheplu commented on Nov 16, 2022

kyliewd commented on Nov 17, 2022

mcollina commented on Nov 18, 2022

3 remaining items

mhdawson commented on Jan 20, 2023

mhdawson commented on Mar 29, 2023

mhdawson commented on Apr 12, 2023

mhdawson commented on May 29, 2023

mhdawson commented on May 29, 2023

mhdawson commented on May 29, 2023

sheplu commented on Jun 21, 2023

peterc commented on Jun 23, 2023

mhdawson commented on Jun 28, 2023

mhdawson commented on Jun 28, 2023

UlisesGascon commented on Nov 25, 2023

mhdawson commented on Jun 12, 2024

AugustinMauroy commented on Jul 24, 2024

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions