Skip to content

Issue: New .NET Foundation Project Application #458

@ZjzMisaka

Description

@ZjzMisaka

Project Name

PowerThreadPool

License

MIT

Contributor

Zhang Junzhi

Existing OSS Project?

Yes

Source Code URL

https://github.com/ZjzMisaka/PowerThreadPool

Project Homepage URL

https://github.com/ZjzMisaka/PowerThreadPool/wiki

Project Transfer Signatories

Zhang Junzhi zjzmisaka@outlook.com
Huang Haolin admin@dlnn.net

Description

A comprehensive and efficient lock-free thread pool with granular work control, flexible concurrency, robust error handling, and easy work management for both sync and async workloads.

Name

Zhang Junzhi

Email

zjzmisaka@outlook.com

GitHub Profile URL

https://github.com/ZjzMisaka

Committers

ZjzMisaka
dlnn

Discord Ids

zjzmisaka_30898

Governance Model

New code changes are proposed through pull requests on GitHub. Project maintainers review these pull requests, discuss any necessary changes with contributors, and approve them if they meet the project's standards.
If a contributor demonstrates sufficient understanding of the project and makes substantial improvements to its performance, functionality, or user experience, they will be invited to become a committer after confirmation with the contributor.

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

As an infrastructure library, we often face challenges in building a vibrant community and attracting contributors, since such projects tend to be less visible to end users. By joining the Foundation, we aim to improve our project’s governance, attract more contributors, and make it easier for both individuals and organizations to trust, adopt, and contribute to the project. We hope to expand our project’s impact and contribute more effectively to the .NET ecosystem.

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.

Describe why you are applying for Project Membership.

As an infrastructure library, we often face challenges in building a vibrant community and attracting contributors, since such projects tend to be less visible to end users.
By joining the Foundation, we aim to improve our project’s governance, attract more contributors, and make it easier for both individuals and organizations to trust, adopt, and contribute to the project.
We hope to expand our project’s impact and contribute more effectively to the .NET ecosystem.

Infrastructure Requirements Summary

No response

Additional Notes

Whether it is necessary to replace the CODECOV_TOKEN and NUGET_API_KEY currently in use for PTP?

Metadata

Metadata

Labels

project applicationproject supportUse this label to request support for an existing .NET Foundation project

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions