Brendan Murtagh
2013-Sep-25 14:50 UTC
[Puppet Users] Managing Duplicate PuppetLabs'' modules and Community Involvement (puppetlabs/passenger & puppetlabs/apache)
My reasoning for creating this post is two-fold. Currently there is two development efforts in progress for a common application. The community will benefit from having a combined effort in one place for development, bug reports, and future improvements. The second case is that both the puppetlabs/passenger and apache::mod::passenger lack Passenger Enterprise support. Hopefully having additional eyes and brain power involved, Enterprise support could be added in relatively quick. I spoke to ashp this morning on IRC about this situation and suggested I post here. I think this is a good initial step and all opinions are welcome. *Talking Points*: Managing two Passenger modules leads to double effort, confusion, and split-focus. Lack of Passenger Enterprise support *Proposal*: As a community, come to a decision on whether the Passenger module exists on its own or is only developed within the puppetlabs/apache module via the mod class. Scenario 1: puppetlabs/passenger exists as its own entity. The module''s focus would be to provide functionality that can be used in conjuntion with puppetlabs/apache or another module to install, configure, and manage Passenger and Passenger Enterprise. Apache::mod::passenger would be removed from puppetlabs/apache and be replaced by puppetlabs/passenger. Scenario 2: The repository for puppet labs/passenger would no longer be used for active development. Puppetlabs/passenger is archived and the current state of development, functionality, and features get merged into apache::mod::passenger. Thanks, Brendan -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Martin Alfke
2013-Sep-26 08:19 UTC
Re: [Puppet Users] Managing Duplicate PuppetLabs'' modules and Community Involvement (puppetlabs/passenger & puppetlabs/apache)
Hi, On Sep 25, 2013, at 4:50 PM, Brendan Murtagh <brendan.r.murtagh@gmail.com> wrote:> My reasoning for creating this post is two-fold. Currently there is two development efforts in progress for a common application. The community will benefit from having a combined effort in one place for development, bug reports, and future improvements. The second case is that both the puppetlabs/passenger and apache::mod::passenger lack Passenger Enterprise support. Hopefully having additional eyes and brain power involved, Enterprise support could be added in relatively quick. > > I spoke to ashp this morning on IRC about this situation and suggested I post here. I think this is a good initial step and all opinions are welcome. > > Talking Points: > > Managing two Passenger modules leads to double effort, confusion, and split-focus. > > Lack of Passenger Enterprise support > > Proposal: > > As a community, come to a decision on whether the Passenger module exists on its own or is only developed within the puppetlabs/apache module via the mod class. > > Scenario 1: > > puppetlabs/passenger exists as its own entity. The module''s focus would be to provide functionality that can be used in conjuntion with puppetlabs/apache or another module to install, configure, and manage Passenger and Passenger Enterprise. Apache::mod::passenger would be removed from puppetlabs/apache and be replaced by puppetlabs/passenger. > > Scenario 2: > > The repository for puppet labs/passenger would no longer be used for active development. Puppetlabs/passenger is archived and the current state of development, functionality, and features get merged into apache::mod::passenger.I would prefer Scenario 1. But that means that you have to add almost the same module to a nginx module. So I vote for Scenario 2: make passenger available without any special binding to apache only.> > Thanks, > > Brendan > > -- > You received this message because you are subscribed to the Google Groups "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. > To post to this group, send email to puppet-users@googlegroups.com. > Visit this group at http://groups.google.com/group/puppet-users. > For more options, visit https://groups.google.com/groups/opt_out.-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.