Trivial

1.   General Information

Project Name:
Trivial

License:
MIT

Contributor (Company, Organization or individual name(s)):
Kingcean (@kingcean)

Existing OSS Project? (Yes/No):
Yes.

Source Code URL:
https://github.com/nuscien/trivial

Project Homepage URL (if different):

Project Transfer Signatories:
Will be submitted via e-mail to contact@dotnetfoundation.org.

2.   Description

Trivial libraries contain a lot of utilities, models and components, which are trivial but useful, to help you to focus on the business logic of your projects.

3.   Project Governance

Project Lead:
Kingcean (@kingcean)

Name:
Email: kingcean@live.com
GitHub Profile URL: https://github.com/kingcean

Committers:
Kingcean (@kingcean)

Governance Model:
Changes are proposed in GitHub Issues and Pull Requests. Changes are reviewed by the core contributors and the community.

CLA
No.

CLA Notification Alias
N/A

Project Transfer Type
Assignment (open to feedback)

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.

5.   Eligibility Criteria

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

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

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

• 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

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

• The project uses Source Link.
  Yes

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

• The project code signs their artifacts as appropriate.
  No

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

• 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

• 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

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

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

• The project has a published Security Policy.
  Yes

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

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

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

6.   PR Plan

7.   Infrastructure Requirements

Use Azure Pipelines.

7.   Additional Notes

-/-