By: Radu Matei & Michelle Dhanani
Today, we are excited to announce that Spin has officially been accepted as a Cloud Native Computing Foundation (CNCF) Sandbox project and SpinKube will now be housed within the Spin project.
The Journey
We at Fermyon have always believed Spin belongs in a neutral organization. From the beginning of the company and the Spin project, we made a clear pledge to always keep Spin open source. We started this with the second commit to the project, which introduces the Apache 2 license. We added a proposal process for providing a clear way to evolve the project and propose and discuss features in the open. We re-affirmed the goal to have Spin as a multi-stakeholder project here, added a formal governance document to provide transparency in who makes decisions for the project and how decisions are made, and we’re now at the ultimate step of contributing the Spin project to the CNCF!
Spin
Spin was introduced in early 2022. It started out as a way to make WebAssembly more accessible to developers and rapidly gained traction among developers and organizations seeking a more efficient, secure and portable alternative to traditional containerized workloads. Today, the project boasts over 5.6k stars and 230k ‘clownloads’ (which is our combined term for Clones and Downloads). Organizations like Docker, Microsoft, F5/NGINX, SUSE have already integrated Spin into their workflows, projects and product and service offerings. And it has become increasingly clear that numerous business interests are aligned with the trajectory, longevity, and health of the project.
SpinKube
Last year, we launched SpinKube in conjunction with contributions from Microsoft, Liquid Reply and SUSE to make it easier to run WebAssembly applications in Kubernetes. Since then, we’ve seen much excitement for, and a number of organizations start working and experimenting with the project! Going forward, SpinKube will be a subproject within the Spin umbrella. This will require updating the Spin governance to include a top level steering committee that includes representation from subprojects, updates to documentation (when has that ever been a bad thing?) and updating some infrastructure. We’re very excited to be seeing the adoption for SpinKube grow and we welcome the opportunity to broaden the Spin ecosystem.
The Path Forward
We’re are thrilled to contribute Spin to the CNCF, and look forward to collaborating with existing and new contributors and co-maintainers of the project in this context. Among the many benefits, being in the CNCF gives collaborators and contributors a neutral IP ground to collaborate. The CNCF community also brings greater infrastructure for fostering collaboration and pathways to understand and interact with end user requirements and feedback. With its entry into the CNCF, Spin is poised to deliver even greater value to the community by fostering broader adoption and amplifying its benefits for developers and organizations alike.
In the coming weeks, we’ll be completing CNCF onboarding and be engaging in a number of changes around communication channels, governance, documentation and more. We are humbled to see all the projects being built with Spin and to have this community because the best part of this journey has been the people. Thank you to everyone who has hopped on community meetings, done demos, participated in the Discord channel, or contributed to or tried out Spin and SpinKube. With this next chapter in the project’s journey, it’s an excellent time to get involved!
Top comments (0)