-
Notifications
You must be signed in to change notification settings - Fork 236
Preamble #378
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Preamble #378
Conversation
CLAassistant
commented
Jan 3, 2024
CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
Stephen P. Potter seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
You have signed the CLA already but the status is still pending? Let us recheck it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry but this must be a joke. Why doesn't Perforce want to provide puppet modules for their own software?
And what about the puppetdb specific code in pe-modules rpm/deb package? That's probably still maintained? Why can't Puppet Enterprise eat their own dogfood and use the puppetlabs/puppetdb module instead?
You put us now in a situation where open source users are treated like second class citizens and I fail to understand why.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Another thought: There even is a whole team dedicated to manage puppet modules. They manage a bunch of modules for third party software. Why don't they maintain the PuppetDB module (or one for Puppetserver and Puppet Agent)? I asked that a few times during office hours but never got a proper answer.
@davidsandilands
davidsandilands
Jan 4, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@GSPatton I have suggested we talk about this at the next VOX sync and it might be good for your product area to be aware and to help discuss
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
added this PR as a talking point to the agenda (https://github.com/voxpupuli/community-triage/wiki)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Puppetlabs's own puppetserver team having to work around the lack of maintenance of this module makes this preamble even more puzzling:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was discussed at length: https://github.com/voxpupuli/community-triage/wiki#february-13-2024
The short summary is:
- Historically there exists an internal version to support PuppetDB in PE
- Puppet uses this module for CI
- This preamble is intended to clarify the existing situation
- By the next community meeting (2024年02月13日) we should have more clarity on the path forward
Added preamble to README at request of Puppet Community leadership.