governance alive 2025

Puppet OpenVox

Vox Pupuli community fork after Perforce closed packaging infrastructure.

What it is

Puppet is a configuration management and automation tool used to define and enforce the desired state of IT infrastructure. It uses a declarative language to describe system configurations, with an agent-server architecture that manages thousands of nodes. Puppet was pioneering in the infrastructure-as-code movement alongside Chef and Ansible.

The story

Puppet, the venerable configuration management tool that helped define the DevOps era, had been slowly declining under corporate ownership. After Perforce acquired Puppet in 2022, the writing was on the wall — but the community held on, hoping for the best. That hope evaporated in late 2024 when Perforce made several devastating moves: they discontinued public packaging infrastructure, moved all further development to internal forks, and began requiring commercial licenses for deployments beyond 25 nodes.

The Vox Pupuli community — a collective of Puppet module maintainers who had been keeping the ecosystem alive with nearly 200 community modules — decided enough was enough. In late 2024, Overlook InfraTech began mirroring Puppet and providing community packages. By January 21, 2025, the first official release of OpenVox landed, functionally equivalent to Puppet 8.11 but free of Perforce's restrictions.

The situation deteriorated further in May 2025 when Perforce introduced a new EULA for core developers that the Vox Pupuli community found unacceptable. The restrictions prevented effective testing and distribution of modules and exposed contributors to potential legal challenges. Perforce had explicitly refused to allow the use of the Puppet name, so the community settled on "OpenVox" after briefly considering "OpenPuppetProject."

A Puppet Standards Steering Committee was established to guide the project's direction, and Perforce was even invited to participate — a diplomatic olive branch that speaks to the community's professionalism. By mid-2025, OpenVox had shipped 8 releases across both v7 and v8 branches, and organizations like NC State's Linux Community began documenting transition plans.

OpenVox represents the classic scenario of a corporate owner strangling the golden goose. Perforce took a thriving open-source community and systematically removed every reason to stay, practically gift-wrapping the justification for a fork.

Timeline

Perforce acquires Puppet

Perforce discontinues public Puppet packaging infrastructure

Overlook InfraTech begins mirroring Puppet as OpenVox

First public release of OpenVox, functionally equivalent to Puppet 8.11

Perforce introduces EULA that Vox Pupuli deems unacceptable

Vox Pupuli publishes 'An Unsupportable Path' blog post, confirming full independence

OpenVox reaches 8 releases across v7 and v8 branches

Key people

Ben Ford
Puppet software engineer who documented Perforce's shutdown of open-source development
Vox Pupuli collective
Community maintainers of ~200 Puppet modules who led the fork effort
Overlook InfraTech
Company sponsoring and stewarding the OpenVox project

Impact

OpenVox saved a critical piece of infrastructure automation tooling from corporate lock-in. While Puppet's market share had been declining in favor of Ansible and Terraform, thousands of organizations still depend on it for configuration management. The fork ensures continuity for those users without requiring expensive Perforce licenses.

The project also demonstrated the power of pre-existing community infrastructure. Vox Pupuli's years of maintaining community modules gave them the credibility and technical depth to execute the fork successfully, unlike many forks that start from scratch.

Lesson: When a corporation acquires an open-source project and starts closing doors, the community that maintained the ecosystem becomes the natural successor.