Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue: New .NET Foundation Project Application #325

Open
14 of 18 tasks
RealDotNetDave opened this issue Sep 13, 2023 · 1 comment
Open
14 of 18 tasks

Issue: New .NET Foundation Project Application #325

RealDotNetDave opened this issue Sep 13, 2023 · 1 comment
Assignees
Labels
project application project support Use this label to request support for an existing .NET Foundation project

Comments

@RealDotNetDave
Copy link

Project Name

Spargine

License

GNU LESSER GENERAL PUBLIC LICENSE

Contributor

David McCarter - dotNetTips.com

Existing OSS Project?

Yes

Source Code URL

https://github.com/RealDotNetDave/dotNetTips.Spargine

Project Homepage URL

https://dotnettips.wordpress.com/spargine/

Project Transfer Signatories

Description

These assemblies encapsulate the foundational code I have been developing since the early days of .NET 2. I am not only a devoted user of these assemblies in all of my projects, but they are also currently in production at most of the companies I have worked for.

Current assemblies are:

  • DotNetTips.Spargine: Common code for the Windows platform.
  • DotNetTips.Spargine.Core: Core assembly that contains code that is also used by the other assemblies that make up Spargine.
  • DotNetTips.Extensions: Assembly: for extension methods.
  • DotNetTips.Spargine.Tester: Code that generates random data for use in unit tests and benchmark testing.
  • DotNetTips.Spargine.Benchmarking: Code and classes that make writing benchmark tests easier when using BenchmarkDotNet.

Name

David McCarter

Email

[email protected]

GitHub Profile URL

https://github.com/RealDotNetDave

Committers

No response

Governance Model

The code will be reviewed by myself via pull requests.

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

None that I know of.

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 will heavily promote the announcements via social media and on dotNetTips.com.

Infrastructure Requirements Summary

N/A

Additional Notes

This is the common code that I have been writing since .NET 2. I heavily use proper coding standards, and I benchmark each major release to ensure the best code performance. The purpose of this code to to put the code we wright over and over again into one set of assemblies.

Along with documenting the code via XML comments, I write an article for every release and more that can be found here: https://dotnettips.wordpress.com/category/spargine/

@RealDotNetDave RealDotNetDave added project application project support Use this label to request support for an existing .NET Foundation project labels Sep 13, 2023
@sbwalker
Copy link
Collaborator

@RealDotNetDave thank you for your application... the Project Committee reviewed your application last week. The .NET Foundation Project Charter (https://github.com/dotnet-foundation/projects) contains Eligibility Criteria related to licensing:

Licenses and Copyright

  • The code is offered under a standard, permissive open source license which has been approved by the .NET Foundation.

At this time the .NET Foundation does not accept projects licensed under non-permissive / copyleft licenses. The GNU LESSER GENERAL PUBLIC LICENSE is not considered to be a permissive license.

did notice that your project was originally licensed under Apache 2.0 (permissive) however the license was later changed to the LGPL on Jan 18, 2021. I am sure you had valid reasons for this change in terms of making the license more restrictive.

At this time based on the eligibility criteria, the Project Committee will need to place your application on hold. If anything changes which would make your project eligible for membership in the future, the Committee will review your application once more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
project application project support Use this label to request support for an existing .NET Foundation project
Projects
None yet
Development

No branches or pull requests

3 participants