New .NET Foundation Project Application: HttpReports APM

1.   General Information

Project Name:

HttpReports

License:

MIT

Contributor (Company, Organization or individual name(s)):

@SpringLee
@StratosBlue
@mzorec

Existing OSS Project? (Yes/No):

Yes

Source Code URL:

https://github.com/dotnetcore/HttpReports

Project Homepage URL (if different):

https://www.yuque.com/httpreports/docs

Project Transfer Signatories:

Full legal name and springleers@gmail.com required of the individual(s) with the authority to transfer or contribute the project to the .NET Foundation. Note that if you'd prefer not to include this in the public application, it can be submitted via e-mail to contact@dotnetfoundation.org (referencing this issue number)

2.   Description

HttpReports is an APM (application performance monitor) system for .Net Core. Based on MIT open source protocol, The main functions include statistics, analysis, visualization, monitoring, tracking, etc，It is very suitable for use in microservices

3.   Project Governance

Project Lead:

Name: Spring Lee
Email: springleers@gmail.com
GitHub Profile URL: https://github.com/SpringLeee

Committers:

@SpringLee
@StratosBlue
@mzorec

Governance Model:

Community members submit pull requests which are reviewed by the core committers

CLA

No

CLA Notification Alias

springleers@gmail.com

Project Transfer Type

Contribution

4.   Repository Layout

We already follow the guidelines here.

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

No PR Plan

7.   Infrastructure Requirements

Hosting space for our website would be useful.

8.   Additional Notes

HttpReports is Member of NCC organization.