Jun 12, 2020
by StackStorm Team
In recent news Extreme Networks open-sourced EWC and contributed all previously “enterprise only” features to the StackStorm project operating under the Linux Foundation.
This is very exciting news for the project’s future and its users. It also means that StackStorm’s destiny now rides on the shoulders of the community along with organizations that rely on it in their production infrastructure and benefit from the project’s unique event-driven-automation and automated remediation capabilities.
StackStorm includes a lot of components that makes it an amazing and complete platform: st2 core platform, st2 plugins and modules, documentation, StackStorm Exchange with the 150+ integration packs, Web UI, the Orquesta workflow engine, deb/rpm packages, CI/CD, ChatOps, internal infrastructure and a number of deployment methods like Puppet, Chef, Ansible, Docker, Kubernetes, Vagrant as well as our Forum and Slack Communities. This is maintained by a small team of enthusiasts during their free time.
The StackStorm team takes the project quality seriously. A quick example, every time someone opens a new PR against StackStorm/st2 Deb/RPM packages are built, uploaded to Apt/Yum repositories and verified end to end in different testing scenarios by creating a temporary VM instances in the cloud for every OS platform we support (currently 5 OS flavors). This is powered by st2tests, st2ci, and st2cd workflows running on a StackStorm cluster in AWS. We also eat our dog food and find ways to improve the StackStorm via nightly builds, package promotion workflows, staging/unstable/production environments, and release process that encompasses testing all the components thoroughly before our users download new versions.
But there are many other pieces used behind the scenes of the StackStorm project besides just the AWS cloud and computing resources. StackStorm relies on a number of external paid services to function well: we use PackageCloud for hosting our Deb/RPM package repositories, Discourse to allow you get help through forum.stackstorm.com, CircleCI for automated testing, G Suite for administrative emails, Zoom for the monthly TSC meetings, stackstorm.com domain SSL certificates, etc. The full list is highlighted in the StackStorm Expenses document.
Now that StackStorm is fully independent and backed by its community of users we are happy to announce that StackStorm has established a way to accept monetary donations through the Linux Foundation’s Community Bridge.
The Community Bridge platform provides transparency around funds usage and reporting, establishes trust and enables the community to support the StackStorm project. We’re very excited to see recent movement around fixing the economy behind Open Source with new platforms and also adding a Github “Sponsor” button to all StackStorm project repositories.
Moving forward we will need contributions in order to help covering StackStorm maintenance, infrastructure expenses, development, bug fixes, security researches, timely security patches, spreading the word via meetups, developer conferences, marketing and any other initiatives that would make StackStorm successful. Please show your appreciation to the StackStorm team’s dedication, hard work, and value that StackStorm as a tool provides and time it saves in your day to day work by donating to the project via Community Bridge Sponsorship platform.
If you have any questions, please read FAQ or reach to us in StackStorm Community Slack.