Hi Benedikt, Thanks for sharing that information. I wasn't aware of it and it sounds like a very nice news. I'll check the discussion and will try to be involved. Thank you, Takashi On 3/5/26 3:24 AM, Benedikt Trefzer wrote:
Hi puppeteers,
First thanks to the work done by Takashi and others on the puppet modules, I really appreciate !
I just want to make you aware that the problems around the perforce "maintained" modules is also discussed in the openvox community. OpenVox as Takashi already said is the actively puppet fork maintained by Voxpupuli. Voxpupuli already maintaince a big number of opensource puppet modules, which also depend on the perforce "maintained" modules. So there is a high demand of the whole community to fork especially the modules Takashi mentioned (mysql, apache etc). I expect these to be taken by Voxpupuli. Currently there is a discussion about the License to choose for such forks [1].
So I expect the second 'problem' about the depend modules will be solvable by the communities.
Benedikt
[1] https://github.com/voxpupuli/community-triage/issues/92
On 04.03.26 18:13, Takashi Kajinami wrote:
- The upstream puppet has been "dead" after Perforce (who acquired puppetlabs) changed their strategies. OpenVox was created as a fork of puppet, but there are number of core modules such as puppetlabs-apache or puppetlabs-mysql which are not yet forked. I've asked possibility to fork and host these in OpenVox but it was not acceptable due to limited resources the OpenVox community and no real commitment (more specifically speaking, sponsorship) I can provide. There are some works done earlier to replace puppet by OpenVox but it is essentially blocked by the fixes needed in these "abandoned" puppetlabs modules. In addtion, we need to bump versions of our testing platform soon, and I expect these unmaintained modules cause new problems. As afar as I'm aware of, migration to CentOS 10 is completely blocked by "unmaintained puppetlabs-mysql[2], and I expect more for migration to Ubuntu 26.04 or Debian 14 we need in upcoming cycles. [2] https://github.com/puppetlabs/puppetlabs-mysql/issues/1676
So... The situation is getting out of my control and I'd admit that I may soon terminate the project in case the situation is not improved, given my work in the OpenStack community has been all voluntary-based these days.
I intend to continue my PTL role of this project for next cycle, so that I can help anyone who would be interested in sustaining the project, but I hope that we get some conclusion and agreement about the future project direction and maintenance during this cycle.
Please reply to this in thread or reach me directly (in email or irc) if you are interested in further discussions.
Thank you, Takashi