RConfig .NET Foundation Project Application

Project Name

RConfig

License

MIT

Contributor

alizorlu

Existing OSS Project?

Yes

Source Code URL

https://github.com/alizorlu/RConfig

Project Homepage URL

https://github.com/alizorlu/RConfig

Project Transfer Signatories

Ali Zorlu azorlua@gmail.com

Description

With .Net Core, it allows you to keep the json files of your applications securely encrypted on your remote server and easily integrate them into your applications.

Name

Ali Zorlu

Email

azorlua@gmail.com

GitHub Profile URL

https://github.com/alizorlu

Committers

No response

Discord Ids

No response

Governance Model

Json extention (https://github.com/alizorlu/RConfig.Crypto), which is written for all versions on .net 6, can be tested and its stability can be checked in all versions.

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

Migrate remote changes,
Providing Postgresql support
Legacy .Net framework support

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.

PR Plan Summary

I want to contribute to the community because I think the project will contribute and facilitate the .net family and because I am a .net developer.

Infrastructure Requirements Summary

No response

Additional Notes

No response