activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hiram Chirino <hi...@hiramchirino.com>
Subject Re: [POLL] - Remove the old ActiveMQ Console
Date Wed, 22 Jan 2014 22:30:51 GMT
I don't really see much of a difference.  As long as the PMC is happy
with the end product that we produce what's the problem?  You don't
like the way some UI element works? Then raise an ActiveMQ jira issue.
 We can follow the normal deficiency resolution processes to fix it.
If you think we can't for some reason, I'd like to understand why you
think that.

Perhaps there some special ASF policy your talking about that I'm not
aware of?  If so, could you you provide me a pointer to where it's
documented?


On Wed, Jan 22, 2014 at 4:47 PM, James Carman
<james@carmanconsulting.com> wrote:
> This whole "then we shouldn't use any 3rd party libraries" argument is
> getting old, Hiram.  You know there's a difference between using a
> library behind the scenes and the entire web console itself that the
> users interact with directly. Come on, man.  Give it up.
>
>
> On Wed, Jan 22, 2014 at 1:48 PM, Hiram Chirino <hiram@hiramchirino.com> wrote:
>> On Wed, Jan 22, 2014 at 1:04 PM, Daniel Kulp <dkulp@apache.org> wrote:
>>> That’s completely BS.     If I download “activemq-###.tar.gz” from ActiveMQ’s
website and I run the startup scripts and such that are documented in that bundle and I find
a problem that directly pertains to ActiveMQ, I COMPLETELY expect to be able to go to ActiveMQ’s
JIRA and log an issue.  I also completely expect to be able to do a “git clone” of ActiveMQ’s
repo, diagnose the problem, and submit a patch back to ActiveMQ.
>>>
>>
>> If this is true then we should not be using ANY 3rd party libs at all.
>>  Most users cannot tell where the line is between 3rd party libs and
>> ActiveMQ's source.  The ActiveMQ project is ultimately responsible for
>> all functionality shipped (if its 3rd party or not).  If it's a 3rd
>> party defect then the ActiveMQ project needs to either work around the
>> defect, patch the defect in the 3rd party library or work with the 3rd
>> party to fix the defect.  All 3 approaches are possible with hawtio
>> too.

-- 
Hiram Chirino
Engineering | Red Hat, Inc.
hchirino@redhat.com | fusesource.com | redhat.com
skype: hiramchirino | twitter: @hiramchirino

Mime
View raw message