-
Notifications
You must be signed in to change notification settings - Fork 24
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
Comments
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 |
Refs: nodejs/next-10#110 Signed-off-by: Michael Dawson <[email protected]>
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. I doubt CxO will be reading Node Weekly to keep track. |
@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 Refs: nodejs/next-10#110 Signed-off-by: Michael Dawson <[email protected]>
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. |
I put that here so it's can be discuss on meeting |
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):
We could also figure out how to send emails via the org email to avoid spam filters.
The text was updated successfully, but these errors were encountered: