-
Notifications
You must be signed in to change notification settings - Fork 134
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
Comments
This was referenced Jan 20, 2023
This was referenced Jan 30, 2023
We discussed in the last TSC meeting, some positive feedback no concerns raised by those who where there. |
I voluteered to submit a PR to document/capture the process where further discusion can take place. |
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
Fixes: nodejs/TSC#1333 Signed-off-by: Michael Dawson <mdawson@devrus.com>
RafaelGSS
pushed a commit
to nodejs/node
that referenced
this issue
Apr 5, 2023
Fixes: nodejs/TSC#1333 Signed-off-by: Michael Dawson <mdawson@devrus.com> PR-URL: #47189 Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com> Reviewed-By: Chengzhong Wu <legendecas@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
RafaelGSS
pushed a commit
to nodejs/node
that referenced
this issue
Apr 6, 2023
Fixes: nodejs/TSC#1333 Signed-off-by: Michael Dawson <mdawson@devrus.com> PR-URL: #47189 Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com> Reviewed-By: Chengzhong Wu <legendecas@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
RafaelGSS
pushed a commit
to nodejs/node
that referenced
this issue
Apr 7, 2023
Fixes: nodejs/TSC#1333 Signed-off-by: Michael Dawson <mdawson@devrus.com> PR-URL: #47189 Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com> Reviewed-By: Chengzhong Wu <legendecas@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
danielleadams
pushed a commit
to nodejs/node
that referenced
this issue
Jul 6, 2023
Fixes: nodejs/TSC#1333 Signed-off-by: Michael Dawson <mdawson@devrus.com> PR-URL: #47189 Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com> Reviewed-By: Chengzhong Wu <legendecas@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
We could also create such an issue for any collaborator to post "news" to for nodejs/node as well.
The text was updated successfully, but these errors were encountered: