Issue: New .NET Foundation Project Application #552

Community Readiness Self-Check (optional, for your own reflection)

• My project has at least one merged pull request from someone other than me or an automated bot.
• My project has been public for at least 3 months.
• My project has organic GitHub stars, forks, or package downloads that I can't attribute to my own testing or CI activity.
• I already have a presence in the .NET Foundation Discord and/or other .NET community spaces.

Project Name

Birdflyfly

License

Systems

Contributor

Birdflyfly

Existing OSS Project?

Yes

Source Code URL

Birdflyfly.com

Project Homepage URL

No response

Project Transfer Signatories

Indeed important projects

Description

Indeed important projects

What are you hoping from the foundation

Indeed important projects

Name

Fritz Abraham

Email

callloulou131@gmaul.com

GitHub Profile URL

No response

Committers

Indeed important projects

Discord Ids

Indeed important projects

Governance Model

Indeed important projects

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?

Indeed important projects

CLA Notification Alias

No response

Select the Project Transfer Agreement model

Assignment

Repository Layout

Indeed important projects

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.

Indeed important projects

Infrastructure Requirements Summary

Indeed important projects

Additional Notes

Indeed important projects