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

Sharing project news #1333

Closed
mhdawson opened this issue Jan 20, 2023 · 3 comments
Closed

Sharing project news #1333

mhdawson opened this issue Jan 20, 2023 · 3 comments
Assignees

Comments

@mhdawson
Copy link
Member

The next-10 team had discussed formalizing relationships with Communications Channel to JS Newsletters/Periodicals in nodejs/next-10#110 and asked for Foundation help. It seems like the Foundation won't have time to support in the forseable future.

In the last meeting we discussed simpler/lower overhead approach

  1. teams/groups can create a "what's new in 2023" issue if their repo if they want. The Node-API team was already planning to do this and to add notable news we discuss in team meetings on a regular basic
  2. We document this approach
  3. We give an FYI to groups like
  • JS Weekly
  • Node Weekly
  • ES.Next News
  • Bytes
  1. If they are interested they can check out the issues for the teams/groups periodically for news

We could also create such an issue for any collaborator to post "news" to for nodejs/node as well.

@mhdawson
Copy link
Member Author

mhdawson commented Feb 6, 2023

We discussed in the last TSC meeting, some positive feedback no concerns raised by those who where there.

@mhdawson
Copy link
Member Author

mhdawson commented Feb 6, 2023

I voluteered to submit a PR to document/capture the process where further discusion can take place.

@mhdawson mhdawson self-assigned this Feb 6, 2023
@mhdawson
Copy link
Member Author

mhdawson commented Mar 1, 2023

Still plan to do this, but will be out for a few weeks.

mhdawson added a commit to mhdawson/io.js that referenced this issue Mar 21, 2023
RafaelGSS pushed a commit to nodejs/node that referenced this issue Apr 5, 2023
Fixes: nodejs/TSC#1333

Signed-off-by: Michael Dawson <[email protected]>

PR-URL: #47189
Reviewed-By: Gireesh Punathil <[email protected]>
Reviewed-By: Chengzhong Wu <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
RafaelGSS pushed a commit to nodejs/node that referenced this issue Apr 6, 2023
Fixes: nodejs/TSC#1333

Signed-off-by: Michael Dawson <[email protected]>

PR-URL: #47189
Reviewed-By: Gireesh Punathil <[email protected]>
Reviewed-By: Chengzhong Wu <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
RafaelGSS pushed a commit to nodejs/node that referenced this issue Apr 7, 2023
Fixes: nodejs/TSC#1333

Signed-off-by: Michael Dawson <[email protected]>

PR-URL: #47189
Reviewed-By: Gireesh Punathil <[email protected]>
Reviewed-By: Chengzhong Wu <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
danielleadams pushed a commit to nodejs/node that referenced this issue Jul 6, 2023
Fixes: nodejs/TSC#1333

Signed-off-by: Michael Dawson <[email protected]>

PR-URL: #47189
Reviewed-By: Gireesh Punathil <[email protected]>
Reviewed-By: Chengzhong Wu <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
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

Successfully merging a pull request may close this issue.

1 participant