Re: [Pulp-list] What to do with Puppet Deployment
After a small amount of discussion we have decided to deprecate Pulp's Puppet deployment repository. To be clear, this is not the Puppet package plugin, but the Puppet code that can be used to deploy Pulp. This pull request adds a note about this to the README.md in the repository that contains a link to the Katello Puppet module that serves the same purpose: https://github.com/pulp/puppet_deployment/pull/27 -- Randy Barlow irc: bowlofeggs phone: +1-919-890-8150 signature.asc Description: PGP signature ___ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list
Re: [Pulp-list] What to do with Puppet Deployment
On Tue, Dec 01, 2015 at 11:55:25AM -0500, Sean Myers wrote: > On 11/30/2015 04:55 PM, Randy Barlow wrote: > > 1) We could make the repository's README state that it is deprecated, > > and provide a link to the Katello project. > > I prefer this, more details below. > > … > > I think the best possible outcome is to leave all the code available for > those that might still be using it, make sure the project is clearly > deprecated, and provide some examples for migrating from the deprecated > module to the katello module if possible. > > Gaps in functionality between the pulp module and the katello module > should be identified; if found, those gaps should be tracked as > enhancement requests on the katello module. This is also my preference. Does anybody else have any thoughts? Should we proceed with this plan? If possible, it may be good to disable pull requests on the repository as well. -- Randy Barlow irc: bowlofeggs phone: +1-919-890-8150 signature.asc Description: PGP signature ___ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list
Re: [Pulp-list] What to do with Puppet Deployment
On 11/30/2015 04:55 PM, Randy Barlow wrote: > For a variety of reasons, not least of which is that Katello has a > project that has the same purpose[0], the Pulp team is unable to maintain the > Puppet > Deployment repository[1]. I'd like to have a discussion here about the > future of the repository. Here are a few possibilities, feel free to > suggest you own ideas in response: I assume it's probably not worth going into, but I'm vaguely curious about the other reasons. > 0) We could remove the repository. I think this is a little extreme. Even if it's deprecated, I think there's value in leaving the code around for anyone still using it. "If I serve no other purpose, may I at least serve as a bad example." :) > 1) We could make the repository's README state that it is deprecated, > and provide a link to the Katello project. I prefer this, more details below. > 1.5) We could remove all code from the repository, leaving only the > README about how it is deprecated and to use the Katello repository. This is also a little extreme. > 2) Someone from the community who is proficient at Puppet could take > ownership of maintaining the repository, including pull request review > and fixing issues. Would that person do more good helping out the katello project, though? > Any other ideas or thoughts? I think the best possible outcome is to leave all the code available for those that might still be using it, make sure the project is clearly deprecated, and provide some examples for migrating from the deprecated module to the katello module if possible. Gaps in functionality between the pulp module and the katello module should be identified; if found, those gaps should be tracked as enhancement requests on the katello module. signature.asc Description: OpenPGP digital signature ___ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list
[Pulp-list] What to do with Puppet Deployment
For a variety of reasons, not least of which is that Katello has a project that has the same purpose[0], the Pulp team is unable to maintain the Puppet Deployment repository[1]. I'd like to have a discussion here about the future of the repository. Here are a few possibilities, feel free to suggest you own ideas in response: 0) We could remove the repository. 1) We could make the repository's README state that it is deprecated, and provide a link to the Katello project. 1.5) We could remove all code from the repository, leaving only the README about how it is deprecated and to use the Katello repository. 2) Someone from the community who is proficient at Puppet could take ownership of maintaining the repository, including pull request review and fixing issues. Any other ideas or thoughts? [0] https://github.com/Katello/puppet-pulp [1] https://github.com/pulp/puppet_deployment -- Randy Barlow irc: bowlofeggs phone: +1-919-890-8150 signature.asc Description: PGP signature ___ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list
