So if the reason for trashing the console out of the Camel code base is the proven lack of development focus on it, I wonder if it'd make sense to contact the person behind the camelwatch project to ask if he'd be willing to contribute it to ASF.
Fair enough it's not the slickest UI, but maybe he'll be happy to continue evolving it here? What truly harms us is having an outdated console not lining up with the real richness of our monitoring and management API. Other than that, offering a basic & optional console from within this community is not a bad idea. AFAIK, camelwatch is more up-to-date, so it could give us a leap in this area. Regards, Raúl. On 25 Jan 2013 17:58, "Hadrian Zbarcea" <hzbar...@gmail.com> wrote: > In the context of a few web based consoles available for Camel, including > the Karaf console and the recently announced hawt.io, the question of if > Camel needs its own console popped up. > > My understanding is the some are in favor or Camel continuing to ship with > a web console. My personal opinion is that we should not (starting with > 3.0). > > I understand that a web console is very useful to users and a nice to > have. However, our console is not that great (to put it mildly), not really > maintained and we lack the necessary ui knowledge in the community to > maintain something of excellent quality. I think we should focus on the > server side technology that we do so well. > > Therefore, my personal position and proposal is that we should either move > the console in a subproject or remove it completely. > > Thoughts? > Hadrian > > > -- > Hadrian Zbarcea > Principal Software Architect > Talend, Inc > http://coders.talend.com/ > http://camelbot.blogspot.com/ >
