dotnet-foundation / dotnet-foundation/projects
Issue: New .NET Foundation Project Application
@sbwalker is already working on this.
Since Sep 11, 2023.
- Dominant language
- No language data
- Stars
- 157
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
Project Name
CodeBehind
License
GPLv3
Contributor
Elanat
Existing OSS Project?
Yes
Source Code URL
https://github.com/elanatframework/Code_behind
Project Homepage URL
No response
Project Transfer Signatories
- Mohammad Rabie mohammad_rabiyi@aol.com
Description
CodeBehind is a backend framework based on the MVC structure which provides the possibility of creating dynamic aspx files in ASP.NET Core.
Name
Mohammad Rabie
mohammad_raniyi@aol.com
GitHub Profile URL
https://github.com/elanatframework
Committers
No response
Governance Model
Proposals with the most requests for changes will be voted on, and the list of committed committers will have the right to vote.
Committers are approved that provide strong and solid documentation for the need to apply changes.
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.
PR Plan Summary
No response
Infrastructure Requirements Summary
No response
Additional Notes
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.