camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Babak Vahdat <>
Subject Re: git commit: CAMEL-7023: Added hawtio goal to camel maven plugin.
Date Sun, 01 Dec 2013 16:58:16 GMT

Let me sincerly tell you my personal opinion. To me the vetos both Dan &
Hadrian have started in this thread has nothing really technical in it and
is just POLITICAL justifications as Talend representatives.

Why not let the community benefit from a ASL2 licensed software?

@Dan in open source community there is nothing ANYBODY should get the
control over because the open source community doesn't need a BOSS as you
like to be:

If there's any improvement you see just make a pull request like ALL OTHER
people in the community, SPECIALLY for:

 "links popping up and icons and such that promote something else"

You did mention about in this thread. BTW where did you exactly spot those
icons & pop-ups?

Babak wrote
> On Dec 1, 2013, at 3:46 AM, Rob Davies &lt;

> rajdavies@

> &gt; wrote:

> dkulp@

>  wrote
>>> Having no way for this PMC to control the display of the Camel route
>>> *IS*
>>> a technical justification.   If we as a PMC wanted to remove columns,
>>> add
>>> new columns for new features, change the order of stuff, etc….   *WE*
>>> have
>>> no way to do so.   
>>> Having no way to change the branding of what is displayed *IS* a
>>> technical
>>> justification.   We cannot have links popping up and icons and such that
>>> promote something else.
>>> Having no way to remove all the “cruft” that is unrelated to Camel *IS* 
>>> a
>>> technical justification.   Claus’s screen shot on the wiki has an
>>> AcitveMQ
>>> tab, Wiki tab, etc…  which would need to be removed if the goal is to
>>> have
>>> a Camel route display.
>>> That’s all technical justification.    This needs to be removed until
>>> they
>>> can all be addressed.  
>>> Oh… and the maven goal cannot be camel:hawtio.   It would need to be
>>> camel:run-webconsole or similar to remove the branding part from that as
>>> well.
>> So any 3rd party tool that aids developers, can't be run as a maven
>> target
>> unless its completely branded and controlled by the Camel PMC is the
>> stance
>> you are taking. 
> If the maven plugin is part of Camel and it’s stated purpose it to present
> *Camel*  to the user, then yes.   That BETTER be under the PMC’s complete
> control and influence. 
> -- 
> Daniel Kulp

> dkulp@

>  -
> Talend Community Coder -

View this message in context:
Sent from the Camel Development mailing list archive at

View raw message