Add WinDebloat as a new project

Project Name

WinDebloat

License

MIT

Contributor

Simon Cropp

Existing OSS Project?

Yes

Source Code URL

https://github.com/SimonCropp/WinDebloat

Project Homepage URL

https://github.com/SimonCropp/WinDebloat

Project Transfer Signatories

• Simon Cropp simon.cropp@gmail.com

Description

A dotnet tool that removes the bloat in Windows

Name

Simon Cropp

Email

simon.cropp@gmail.com

GitHub Profile URL

https://github.com/SimonCropp

Committers

https://github.com/SimonCropp

Governance Model

describe how new code changes are proposed to the project,

via GH issue, GH pull request, twitter, zoom, email.

how those changes are reviewed and how a decision is made to accept proposed changes.

Discussion with the submitter. ensure correctness, value to other consumers, and no known technical debt.

Also describe the process for identifying and appointing new committers.

Currently none.

TBH I have not needed an formalized Governance Model for my OSS projects. Happy to consider suggestions for recommended models.

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

simon.cropp@gmail.com

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

promote through twitter and mastodon.

Infrastructure Requirements Summary

How will build servers be operated?

AppVeyor

Any web hosting or service hosting requirements?

no

Do we need to set up SSL certificates or provide Authenticode Code Signing arrangement for releases?

no

Additional Notes

No response