You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey @adamstac & @jerodsanto, we met at the conference earlier this year in Vancouver. We just had a collab summit and were talking about ways we could partner with folks doing content and figure out a better way to get some of the message out from Node.js.
This issue doesn't have much detail, it was just @sheplu getting it started so we could have a place to discuss, but would love to know if you had ideas. Basically we have lots of folks doing the code work, but not a lot of folks doing the rest of the important work to get the word out and generally build excitement about all the good stuff going on. Is there a good home for this stuff in any of your lineup of work? Is there a particular thing folks like yourselves would be looking for from us that would help us get in the door? Any general advice on how we can do this in a better way for the project?
JS Party is a natural fit for hearing/discussing what's being worked on by the Node team. In fact, we're shipping an episode this week with Matteo Collina and James Snell...
Changelog News is our weekly podcast + newsletter combo (a must-sub, if you haven't already). It's the best place to share news, announcements, blog posts, etc.
Oh cool!! This is very helpful. Ok, so now we need to translate that feed from @bnb (example)into a single post of the top issues, post that to https://github.com/nodejs/nodejs-news-feeder and then figure out a way to auto submit that to both of these each week 📦 😄
Weekly auto-submissions probably wouldn't bear you much fruit tbh. I'd suggest waiting until there's a solid pile of updates and/or a big idea/new thing and then hit us up (with a human) when the time feels right.
Thanks! Yeah I didn't really mean that verbatim I guess, I just meant part of the issue here is that no one can regularly carve out time for this. That is why it never happens. So maybe "auto submission" is not good, but at least having it prep'd by the systems with someone just doing a last mile "is this worth it" check is where we need to land.
EDIT: sorry, re-reading it I guess I probably came across like I was saying something that might waste your time. I didn't mean that. I just meant that as a very important project where most of the investment is in code things, not community things, anything we can do to automate it pays off really quickly so that the few volunteers we have for community parts are not totally and completely overloaded.
Just want to chime in to add that we at Socket are willing to cover important community news and help disseminate to our readers and the broader community. We've written a few posts in this vain:
We're happy to help educate the community and get the word out on important topics. You can reach out to me at [my username] [at] socket [dot] dev or press [at] socket [dot] dev.
Reacted by Wes Todd, Augustin Mauroy and Ulises Gascón
Activity
wesleytodd commentedon Sep 23, 2023
Hey @adamstac & @jerodsanto, we met at the conference earlier this year in Vancouver. We just had a collab summit and were talking about ways we could partner with folks doing content and figure out a better way to get some of the message out from Node.js.
This issue doesn't have much detail, it was just @sheplu getting it started so we could have a place to discuss, but would love to know if you had ideas. Basically we have lots of folks doing the code work, but not a lot of folks doing the rest of the important work to get the word out and generally build excitement about all the good stuff going on. Is there a good home for this stuff in any of your lineup of work? Is there a particular thing folks like yourselves would be looking for from us that would help us get in the door? Any general advice on how we can do this in a better way for the project?
jerodsanto commentedon Sep 25, 2023
Hey Wes, I recall! 👋
JS Party is a natural fit for hearing/discussing what's being worked on by the Node team. In fact, we're shipping an episode this week with Matteo Collina and James Snell...
Pitch us episode ideas here ~> https://jsparty.fm/request
Changelog News is our weekly podcast + newsletter combo (a must-sub, if you haven't already). It's the best place to share news, announcements, blog posts, etc.
Pitch us news to cover here ~> https://changelog.com/submit
Hope this helps!
wesleytodd commentedon Sep 26, 2023
Oh cool!! This is very helpful. Ok, so now we need to translate that feed from @bnb (example)into a single post of the top issues, post that to https://github.com/nodejs/nodejs-news-feeder and then figure out a way to auto submit that to both of these each week 📦 😄
@UlisesGascon thoughts on that idea?
jerodsanto commentedon Sep 26, 2023
Weekly auto-submissions probably wouldn't bear you much fruit tbh. I'd suggest waiting until there's a solid pile of updates and/or a big idea/new thing and then hit us up (with a human) when the time feels right.
wesleytodd commentedon Sep 26, 2023
Thanks! Yeah I didn't really mean that verbatim I guess, I just meant part of the issue here is that no one can regularly carve out time for this. That is why it never happens. So maybe "auto submission" is not good, but at least having it prep'd by the systems with someone just doing a last mile "is this worth it" check is where we need to land.
EDIT: sorry, re-reading it I guess I probably came across like I was saying something that might waste your time. I didn't mean that. I just meant that as a very important project where most of the investment is in code things, not community things, anything we can do to automate it pays off really quickly so that the few volunteers we have for community parts are not totally and completely overloaded.
darcyclarke commentedon Oct 2, 2023
"Create a Node.js Documentary"... yessheplu commentedon Oct 11, 2023
feedback articles for a major conference
feross commentedon Feb 8, 2024
Just want to chime in to add that we at Socket are willing to cover important community news and help disseminate to our readers and the broader community. We've written a few posts in this vain:
We're happy to help educate the community and get the word out on important topics. You can reach out to me at [my username] [at] socket [dot] dev or press [at] socket [dot] dev.