ampproject / ampproject/wg-security-privacy
Transitioning responsible security disclosures to the OpenJSF
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 2
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
- Tracking how to handle responsible security disclosure at the OpenJSF in https://github.com/openjs-foundation/cross-project-council/issues/326.
- The Node.js Security WG is working on this.
- It is now suggesting to broaden the discussion by including other projects in the conversation. It would be great if AMP sent a representative there.
/cc @mrjoro
Contributor guide
No contributing guide indexed for this repository
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 by reading the linked OpenJS Foundation Cross Project Council issue #326 and Node.js Security WG issue #511 to understand the proposed disclosure process and broader discussion. The issue mentions including AMP in that conversation, but names no files, tests, or concrete repository change; completion would require an agreed AMP representative and process direction.
Written by the indexing model from the issue text.
Assessment
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100