Openvox recently presented the first issue of the project Openvox, which is a fork for the configuration control system puppet. This allows for the automation of server group administration and centralized execution of tasks like user management, package setting, and configuration updating. The first issue of Openvox 8.11 is similar to a Puppet version and can be used as a transparent replacement. The project code is written in Ruby and is distributed under the Apache 2.0 license.
Openvox plans to develop as a soft fork, synchronized with the Puppet code base and maintaining full compatibility with Puppet issues. The team is currently collaborating with representatives of PerForce, the owner of the Puppet project, to create a joint leading committee to determine the development direction of Openvox and Puppet.
It is important to note that until the rebranding and testing system deployment process is completed, Openvox is not recommended for use in critical infrastructures. In terms of functionality, Openvox supports the same teams, modules, expansions, and settings as Puppet.
Some goals of Openvox include modernizing the code base and ecosystem, focusing on the community and user needs, democratizing platform support, providing the ability to make necessary changes without business requirements, and maintaining an active community.
The reason behind the fork’s creation is a change in Perforce’s policy. In 2022, PerForce acquired the Puppet project, and from fall 2024, they stopped public distribution of binary packets with Puppet. Instead, they focused on developing an internal branch and halted the open code base development. The Puppet license remained the same, but PerForce’s source code was no longer publicly available.
According to the creators of Openvox, this project should be considered the primary one. PerForce created its proprietary Fork Puppet based on code developed with input from the code community. Openvox developers will continue to advance the main code base, unable to use the Puppet name that belongs to PerForce. PerForce attempted to enforce one-sided cooperation on the community, expecting them to follow the Puppet Community version without offering proper opportunities and freedoms. This approach did not sit well with the community.