On 05/15/2013 10:50 AM, Dave Neary wrote:
Hi,
On 05/12/2013 04:00 PM, Itamar Heim wrote:
> On 04/18/2013 09:32 PM, Liran Zelkha wrote:
>> These capabilities are covered by commercial profilers. One of them is
>> called JProfiler
>> (
http://www.ej-technologies.com/products/jprofiler/overview.html).
>> The company that manufactures JProfiler offers a solution for open
>> source projects, allowing them to use JProfiler licenses for free, in
>> exchange for posting the JProfiler logo on the open source project site.
>> (See here <
http://roq-messaging.org/> for an example)
>>
>> My question is whether you'll allow such posting on the Ovirt web
>> site, so that the Engine team can use JProfiler to improve Ovirt's
>> Engine performance.
>
> no replies, so i assume no one objects to this?
I have no opposition to oVirt developers using JProfiler themselves, but
I would not like to see it become a key piece of the project's
infrastructure, because it is not open source.
I also do not like the idea of promoting JProfiler, a proprietary tool,
on the oVirt website.
However, if the board members decide that this is appropriate, then we
can do this.
+1
Perhaps the oVirt team at Red Hat can purchase the can opener^H profiler
tool, use it, and report the results on the wiki (where the results are
open and free under the Apache license.)
As an open community infrastructure geek, I'm extremely wary of any
non-open tools in the chain. It's like conducting science that others
can't verify themselves. It also makes it harder to run for a volunteer
infrastructure team, where skills are usually learned on freely
available open source instances.
- Karsten
--
Karsten 'quaid' Wade
http://TheOpenSourceWay.org .^\
http://community.redhat.com
@quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41