Open saschanaz opened 3 years ago
Just as a possible counterpoint to this, from the proposed webappsec charter, AFAIU the intention is to propose new changes in the WICG first, and only later merge them here (e.g. similarly to https://github.com/WICG/uuid). To that end, it may be better to keep the spec extensible to some extent, so that that remains possible.
I'm also working on specifying secure curves in Web Crypto, in the same vein. Obviously, I'm also happy to just make a PR and let people comment there, but it seems substantial enough that a separate repo for comments and discussion seems not unreasonable. @mikewest and @annevk I'd be happy to hear your thoughts, though.
I think incubating new ideas in separate repositories and even distinct venues is fine. I don't think that necessarily warrants "extensibility" however. I would expect any such proposal to detail how it would amend the base specification. And ideally an upstream issue would be filed to make the community around the base specification aware of the proposal.
Context: https://github.com/w3c/webcrypto/pull/286#issuecomment-936461968 Related: #293
Probably worth to have a dedicated issue 😄