There have been a lot of concerns and questions about Puppet and the Community over the past couple of months since the changes were announced . It has taken Perforce and the Community time to work out how to meet the Communities need for autonomy, Perforces business needs and legal responsibilities for items like trademark, all while ensuring the rich Puppet ecosystem of content and tools remain compatible.
OpenVox have created what we would describe as a soft fork, where they create a new name space and project name OpenVox but the use of 'puppet'; in forked source code follows Apache 2.0 licensing with the intent to retain compatibility, and attribute the Puppet trademark appropriately to avoid brand confusion. Simply this ensures binaries, libraries, etc do not need renamed and ensures Perforces responsibility as a trademark holder is met.
To ensure this new partnership works well we will be taking a number of steps in order to guarantee long term interoperability to the benefit of all current and future Puppet users.
Perforce and the Community will partner together on a language steering group to ensure we continues to develop the language specification and ensure ecosystem compatibility.
Everyone will have access to EULA signed builds from Perforce for development purposes which will be released on a 6 week cycle.
We will be revitalizing our trusted Contributor and Champions programs while also ensuring our own staff are enabled to contribute
An event plan will be created to help our community and customers know where they can come and collaborate with us
We congratulate OpenVox on their first release and look forward to shortly releasing Puppet Core which will offer hardened binaries with bug and vulnerability support to give customers a more accessible level for enterprise support.
Look out for further announcements and hopefully we will see many of you at Cfgmgmt Camp in two weeks
Top comments (0)