> 6. aug. 2019 kl. 17:35 skrev Daniel Gruno <humbed...@apache.org>:
>> Another question - I don't see mailing list stats for the list 
>> solr-u...@lucene.apache.org <mailto:solr-u...@lucene.apache.org>, what is 
>> the logic behind what lists to show and not?
>> The solr-user@ list has 1403 mails last 3 months 
>> https://lists.apache.org/list.html?solr-u...@lucene.apache.org:lte=3M: 
>> <https://lists.apache.org/list.html?solr-u...@lucene.apache.org:lte=3M:>
> 
> It shows lists where there is a change to what happened in the previous 
> quarter, that is, if traffic went up or down by more than a few percent.
> We could opt to display all lists on the statistics page, and keep the editor 
> as just showing the ones with significant changes.

The Lucene project has several lists that not active due to historic reasons, 
such as c-commits@, ruby-dev@, solr-commits@, java-commits@ and c-dev@ and more.

The old reporter lists all of these and that is just noise. What if we show all 
lists with some significant traffic, and filter out those with 0 (or very few) 
mails? 
The % change is btw not a very reliable metric for low-volume lists such as our 
gene...@lucene.apache.org, it will probably be tagged as increasing/decreasing 
every single quarter (10-30 email). 

>> --
>> Jan Høydahl, search solution architect
>> Cominvent AS - www.cominvent.com
>>> 6. aug. 2019 kl. 17:25 skrev Daniel Gruno <humbed...@apache.org>:
>>> 
>>> On 8/6/19 5:20 PM, Jan Høydahl wrote:
>>>> The reporter wizard is impressive, nice work!
>>>> One issue: the "Recent releases" section of the wizard shows the three 
>>>> OLDEST releases, not the newest :)
>>> 
>>> It's supposed to sort reverse by age, so hm...
>>> which project are you seeing the issue with? and have you tried a hard 
>>> refresh (ctrl+f5) to maybe clear some cache?
>>> 
>>> With regards,
>>> Daniel.
>>> 
>>>> --
>>>> Jan Høydahl, search solution architect
>>>> Cominvent AS - www.cominvent.com
>>>>> 6. aug. 2019 kl. 12:16 skrev Daniel Gruno <humbed...@apache.org>:
>>>>> 
>>>>> On 8/6/19 12:14 PM, Maxim Solodovnik wrote:
>>>>>> Hello Daniel,
>>>>>> There seems to be an issue with email stats
>>>>>> Just have checked 
>>>>>> https://reporter.apache.org/wizard/statistics?openmeetings
>>>>>> There are 3 different charts labeled the same user@ (suspect one should 
>>>>>> be
>>>>>> dev@ and one private@) ...
>>>>> 
>>>>> parsing bug :) one is user@ the other two are the localized user lists. 
>>>>> I'll fix!
>>>>> 
>>>>>> On Tue, 6 Aug 2019 at 17:00, Daniel Gruno <humbed...@apache.org> wrote:
>>>>>>> On 8/6/19 9:08 AM, Christopher wrote:
>>>>>>>> 
>>>>>>>> The score may be arbitrary, but it's still useful to view
>>>>>>>> upward/downward trends of the score in the context of a single
>>>>>>>> project.... not so useful to compare to other projects.
>>>>>>>> 
>>>>>>> 
>>>>>>> I've added it to the statistics page (see below).
>>>>>>> 
>>>>>>>> 
>>>>>>>> Yes, that's basically what I'm getting at. As far as I can tell,
>>>>>>>> https://reporter.apache.org is useful to 3 groups of people:
>>>>>>>> 
>>>>>>>> 1. PMC Chairs preparing board reports (the bottom "Report template"
>>>>>>> section)
>>>>>>>> 2. Release managers (recording new releases -- probably the most
>>>>>>>> frequent visitors)
>>>>>>>> 3. Viewing of the informational content (charts, graphs, list of
>>>>>>>> historical releases, stats, etc., to include use of "Members-only
>>>>>>>> Quick-nav" button)
>>>>>>>> 
>>>>>>>> As far as I can tell, the wizard is only a substitute for the "Report
>>>>>>>> template" section of the site, satisfying the first use case, but not
>>>>>>>> the other two. The second use case is easily satisfied with a few
>>>>>>>> links ("Add a release", "Fetch releases from JIRA", "Manage release
>>>>>>>> versions", or some equivalent set). The third use case seems to be the
>>>>>>>> focus of the current site, based on the layout, and the significant
>>>>>>>> space the different information takes up (colorful charts and fonts,
>>>>>>>> use of italics and bold, section headers to this various information).
>>>>>>>> It is this third use case that seems at greatest risk of being lost if
>>>>>>>> the site is replaced by the wizard (as is). If the wizard view were to
>>>>>>>> add these things, or if they were available on whimsy, then I think it
>>>>>>>> could replace the current view. But if the wizard were to replace the
>>>>>>>> site right now, it looks like those features would simply go away.
>>>>>>>> 
>>>>>>> 
>>>>>>> I can relate to this, and see how reporter.a.o is also a place for
>>>>>>> general curiousness :) So I've added a more detailed stats page for each
>>>>>>> project, and put links to both the editor and the stats page on the
>>>>>>> front page of the wizard.
>>>>>>> 
>>>>>>> New stats page looks like this:
>>>>>>> https://reporter.apache.org/wizard/statistics?beam
>>>>>>> 
>>>>>>> With regards,
>>>>>>> Daniel.
>>>>>>> 
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>>>>>>> For additional commands, e-mail: dev-h...@community.apache.org
>>>>>>> 
>>>>>>> 
>>>>> 
>>>>> 
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>>>>> For additional commands, e-mail: dev-h...@community.apache.org
>>>>> 
>>> 
>>> 
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org 
>>> <mailto:dev-unsubscr...@community.apache.org> 
>>> <mailto:dev-unsubscr...@community.apache.org 
>>> <mailto:dev-unsubscr...@community.apache.org>>
>>> For additional commands, e-mail: dev-h...@community.apache.org 
>>> <mailto:dev-h...@community.apache.org> 
>>> <mailto:dev-h...@community.apache.org 
>>> <mailto:dev-h...@community.apache.org>>
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org 
> <mailto:dev-unsubscr...@community.apache.org>
> For additional commands, e-mail: dev-h...@community.apache.org 
> <mailto:dev-h...@community.apache.org>

Reply via email to