I'm fairly sure that puppetlabs uses their activemq module internally to manage the activemq component of mcollective. I'm interested in contributing an ActiveMQ module myself, one that is for more general use. I'm not sure if I should contribute and expand the functionality of PuppetLabs ActiveMQ module, contribute to another ActiveMQ module, or create a new one.
When read the guide on forge contributions, the first step is to open an issue for the bug or feature, and it appears as though issues are disabled for the PuppetLabs/ActiveMQ module, however I do see pull requests. The features I'd like to add over multiple phases are: Support for choosing a persistence engine (KahaDB, LevelDB, MySQL, whatever else is supported). Support for creating a network of brokers. Support for HA scenarios, such as Zookeeper or shared storage configurations. In short, there are lot of deployment configurations for ActiveMQ, and I'd like to help the main PuppetLabs module support as many as possible, I'm just not quite sure where to begin as far as collaboration with PuppetLabs is concerned. If PuppetLabs would like to keep their ActiveMQ module tuned for the puppet application stack, which module should I then proceed to contribute this functionality toward? John A. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/1222294e-531f-4521-9c4f-9b07df086c12%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
