forked from nodejs/node
-
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
doc: document process for sharing project news
Fixes: nodejs/TSC#1333 Signed-off-by: Michael Dawson <mdawson@devrus.com> PR-URL: nodejs#47189 Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com> Reviewed-By: Chengzhong Wu <legendecas@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
- Loading branch information
Showing
1 changed file
with
30 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,30 @@ | ||
# Sharing project news | ||
|
||
The project aims to make it easy | ||
to share project news with those who publish newsletters | ||
that cover Node.js. | ||
|
||
The project's approach is as follows: | ||
|
||
* The project will create one "What's new in YYYY" discussion item in | ||
the `nodejs/node` repo for news related to Node.js core. | ||
* Teams/groups can create a "what's new in YYYY" issue or discussion item | ||
in one or more of their repositories. As an example see | ||
[What's new in the Node-API and node-addon-api world? - 2023 version](https://github.com/nodejs/abi-stable-node/issues/446). | ||
* Collaborators periodically add news as additional comments on these | ||
issues throughout the year. | ||
* At the end of each year the issue is closed and if appropriate a | ||
new one is created. | ||
* A list of these documents is maintained in the section below as a | ||
quick way to find them. | ||
* The next-10 team reaches out to teams/groups on an ad hoc basis | ||
to ensure teams know about the option for sharing news. | ||
* The next-10 team reaches out to those who publish newsletters ad hoc | ||
to let them know about this approach and how they can find the updates. | ||
|
||
We trust/expect collaborators to post project related news versus news | ||
that promotes a specific company or commercial interest. | ||
|
||
## Teams doing updates | ||
|
||
* [node-api/node-addon-api](https://github.com/nodejs/abi-stable-node/issues/446). |