On 20 July 2017 at 06:53, Philippe Mouawad <philippe.moua...@gmail.com> wrote:
> Hello Emilian,

> In the past it was possible through Apache to know number of downloads.
Huh?
> With mirrors it appears we lost this precious (IMO) info.

The ASF has used 3rd party mirrors for ages, probably from before
JMeter was started.

There has never been a way to measure what downloads are made through
the 3rd party mirrors, so I'm not sure what information you think has
been lost.

> What you propose is a good idea but there are many issues:
> - privacy if we use something like GA
> - all users behind enterprise proxies or with a bad network
> - plus amount of work

Agreed.

> For now we use:
> - number of issues reported
> - questions on SO and mailing lists

Agreed.

> IMO, we should concentrate our efforts on:
> - http2 support
> - fix on undo/redo . With your experience of Netbeans , would you have an
> idea for that missing and always requested feature
> - fix caching of resources in already cached resources
>
> Thanks for your recent works !
> Regards
>
> On Thursday, July 20, 2017, Emilian Bold <emilian.b...@gmail.com> wrote:
>
>> Hello,
>>
>> I was wondering about how many users / downloads does JMeter have and
>> I couldn't find such information except indirectly via the usage
>> statistics from http://www.jmeter-plugins.org/stats/
>>
>> Just yesterday we were discussing about MongoDB support which is
>> deprecated since it's not used very much but usage is measured
>> indirectly from support questions.
>>
>> Are there any other sources of such info?
>>
>> I believe it would be healthy for JMeter to actively measure such
>> usage info in order to better decide the future.
>>
>> A while back NetBeans measured anonymously various metrics in order to
>> prioritise work. Information such as this
>> http://statistics.netbeans.org/analytics/graph/projecttypes.jsp and
>> this http://statistics.netbeans.org/analytics/graph/databaseservers.jsp
>> and this http://statistics.netbeans.org/analytics/graph/technologies.jsp
>> help determine which plugin deserves extra attention and which is
>> heading towards deprecation.
>>
>> So, we should think about how we could implement something like this
>> while respecting the Apache rules surrounding user data.
>>
>> --emi
>>
>
>
> --
> Cordialement.
> Philippe Mouawad.

Reply via email to