Issue: New .NET Foundation Project Application (Azure Key Vault Emulator) #441
Description
Project Name
Azure Key Vault Emulator
License
Apache 2.0
Contributor
James Gould
Existing OSS Project?
Yes
Source Code URL
https://github.com/james-gould/azure-keyvault-emulator
Project Homepage URL
No response
Project Transfer Signatories
- James Gould hello@jamesgould.dev
Description
Emulates the functionality of Azure Key Vault from within a container, allowing developers to easily develop applications using secure storage without requiring a hosted, paid for Azure Resource at dev time.
Name
James Gould
GitHub Profile URL
https://github.com/james-gould
Committers
Current
Previous
Discord Ids
- James Gould (james.gould)
Governance Model
I am currently the only contributor, features are dictated by the functionality of the Azure Key Vault REST API.
CLA
- If already an OSS project, was a Contribution License Agreement in place for contributions accepted?
How does the project check who has signed one?
No response
CLA Notification Alias
No response
Select the Project Transfer Agreement model
Contribution
Repository Layout
No response
Eligibility Criteria
- The project is built on the .NET platform and/or creates value within the .NET ecosystem.
- The project produces source code for distribution to the public at no charge.
- The project's code is easily discoverable and publicly accessible (preferably on GitHub).
- The project contains a build script that can produce deployable artifacts that are identical to the official deployable artifacts, with the exception of code signing (Exception may be granted for strong name keys, though strongly encouraged to be committed. Exception relies on OSS signing being in the build script for public builds).
- When applicable, project must use reproducible build settings in its toolchain.
- The project uses Source Link.
- The project uses either embedded PDBs or publish symbol packages to NuGet (if applicable).
- The project code signs their artifacts as appropriate.
- The project organization has 2FA enabled. Requiring 2FA must be done as part of onboarding if not already enabled.
- Libraries that are mandatory dependencies of the project are offered under a standard, permissive open source license which has been approved by the .NET Foundation (exceptions include a dependency that is required by the target platform where no alternative open source dependency is available such as the .NET Framework or a hardware specific library).
- Committers are bound by a Contributor License Agreement (CLA) and/or are willing to embrace the .NET Foundation's CLA when the project becomes a Member.
- The copyright ownership of everything that the project produces is clearly defined and documented.
- The project has a public issue tracker where the status of any defect can be easily obtained.
- The project has a published Security Policy.
- The project has a home page which provides high level information about its status and purpose.
- The project has a public communication channel where community members can engage with maintainers.
- The project has a publicly available location where members can review and contribute to documentation.
Describe why you are applying for Project Membership.
Key Vault is a widely used service in .NET enterprise applications; with the uptick in .NET Aspire integrations across the industry having a marker of support and validation would be beneficial to those wishing to make use of the project.
Infrastructure Requirements Summary
Code Signing for releases would be beneficial given the context of the application.
Additional Notes
The original Github Repository went into an archived state in October 2024, the project has since been forked and massively developed from its' previous position. Due to the differences, and the archived repo, the fork has been detached (with copyrights retained).
I've retained the original Apache 2.0 license (with copyright updates) and issued a NOTICE describing the detatched state of the project.