Moving from our CNA to OpenJS CNA
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 694
- Forks
- 142
- PR merge metrics
- No merged PRs in 30d
Description
As recently announced by OpenJS, they now own their CNA.
I have been talking with @ruddermann over the past month about the possibility of including Node.js in the OpenJS CNA umbrella. As stated by @mcollina in the TSC channel
We are a CNA only as a defensive measure to have the final say. I trust OpenJS to be a good CNA.
I feel it would be great to fold in their CNA as well. Nothing should change from our security release process or in the automation.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the OpenJS CNA announcement and the issue's references to the security release process and automation. Determine the implications of placing Node.js under the OpenJS CNA umbrella while preserving those processes; done requires a documented TSC decision and an agreed transition scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- release, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100