Frank.Libraries Application

1.   General Information

Project Name: Frank.Libraries

License: MIT

Contributor (Company, Organization or individual name(s)): Frank R. Haugen

Existing OSS Project? (Yes/No): Yes

Source Code URL: https://github.com/frankhaugen/Frank.Libraries

Project Homepage URL (if different):

Project Transfer Signatories: Frank Reidar Haugen (frank.haugen@gmail.com)

2.   Description

A set of useful libraries for .net, that are "quality of life"-improvements, from Enums of country names, to extension methods for pivoting a DataTable

3.   Project Governance

Project Lead: Frank. R. Haugen

Name: Frank R. Haugen
Email: frnak.haugen@gmail.com
GitHub Profile URL: https://github.com/frankhaugen

Committers: frankhaugen, stzoran1

Governance Model: Any contributions, given that they makes sense, are not too breaking and don't contradict any plans are welcomed and accept by default. Contributors should never be limited as long as their code is acceptable

CLA
There where no CLA in place when the one contribution was received, (this contribution was later refactored "to oblivion" and as such is no longer "part" of the current code-base). Contributions from bots are assumed not relevant for this issue

CLA Notification Alias: frank.haugen@gmail.com

Assignment Model. Under the .NET Foundation assignment model, project ownership and other intellectual property is assigned to the .NET Foundation and the .NET Foundation agrees to grantback a license to the contributor(s).

Contribution Model. Under the .NET Foundation contribution model, a project retains ownership of the copyright, but grants the .NET Foundation a broad license to the project’s code and other intellectual property. The project also confirms that the project’s submissions to .NET Foundation are its own original work (there are also instructions for any third party materials that might be included).

4.   Repository Layout

The .NET Foundation host guidance for new projects and details on recommended structure here:
https://github.com/dotnet/home/tree/master/guidance

Note that the open source repository should be the master where changes are made by the core development team using the same PR process that is used for non-committer contributions.

Please define below any changes you would want to make to your repositories as part of the process of joining the .NET Foundation

5. Eligibility Criteria

Please complete the following for your project

• The project is built on the .NET platform and/or creates value within the .NET ecosystem.

• Yes
• No

• The project produces source code for distribution to the public at no charge.

• Yes
• No

• The project's code is easily discoverable and publicly accessible (preferably on GitHub).

• Yes
• No

• 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).

• Yes
• No

• When applicable, project must use reproducible build settings in its toolchain.

• Yes
• No

• The project uses Source Link.

• Yes
• No

• The project uses either embedded PDBs or publish symbol packages to NuGet (if applicable).

• Yes
• No

• The project code signs their artifacts as appropriate.

• Yes
• No

• The project organization has 2FA enabled. Requiring 2FA must be done as part of onboarding if not already enabled.

• Yes
• No

• 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).

• Yes
• No

• 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.

• Yes
• No

• The copyright ownership of everything that the project produces is clearly defined and documented.

• Yes
• No

• The project has a public issue tracker where the status of any defect can be easily obtained.

• Yes
• No

• The project has a published Security Policy.

• Yes
• No

• The project has a home page which provides high level information about its status and purpose.

• Yes
• No

• The project has a public communication channel where community members can engage with maintainers.

• Yes
• No

• The project has a publicly available location where members can review and contribute to documentation.

• Yes
• No

6.   PR Plan

The plan is to write an article about the process of attempting or succeeding in joining the foundation, and also publish videos on YouTube to showcase the nugets

7.   Infrastructure Requirements

All infrastructure is covered by GitHub actions

8.   Additional Notes

It's understood that there might be some changes required, if for nothing else, to get the legal stuff correct