Submission of wallet-framework-dotnet project proposal #16

ntsbs · 2023-09-14T15:36:11Z

No description provided.

Signed-off-by: Sebastian Bickerle <sebastian.bickerle@neosfer.com>

tkuhrt

Thank you for the submission. I am not sure that we will have to get to this review at the meeting on the 20th, but we will see how quickly we make it through the VC-API proposal to see if we have some time for discussion.

tkuhrt · 2023-09-14T20:49:30Z

projects/wallet-framework-dotnet.md

+
+Currently, the framework supports DidComm v1 and AnonCreds. There is an active intention to extend support for other promising protocols, notably DidComm v2, to ensure the framework remains at the forefront of digital identity solutions.
+
+Furthermore, the team is considering the development of SD-JWT credentials as a standalone library. This might transition into a separate project proposal in the future, underscoring the commitment to modular and reusable components in the digital identity space.


Please note that we have two SD-JWT projects in the OpenWallet Foundation. One is in Python and the other in Kotlin. I am not sure if either of those projects would satisfy your need for a standalone library. It would be good to work closely together with these two projects.

I am aware of both projects and I am also in regular contact with both authors. We prefer to have a native library/implementation, but I will make sure that this is aligned with the other implementations.

I would also support having native SD-JWT implementation in different technologies. It's good however to see an alignment between all these projects: For example, share the same test scenarios and exercise their code base over them.

Should we consider extracting the SD-JWT part into its own building block (library) and repository?

tkuhrt · 2023-09-14T20:50:07Z

projects/wallet-framework-dotnet.md

+Furthermore, the team is considering the development of SD-JWT credentials as a standalone library. This might transition into a separate project proposal in the future, underscoring the commitment to modular and reusable components in the digital identity space.
+
+# Alignment with the OpenWallet Foundation Mission
+The wallet-framework-dotnet directly aligns with the OpenWallet Foundation mission by offering an open-source solution that will advance the state of digital identity wallets. The project's focus on implementing OpenID4VC in conjunction with the European Identity Wallet initiative underscores our commitment to global, interoperable standards, and enhances trust and security in digital identity systems.


Are there any plans to expand the wallet beyond identity?

Not yet, we will focus on identity and verifiable credentials

tkuhrt · 2023-09-14T20:50:25Z

projects/wallet-framework-dotnet.md

+The wallet-framework-dotnet directly aligns with the OpenWallet Foundation mission by offering an open-source solution that will advance the state of digital identity wallets. The project's focus on implementing OpenID4VC in conjunction with the European Identity Wallet initiative underscores our commitment to global, interoperable standards, and enhances trust and security in digital identity systems.
+
+# Current Code of Conduct
+tbd


Would you be willing to adopt the LF EU Code of Conduct?

Yes, we would

tkuhrt · 2023-09-14T20:51:32Z

projects/wallet-framework-dotnet.md

+# Source Control
+To be established (Expected: https://github.com/openwallet-foundation/wallet-framework-dotnet)
+
+Suceeds Hyperledger Aries project: [aries-framework-dotnet](https://github.com/hyperledger/aries-framework-dotnet)


Would the plan be to transfer the repo from Hyperledger to OWF? Or would the intention be to archive the one in Hyperledger and start with a new repo in OWF?

tkuhrt · 2023-09-14T20:52:41Z

projects/wallet-framework-dotnet.md

+# Communication Channels
+To be established. (Discord Channel in OWF)
+
+# Project Website


This section is intended to represent if there is an existing website for the project that we need to be aware of.

Then I would add the current repository at aries here

tkuhrt · 2023-09-14T20:53:06Z

projects/wallet-framework-dotnet.md

+
+
+# Infrastructure
+- Requires build and release pipeline for the Nuget package


Can this be handled by GitHub Actions?

I personally have experience with Azure Devops, but I am certain that GitHub Actions would also work

@ntsbs please don't use ADO - Microsoft's stated plan is to EOL ADO once GHA has all the features of ADO. It is also harder to manage.

I am okay with Github Actions

@ntsbs Will this be a possible solution?

You can configure the dotnet command-line interface (CLI) to publish NuGet packages to GitHub Packages and to use packages stored on GitHub Packages as dependencies in a .NET project.

https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry

If this can be set up with OWF, I am happy to do so

While this isn't explicit, the OWF project lifecycle says that " Labs will receive minimal support from the Foundation". Is this pipeline support acceptable to the TAC for labs projects?

That being said, I think this project could easily apply for growth status, as I've said below.

skounis · 2023-09-20T13:13:14Z

projects/wallet-framework-dotnet.md

+
+Currently, the framework supports DidComm v1 and AnonCreds. There is an active intention to extend support for other promising protocols, notably DidComm v2, to ensure the framework remains at the forefront of digital identity solutions.
+
+Furthermore, the team is considering the development of SD-JWT credentials as a standalone library. This might transition into a separate project proposal in the future, underscoring the commitment to modular and reusable components in the digital identity space.


I would also support having native SD-JWT implementation in different technologies. It's good however to see an alignment between all these projects: For example, share the same test scenarios and exercise their code base over them.

skounis · 2023-09-20T13:14:42Z

projects/wallet-framework-dotnet.md

+
+Currently, the framework supports DidComm v1 and AnonCreds. There is an active intention to extend support for other promising protocols, notably DidComm v2, to ensure the framework remains at the forefront of digital identity solutions.
+
+Furthermore, the team is considering the development of SD-JWT credentials as a standalone library. This might transition into a separate project proposal in the future, underscoring the commitment to modular and reusable components in the digital identity space.


Should we consider extracting the SD-JWT part into its own building block (library) and repository?

skounis · 2023-09-20T13:16:17Z

projects/wallet-framework-dotnet.md

+# Issue Tracker
+GitHub Issues
+
+# External Dependencies


Did we check the license of these dependencies for compatibility with Apache 2.0 and re-licensing?

All other Aries projects that we currently depend on are licensed under Apache-2.0

skounis · 2023-09-20T13:18:17Z

projects/wallet-framework-dotnet.md

+
+
+# Infrastructure
+- Requires build and release pipeline for the Nuget package


@ntsbs Will this be a possible solution?

You can configure the dotnet command-line interface (CLI) to publish NuGet packages to GitHub Packages and to use packages stored on GitHub Packages as dependencies in a .NET project.

https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry

hartm · 2023-09-25T15:12:34Z

projects/wallet-framework-dotnet.md

+- Christopher Hempel [CHempel-esatus](https://github.com/CHempel-esatus)
+
+# Proposed Project Governance
+tbd


Do you all want to ask the LF project/legal team for your own charter?

Since there are not as many stakeholders, the governance was so far not an issue. Are there any references with regard to the governance of other projects?

The OWF is a "new" LF foundation, and new LF foundations generally encourage projects to have their own charters written. Hyperledger is an "old" foundation, and has rules that are different (but not encouraged for new foundations these days).

A charter can help you get more contributors and maintainers by explicitly laying out governance rules, making it easier for outsiders to see how to get involved.

hartm · 2023-09-25T15:17:37Z

projects/wallet-framework-dotnet.md

+tbd
+
+# Preferred Maturity Level
+Labs


Is there a reason you all are applying for labs status and not growth? You will not get some project services as a labs project that you currently have as a part of Aries (e.g. CI/CD, security programs, etc.). While I can't speak for the TAC, it may make sense to consider applying as a growth project.

I thought Labs is the general entry state and a project will be promoted to growth if it gets more adoption

You can apply for any status that you want. There are no guarantees that you'll get it, but you can always ask the TAC.

Labs might be the default status for new projects without much code, but you all aren't submitting a "new" open source project.

hartm · 2023-09-25T15:18:57Z

projects/wallet-framework-dotnet.md

@@ -0,0 +1,65 @@
+# Project Name
+Wallet Framework .NET (wallet-framework-dotnet)


This name probably isn't going to work if you want to become a growth or impact project, as there will most likely be trademark issues. Are you all OK with renaming to something more distinctive (or trademarkable)?

Are your concerns mostly due to .NET? Maybe wallet-framework-csharp would be an alternative

No, my concerns are mostly due to the distinctiveness of the name.

Signed-off-by: Sebastian Bickerle <sebastian.bickerle@neosfer.com>

tkuhrt · 2023-10-05T18:16:36Z

@ntsbs : Could you please update this branch so that we can merge the project proposal?

tkuhrt · 2023-10-07T18:10:29Z

Approved by TAC on October 4, 2023

ntsbs requested review from tkuhrt, troyronda, wenjing, skounis, quartzjer and petecool as code owners September 14, 2023 15:36

Sebastian Bickerle added 2 commits September 14, 2023 17:43

created proposal for wallet-framework-dotnet

7d351b9

Signed-off-by: Sebastian Bickerle <sebastian.bickerle@neosfer.com>

added currently supported protocols

fa6af40

Signed-off-by: Sebastian Bickerle <sebastian.bickerle@neosfer.com>

ntsbs force-pushed the wallet-framework-dotnet-proposal branch from d46a7aa to fa6af40 Compare September 14, 2023 15:44

tkuhrt reviewed Sep 14, 2023

View reviewed changes

skounis reviewed Sep 20, 2023

View reviewed changes

hartm reviewed Sep 25, 2023

View reviewed changes

added maintainer

e9007c7

Signed-off-by: Sebastian Bickerle <sebastian.bickerle@neosfer.com>

Merge branch 'main' into wallet-framework-dotnet-proposal

ac6df81

ntsbs requested a review from davidz25 as a code owner October 7, 2023 14:53

tkuhrt merged commit f6283c1 into openwallet-foundation:main Oct 7, 2023
1 check passed


		Currently, the framework supports DidComm v1 and AnonCreds. There is an active intention to extend support for other promising protocols, notably DidComm v2, to ensure the framework remains at the forefront of digital identity solutions.

		Furthermore, the team is considering the development of SD-JWT credentials as a standalone library. This might transition into a separate project proposal in the future, underscoring the commitment to modular and reusable components in the digital identity space.



		# Infrastructure
		- Requires build and release pipeline for the Nuget package

		@@ -0,0 +1,65 @@
		# Project Name
		Wallet Framework .NET (wallet-framework-dotnet)

Submission of wallet-framework-dotnet project proposal #16

Submission of wallet-framework-dotnet project proposal #16

Conversation

ntsbs commented Sep 14, 2023

tkuhrt left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

tkuhrt commented Oct 5, 2023

tkuhrt commented Oct 7, 2023