Issue: New .NET Foundation Project Application - Cloud Streams

[cdavernas]

Project Name

Cloud Streams

License

Apache-2.0

Contributor

Neuroglia SRL, Charles d'Avernas, Jean-Baptiste Bianchi

Existing OSS Project?

Yes

Source Code URL

https://github.com/neuroglia-io/cloud-streams

Project Homepage URL

No response

Project Transfer Signatories

• Charles d'Avernas [email protected]
• Jean-Baptiste Bianchi [email protected]

Description

Cloud Streams is a cloud-native solution for capturing and processing cloud events in real-time—powering highly scalable, efficient, and fault-tolerant event-driven architectures. Using simple, declarative rules, it lets you stream, filter, partition, mutate, and route data exactly how you need, guaranteeing reliable delivery and the ability to replay past events. Producers simply send CloudEvents via HTTP, while consumers receive them just as easily, with all the heavy lifting handled by Cloud Streams. The result? Flexible, cost-effective data processing you can trust for mission-critical workloads—built for both agility and durability.

Name

Charles d'Avernas

Email

[email protected]

GitHub Profile URL

https://github.com/cdavernas

Committers

Charles d'Avernas
Jean-Baptiste Bianchi

Discord Ids

No response

Governance Model

• Proposing Changes

  1. Contributors create a GitHub issue to discuss the needed fix or feature.
  2. They submit changes via a pull request (PR) on a dedicated branch, linking it to the relevant issue(s).

• Reviewing Changes

  1. Automated CI checks (tests, linting) run on every PR.
  2. Project committers and community members review the code, requesting changes if needed.
  3. Once feedback is addressed and approvals are granted, the PR can be merged.

• Decision Making

  • Most changes follow a "lazy consensus" approach, merging if there are no objections.
  • Major or breaking changes require additional approvals from committers or a project lead.
  • Disagreements are resolved through discussion or escalated to a higher-level committee if necessary.

• New Committers

  1. Potential committers are nominated based on a history of quality contributions and community engagement.
  2. Existing committers vote; a majority or supermajority is required.
  3. Once approved, the new committer receives the necessary permissions and is announced to the community.

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

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.

Describe why you are applying for Project Membership.

We seek to benefit from the .NET Foundation’s visibility and credibility in order to grow a strong, sustainable community around Cloud Streams. By joining the .NET Foundation, we aim to reach a broader audience, attract more contributors, and ensure long-term support and transparency for our project.

Infrastructure Requirements Summary

• Build Servers: We currently utilize GitHub Actions for CI/CD, so no additional dedicated build servers are needed from the Foundation at this time.
• Web Hosting: We require hosting for the project’s website to provide documentation, announcements, and user support.
• SSL Certificates / Code Signing: We need SSL certificates for secure hosting and would also like to leverage Authenticode Code Signing for releases to ensure trust and authenticity of distributed binaries.

Additional Notes

No response

[glennawatson]

The project committee met yesterday and has asked the board to review the admission. The board is meeting later this month.