GeezerVison is showing github.com — doc: document process for sharing project news · nodejs/node@296577a
File tree
Expand file treeCollapse file tree
Open diff view settings
Expand file treeCollapse file tree
Open diff view settings
Collapse file
Copy file name to clipboard +30Lines changed: 30 additions & 0 deletions - Display the source diff
- Display the rich diff
| Original file line number | Diff line number | Diff line change |
|---|
|
| 1 | +# Sharing project news |
| 2 | + |
| 3 | +The project aims to make it easy |
| 4 | +to share project news with those who publish newsletters |
| 5 | +that cover Node.js. |
| 6 | + |
| 7 | +The project's approach is as follows: |
| 8 | + |
| 9 | +* The project will create one "What's new in YYYY" discussion item in |
| 10 | + the `nodejs/node` repo for news related to Node.js core. |
| 11 | +* Teams/groups can create a "what's new in YYYY" issue or discussion item |
| 12 | + in one or more of their repositories. As an example see |
| 13 | + [What's new in the Node-API and node-addon-api world? - 2023 version](https://github.com/nodejs/abi-stable-node/issues/446). |
| 14 | +* Collaborators periodically add news as additional comments on these |
| 15 | + issues throughout the year. |
| 16 | +* At the end of each year the issue is closed and if appropriate a |
| 17 | + new one is created. |
| 18 | +* A list of these documents is maintained in the section below as a |
| 19 | + quick way to find them. |
| 20 | +* The next-10 team reaches out to teams/groups on an ad hoc basis |
| 21 | + to ensure teams know about the option for sharing news. |
| 22 | +* The next-10 team reaches out to those who publish newsletters ad hoc |
| 23 | + to let them know about this approach and how they can find the updates. |
| 24 | + |
| 25 | +We trust/expect collaborators to post project related news versus news |
| 26 | +that promotes a specific company or commercial interest. |
| 27 | + |
| 28 | +## Teams doing updates |
| 29 | + |
| 30 | +* [node-api/node-addon-api](https://github.com/nodejs/abi-stable-node/issues/446). |