On Fri, Jan 17, 2014 at 2:33 PM, Robert Davies <rajdav...@gmail.com> wrote: > I want to take a straw poll to see where everyone stands, because opinion has > varied, mine included. Straw polls can be a useful tool to move towards > consensus. This isn’t a formal vote, but to reduce the noise, can we keep it > to binding votes only ? > > > 1. Have one distribution with no default console, but make it easy to deploy > a console on demand (the original console - or 3rd party ones). > 2. Have two separate distributions, one with no console - and have a second > distribution with the original console > 3. One distribution, with hawtio as the console - ActiveMQ branded. > 4. One distribution, but uses the original ActiveMQ console only. > > Here’s my vote: > > [1]. +1 > [2] 0 > [3] 0 > [4] -1 > > thanks, > > Rob >
[1]: +1 [2]: -1 - there should be an even playing field for consoles. And the original console should be moved to a sub project, where it has its own release schedule. Installing any console into AMQ should be similar and the same for all consoles, such as copying a .war into a special directory. And optionally copy a configuration file into the same dir, to override the default configuration of that installed console. So ActiveMQ should have only one distribution, to have even playing field. But installing a console is end user choice, and they can choose what console to install / use if they want. [3]: -1: see #2 [4]: -1 -- Claus Ibsen ----------------- Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen Make your Camel applications look hawt, try: http://hawt.io
