Should Puppet be sponsoring Vox for supporting its proprietary work?

[binford2k]

Tim raises: https://forge.puppet.com/modules/puppetlabs/cem_linux/readme Puppet now sells modules that depend on our open source work. Any plans to reimburse Vox Pupuli or donate to us or support the module development?

[binford2k]

I have been working on a Vox sponsorship for some time. This is a good argument to raise, I'll add it to the budget proposal and see if I can move it along more quickly.

[bastelfreak]

I was told (and don't know if it's correct) that CD4PE uses by default the puppet dev-tools container which also relies on many Vox Pupuli. This might be another closed source product that heavily benefits from the community.

Our licenses explicitly allow this, but I would love to see a bit more support from Puppet for Vox Pupuli. The beaker project for example receives patches from time to time from Puppet employees.

[bastelfreak]

also PE vendors hiera-eyaml, which is also owned and maintained by Vox Pupuli.

[tuxmea]

There are plenty of add-ons, modules and pipelines which are referenced and used in other Puppet owned work.
Partly the work is also Open Source (like Puppet Operational Dashboard and Puppet Server Helm chart), partly closed source (like cem_linux).

At @betadots we not only sponsor Voxpupuli. Our staff is kindly asked to contribute to and work on Open Source work one day per week!
Puppet should at least do the same to acknowledge the work done by the community.

Besides this: Maybe Puppet should also move to a community driven product like RedHat.

• Foreman -> Satellite
• OKD -> OpenShift

For Puppet this could be:

• Catalog-Diff (and viewer) -> CD4PE
• HDM -> PE Console

[bastelfreak]

slightly related: For the PE Console I had different ideas some months ago and wrote them down here: Convert the PE console into a foreman plugin.

[bastelfreak]

@binford2k do you have an update here?