Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create Communications Channel to JS Newsletters/Periodicals #110

Open
4 tasks
bmeck opened this issue Jan 19, 2022 · 27 comments
Open
4 tasks

Create Communications Channel to JS Newsletters/Periodicals #110

bmeck opened this issue Jan 19, 2022 · 27 comments

Comments

@bmeck
Copy link
Member

bmeck commented Jan 19, 2022

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
Copy link
Member

sheplu commented Jan 20, 2022

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
Copy link
Member

mhdawson commented Mar 2, 2022

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

@mhdawson
Copy link
Member

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

@sheplu
Copy link
Member

sheplu commented Apr 19, 2022

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
Copy link
Member

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

mhdawson added a commit to openjs-foundation/tech-strategy that referenced this issue Apr 26, 2022
* doc: add initial section on how OpenJS helps projects

Refs: nodejs/next-10#110

Signed-off-by: Michael Dawson <[email protected]>
@UlisesGascon
Copy link
Member

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

@mhdawson
Copy link
Member

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.

@AugustinMauroy
Copy link
Contributor

nodejs/nodejs.org#6930

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants