Praxis is applying to the CNCF Sandbox #837
Replies: 3 comments 52 replies
|
As part of the CNCF Sandbox submission, we need to relicense the project from MIT to Apache 2.0 across every repository in the praxis-proxy organization. The CNCF Charter (Section 11) requires that all project code be licensed under Apache 2.0. While a Governing Board exception is technically possible for other OSI-approved licenses, these are rarely granted for core project licenses, and the CNCF's stated preference is to work with projects to relicense rather than grant exceptions. Since all contributors hold copyright over their contributions, we need explicit consent from each contributor to relicense. If you're OK with relicensing your contributions from MIT to Apache 2.0 across all repositories in the organization, please reply directly to this comment with a confirming message. We'd like to have responses within two weeks. @abdallahsamabd @alexsnaps @araujof @aslakknutsen @christinaexyou @crstrn13 @danielezonca @dimakis @esnible @franciscojavierarceo @henschwartz @leseb @liavweiss @lsmola @mariusdanciu @mkoushni @nathan-weinberg @nerdalert @nirrozenbaum @Nitjsefnie @noalimoy @onatozmenn @rikatz @roytman @szedan-rh @terylt @tsisodia10 @usize @yehuditkerido |
|
📣 The project has been submitted for sandbox here: cncf/sandbox#506 Please thumbs up and subscribe if you want to track it! 🖖 |
Uh oh!
There was an error while loading. Please reload this page.
We're preparing to submit Praxis to the Cloud Native Computing Foundation as a Sandbox project.
Praxis is a high-performance, security-first proxy server and composable filter framework built in Rust on Cloudflare's Pingora. Its core design principle is that everything is a filter: routing, load balancing, rate limiting, security, and observability are all composable pipeline stages built on the same trait interface.
The CNCF Sandbox is the entry point for early-stage projects that demonstrate alignment with the cloud-native ecosystem. Praxis fits through its Kubernetes Gateway API operator, Envoy ExtProc bridge, Prometheus metrics, and container-native design. Joining the CNCF would give the project a vendor-neutral home and bring it closer to the ecosystem it already integrates with.
We'll also be formalizing governance, contribution guidelines, and maintainer structure. These changes strengthen the project for long-term community ownership regardless of the submission outcome.
We'll share more details as the application progresses.
All reactions