Issue: New .NET Foundation Project Application For AdsPush

Project Name

AdsPush

License

BSD 3-Clause License

Contributor

adessoTurkey-dotNET

Existing OSS Project?

No

Source Code URL

https://github.com/adessoTurkey-dotNET/AdsPush

Project Homepage URL

https://github.com/adessoTurkey-dotNET/AdsPush

Project Transfer Signatories

Bilgehan Berberoglu bilgehan.berberoglu@adesso.com.tr
Anil Senel anil.senel@adesso.com.tr

Description

AdsPush is the server-side push notification library that fully supports APNS (Apple Push Notification Service) and FCM (Firebase Cloud Messaging) features and works with the most common platforms. It offers good abstraction, is easy to use, and provides complete support for advanced use cases

Name

Bilgehan Berberoglu

Email

bilgehan.berberoglu@adesso.com.tr

GitHub Profile URL

https://github.com/bberberoglu

Committers

adessoTurkey - .NET Community --> https://github.com/adessoTurkey-dotNET
employer : https://adesso.com.tr/

Governance Model

An issue is created describing the proposed code change.
After a review/design process, the maintainers of the project accept the proposed change.
Change is implemented and submitted as a pull request.
Pull request is reviewed and ultimately approved when it aligns with the agreed-upon design and coding/architecture standards of the project.
So far the project has only received sporadic pull requests.

New committers would ideally have made substantial contributions via pull requests which would demonstrate their understanding of the internals of the project, after which they could request contributor status via email.

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

dotnet@adesso.com.tr

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

We are hoping that membership in the .NET foundation will help improve the visibility of the project.

Infrastructure Requirements Summary

No response

Additional Notes

No response