On 07/03/2013 12:38 AM, Karsten 'quaid' Wade wrote:
On 07/02/2013 02:33 AM, Dave Neary wrote:
> Hi Liran,
> It appears I am alone in having concerns about this so I would go ahead
> and request the project license as you proposed.
FWIW, you can *always* figure I have concern about using non-FLOSS tools
in an open source project. I like learning from history and past mistakes.
Bottom line is, if people like us (and our engineering and product
managers) don't step up to the line to deliver open solutions for our
development needs, then we continue to fall behind
closed-but-ready-today solutions in the drive toward deliverable dates.
Every decision to purchase a closed solution instead of writing or
fixing an open solution hurts the entire ecosystem. It's behavior we can
expect at the corporate layer, but it shouldn't push its way up to the
community project layer.
we aren't purchasing, we are using something provided for free for open
similarly, i'm for using the coverity solution for scanning our code(we
are also using the open findbugs, but coverity has things not covered by
findbugs (it actually uses findbugs now).
> On 06/25/2013 12:42 PM, Liran Zelkha wrote:
>> Hi all
>> I have searched for open alternatives, but they do not provide full view of the
application, as is needed in the profiling session of the engine we are conducting.
>> The only alternative I can see is buy JProfiler licenses (or any other commercial
profiler) and let internal RedHat team members use it when profiling.
>> Please advise.
>> ----- Original Message -----
>> From: "Jon Benedict" <Jon.Benedict(a)netapp.com>
>> To: "Itamar Heim" <iheim(a)redhat.com>, "Liran Zelkha"
>> Cc: board(a)ovirt.org
>> Sent: Tuesday, May 14, 2013 6:12:40 PM
>> Subject: Re: JProfiler
>> I have no issue with this.
Board mailing list