Issue: New .NET Foundation Project Application

[VahidFarahmandian]

Project Name

Jinget

License

MIT

Contributor

Vahid Farahmandiam

Existing OSS Project?

Yes

Source Code URL

https://github.com/VahidFarahmandian/Jinget

Project Homepage URL

No response

Project Transfer Signatories

Vahid Farahmandiam farahmandian2011@jinget.ir

Description

Jinget is a framework written using .NET 6.0 , and built using DDD+CQRS. Jinget boosts your productivity by providing robust infrastructure for source codes.

Name

Vahid Farahmandian

Email

farahmandian2011@gmail.com

GitHub Profile URL

https://github.com/VahidFarahmandian

Committers

Every one can commit to this repository.

Governance Model

Contributors write codes in their custom branches and then create PR to merge the changes wirh main branch. Each change in code should have appropriate comment in source code and also provide runable unit tests. For PR to become merged, all unit tests should be passed.

Currently I am the only one who can review the PR and decide to approve/reject it.

If needed, changes are published via CI/CD routines(preview/final release) as NuGet packages on nuget.org.

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?

Currently, CLA is not required

CLA Notification Alias

farahmandian2011@gmail.com

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.

PR Plan Summary

The main reason is to increase participation in the development, completion and improvement of this framework.

Infrastructure Requirements Summary

For hosting Jinget.Blazor test project, it will be necessary to support Blazor Server Side deployment.

Additional Notes

In recent years, I have made many efforts to introduce Jinget. I have introduced it many times in various Microsoft programs, including .NET Docs Show and On .NET Live. I would be very honored to have Jinget join the .NET Foundation.