Project proposal applying to move ACA-Py to OWF #42
Conversation
Signed-off-by: Stephen Curran <[email protected]>
swcurran
requested review from
tkuhrt,
rolsonquadras,
wenjing,
skounis,
petecool,
davidz25 and
aceshim
as code owners
Signed-off-by: Stephen Curran <[email protected]>
|
@swcurran : Thank you for the proposal. I would like to add this as an agenda item for our next TAC meeting, which is October 18th @ 7:00 AM US/Pacific. Would that time work for the team to represent this proposal? |
|
Sounds good. I’ll let others in the ACA-Py community know. Presumably, we’re cover all of the related proposals at the same time? |
|
Not sure if we will make them through all of them, but we can definitely bring them to the attention of the TAC. I figure we start with this one and see if we can get approval for all of them, but we do tend to take a while. :) |
projects/aca-py.md
Outdated
|
|
||
| ## External Dependencies | ||
|
|
||
| The ACA-Py dependency list is maintained in the [source repository](https://github.com/hyperledger/aries-cloudagent-python/blob/main/pyproject.toml). A NOTICES file is also in the repository, but needs to be updated. |
There was a problem hiding this comment.
Can you comment on the licenses for these dependencies?
There was a problem hiding this comment.
I added a quick note to the proposal. All are open source, and I'm sure that vast majority are Apache 2, but we can do an inventory if needed.
| * [ACA-Py Plugins](https://github.com/hyperledger/aries-acapy-plugins) — registry published to [https://plugins.aca-py.org](https://plugins.aca-py.org) | ||
| * [ACA-Py Tools](https://github.com/hyperledger/aries-acapy-tools) — various tools related to ACA-Py including those for upgrade data migrations. | ||
| * [ACA-Py Controllers](https://github.com/hyperledger/aries-acapy-controllers/blob/main/AliceFaberAcmeDemo/README.md) — demos of Aries ACA-Py controllers (business logic) using different technical stacks. | ||
| * [VC-Authn-OIDC](https://github.com/bcgov/vc-authn-oidc) — a multi-tenant OpenIDConnect Identity Provider (IdP) component to enable OIDC Relying Parties to use Verifiable Credential presentations for authentication. |
There was a problem hiding this comment.
Is the intention to move all of these repos to OWF, including the one that is currently in the bcgov organization?
There was a problem hiding this comment.
Yes. The BC Gov (vc-authn-oidc) one could have been contributed to Hyperledger some time ago, and the team believes it would be a good time to contribute it. Its mature, well-used and continues to evolve based on production use cases.
Ugh...got the wrong date. This should have said September 18th @ 7:00 AM US/Pacific. My bad. |
Signed-off-by: Stephen Curran <[email protected]>
|
We support this project. Many members of GAN use ACA-Py heavily. |
Signed-off-by: Stephen Curran <[email protected]>
Signed-off-by: Stephen Curran <[email protected]>
This PR contains a project proposal applying to move the Hyperledger Aries sub-project Aries Cloud Agent Python (ACA-Py) to the OpenWallet Foundation. ACA-Py (Aries Cloud Agent Python) is an open-source framework designed to facilitate the creation, management, and utilization of decentralized digital identities. ACA-Py enables secure, interoperable communication between entities using decentralized identifiers (DIDs) and verifiable credentials, adhering to standards such as DIDComm, OpenID4VCs and the W3C Verifiable Credentials. This proposal has been vetted by the Aries community, and we look forward to continuing that discussion in the OWF.
@dbluhm, @tkuhrt, @jamshale, @TelegramSam, @jljordan42 @brianbehlendorf, @WadeBarnes, @andrewwhitehead, @chumbert
ACA-Py includes several repositories that would transition together with the core ACA-Py repo, as noted in the project proposal.
The Aries community will shortly follow up with 3 other project proposal PRs to apply to move other Aries sub-projects to OWF, and a couple of others could follow over time. We also will be submitting a proposal to start a "Wallet Interoperability" Special Interest Group (SIG) at OWF that will be a forum for promoting interoperability across these and other related projects, specifications and standards. This note will be updated with links to the related PRs for: