- From: Manu Sporny <msporny@digitalbazaar.com>
- Date: Wed, 13 Apr 2022 17:16:03 -0400
- To: W3C Credentials CG <public-credentials@w3.org>
Hey CCG Chairs (and Emeritus Chairs), This question came up during a VC API telecon: Can Github repositories that support an existing CCG work item be moved to CCG automatically, or does every Github repository need to go through the work item process? For example, if "Work Item X" is adopted as a CCG work item, then we create a "Work Item X Use Cases", "Work Item X Test Suite", or "Work Item X Developer Guide" in personal/corporate Github repositories... do those latter three items need to go through the work item adoption process, or can the supporting items just be moved over to CCG as long as the author and Work Item Group agree to move those things over? This is of immediate relevance to the VC API group as we have the following test suite repositories that we expect to contribute to the CCG over the next couple of months: * Implementations (VC API implementer configurations and authz Github secrets) * Assertion libraries (e.g., test VC, Data Integrity, and JWT well-formed-ness (not crypto) checking) * Basic VC Issuer API * Basic VC Verifier API * Cryptosuites (Ed25519, NIST ECDSA, Koblitz ECDSA, VC- JWT, BBS+, etc.) * Basic Presentation Exchange * Credential Refresh 2021 * Industry Vertical VCs (Student ID, Permanent Resident Card, Skill, Transcript, etc.) Moving every single one of those things through the CCG work item process feels like overkill if folks in the VC API group are already doing the work as a part of the VC API testing initiative. The question to the Chairs are, can we just move those test suites into CCG, or do we need to move every single one of those things through the CCG work item process? -- manu -- Manu Sporny - https://www.linkedin.com/in/manusporny/ Founder/CEO - Digital Bazaar, Inc. News: Digital Bazaar Announces New Case Studies (2021) https://www.digitalbazaar.com/
Received on Wednesday, 13 April 2022 21:16:19 UTC