Repository navigation
Plans on r10k #73
Description
What are the plans on r10k?
Will there be a fork as well? Is a fork required? Is a fork advised? Does the license allows it? Are there trademark issues to consider?
While https://github.com/puppetlabs/r10k seems maintained, what if they stop?
Is the control repo ref spec (which I assume r10k to be a reference implementation for) jointly decided upon in a (or the) Puppet Steering Committee (if it exists at all)? Does the OpenVoxProject community still can influence that? Effectively, can the OpenVoxProject community still contribute to the r10k code (also getting merged)?
Activity
nmburgan commentedon Jul 24, 2025
It’s only maintained insofar as they have to for Puppet Enterprise. I would expect they will either have a private fork before long, or will just abandon it. As for the future of r10k in the OpenVox space, it’s been discussed but I don’t think we’ve reached a conclusion yet.
nsballmann commentedon Jul 24, 2025
@nmburgan thank you for the information. I was unaware of that discussion and I haven't found it by a brief search through the issues. Have I just missed it or was it done outside of this planning project? Because I also don't see a fork of https://github.com/puppetlabs/r10k in the https://github.com/OpenVoxProject namespace.
c33s commentedon Jul 24, 2025
honorable mention: https://github.com/xorpaul/g10k
bastelfreak commentedon Jul 25, 2025
I would like to avoid a fork until it's required. A fork also means renaming and is some work. Right now I don't see a need for it and we have enough other topics to work on.
nsballmann commentedon Jul 28, 2025
Got it. Please feel free to move this issue into the backlog (maybe even close it) and pull it back up (or re-open) once we are forced to deal with this.