dotnet-foundation / dotnet-foundation/projects

Issue: New .NET Foundation Project Application - Spargine

Open
#325 12 comments 0 reactions 2 assignees View on GitHub

@sbwalker is already working on this.

Since Sep 13, 2023.

project application project support
Dominant language
No language data
Stars
157
Forks
37
PR merge metrics
No merged PRs in 30d

Description

Project Name

Spargine

License

MIT License

Contributor

David McCarter - dotNetTips.com

Existing OSS Project?

Yes

Source Code URL

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

Project Homepage URL

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

Project Transfer Signatories
  • David McCarter dotnetdave@live.com
Description

These assemblies represent the foundational code I’ve meticulously developed and refined since the inception of .NET 2. Over the years, they’ve become an integral part of my development toolkit, powering all of my projects. Beyond my personal use, these assemblies are actively deployed in production environments across many of the companies I’ve had the privilege to work with, demonstrating their reliability and versatility.

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

dotnetdave@live.com

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 I’ve been crafting and refining since the early days of .NET 2. I adhere strictly to proper coding standards and benchmark each major release to ensure optimal performance. The primary purpose of this codebase is to consolidate the repetitive code we frequently write into a unified set of assemblies, streamlining development and improving efficiency.

To complement the code, I provide thorough documentation using XML comments and publish a detailed article with every release. You can explore these articles and more here:
https://dotnettips.wordpress.com/category/spargine/

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.