You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@community.apache.org by Daniel Gruno <hu...@apache.org> on 2019/08/05 08:41:42 UTC
[Lazy Consensus] Changing the default reporter tool
Hi folks,
I would like to change the default reporter.a.o[1] to be the new wizard
tool[2]. I think it's a good overall improvement and honestly do not see
any downsides to switching. So I'm calling a lazy consensus "vote" for
this change. If there are people that strongly prefer the old one,
please do let me know, and please elaborate on what you'd like to see
changed in the new tool for it to become the default.
I'll let this run for a few days and see if anyone objects :)
With regards,
Daniel.
[1] https://reporter.apache.org/
[2] https://reporter.apache.org/wizard/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: [Lazy Consensus] Changing the default reporter tool
Posted by Daniel Gruno <hu...@apache.org>.
On 8/5/19 10:53 AM, Myrle Krantz wrote:
> Since it's the PMC chairs who use this, I'd much prefer you put this call
> for consensus up over on board@.
mkay, let's do both! :D
>
> Best,
> Myrle
>
> On Mon, Aug 5, 2019 at 10:41 AM Daniel Gruno <hu...@apache.org> wrote:
>
>> Hi folks,
>> I would like to change the default reporter.a.o[1] to be the new wizard
>> tool[2]. I think it's a good overall improvement and honestly do not see
>> any downsides to switching. So I'm calling a lazy consensus "vote" for
>> this change. If there are people that strongly prefer the old one,
>> please do let me know, and please elaborate on what you'd like to see
>> changed in the new tool for it to become the default.
>>
>> I'll let this run for a few days and see if anyone objects :)
>>
>> With regards,
>> Daniel.
>>
>> [1] https://reporter.apache.org/
>> [2] https://reporter.apache.org/wizard/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>> For additional commands, e-mail: dev-help@community.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: [Lazy Consensus] Changing the default reporter tool
Posted by Myrle Krantz <my...@apache.org>.
Since it's the PMC chairs who use this, I'd much prefer you put this call
for consensus up over on board@.
Best,
Myrle
On Mon, Aug 5, 2019 at 10:41 AM Daniel Gruno <hu...@apache.org> wrote:
> Hi folks,
> I would like to change the default reporter.a.o[1] to be the new wizard
> tool[2]. I think it's a good overall improvement and honestly do not see
> any downsides to switching. So I'm calling a lazy consensus "vote" for
> this change. If there are people that strongly prefer the old one,
> please do let me know, and please elaborate on what you'd like to see
> changed in the new tool for it to become the default.
>
> I'll let this run for a few days and see if anyone objects :)
>
> With regards,
> Daniel.
>
> [1] https://reporter.apache.org/
> [2] https://reporter.apache.org/wizard/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org
>
>
Re: [Lazy Consensus] Changing the default reporter tool
Posted by Jan Høydahl <ja...@cominvent.com>.
Happy to help somewhere. If slack counts is something you see useful to track, I'd be happy to whip up a Kibble scanner plugin for Slack, if that makes sense?
--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com
> 8. aug. 2019 kl. 15:16 skrev Rich Bowen <rb...@rcbowen.com>:
>
> If I might make a plug ... two, in fact.
>
> 1) The Kibble project, which provides these statistics, is a warm welcoming place, if anyone is looking for a way to contribute to an exciting project.
>
> 2) reporter.a.o lives in the community.apache.org svn repo, and welcomes patches.
>
> As both Kibble PMC chair, and a ComDev PMC member, I am often concerned by the degree to which many of our project conversations are people asking for stuff, and then Daniel doing it. Yes, Daniel does awesome work, but bus-factor-1 project make me very, very squidgy. Both for sustainability of the project when Daniel burns out, and for the misperception that this service is somehow a function of Infra and should have an SLA.
>
> So ... all that to say, we really would love to see more people tinkering with this code.
>
> --
> Rich Bowen - rbowen@rcbowen.com
> http://rcbowen.com/
> @rbowen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org
>
Re: [Lazy Consensus] Changing the default reporter tool
Posted by Rich Bowen <rb...@rcbowen.com>.
If I might make a plug ... two, in fact.
1) The Kibble project, which provides these statistics, is a warm
welcoming place, if anyone is looking for a way to contribute to an
exciting project.
2) reporter.a.o lives in the community.apache.org svn repo, and welcomes
patches.
As both Kibble PMC chair, and a ComDev PMC member, I am often concerned
by the degree to which many of our project conversations are people
asking for stuff, and then Daniel doing it. Yes, Daniel does awesome
work, but bus-factor-1 project make me very, very squidgy. Both for
sustainability of the project when Daniel burns out, and for the
misperception that this service is somehow a function of Infra and
should have an SLA.
So ... all that to say, we really would love to see more people
tinkering with this code.
--
Rich Bowen - rbowen@rcbowen.com
http://rcbowen.com/
@rbowen
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: [Lazy Consensus] Changing the default reporter tool
Posted by Jan Høydahl <ja...@cominvent.com>.
Just one more suggestion - perhaps Slack metrics would make sense as well for the community health of a project?
--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com
> 6. aug. 2019 kl. 18:58 skrev Daniel Gruno <hu...@apache.org>:
>
> On 8/6/19 6:48 PM, Joan Touzet wrote:
>> On 2019-08-06 12:47, Daniel Gruno wrote:
>>> On 8/6/19 6:43 PM, Jan Høydahl wrote:
>>>>> 6. aug. 2019 kl. 17:35 skrev Daniel Gruno <hu...@apache.org>:
>>>>>> Another question - I don't see mailing list stats for the list
>>>>>> solr-user@lucene.apache.org <ma...@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-user@lucene.apache.org:lte=3M:
>>>>>> <https://lists.apache.org/list.html?solr-user@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 general@lucene.apache.org, it will probably be tagged as
>>>> increasing/decreasing every single quarter (10-30 email).
>>>>
>>>
>>> Consider it done. All lists with fewer than 10 emails in
>>> present/previous quarter (depending on the trend) are filtered out and
>>> the rest are now all shown :) on the statistics page, that is.
>> Request to never filter out dev@. If dev@ is really that quiet...we (PMC
>> members, or the Board) should know about it.
>
> I've added a special "if dev@" rule to always show the stats for that list.
>
>> -Joan
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org <ma...@community.apache.org>
>> For additional commands, e-mail: dev-help@community.apache.org <ma...@community.apache.org>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org <ma...@community.apache.org>
> For additional commands, e-mail: dev-help@community.apache.org <ma...@community.apache.org>
Re: [Lazy Consensus] Changing the default reporter tool
Posted by Daniel Gruno <hu...@apache.org>.
On 8/6/19 6:48 PM, Joan Touzet wrote:
> On 2019-08-06 12:47, Daniel Gruno wrote:
>> On 8/6/19 6:43 PM, Jan Høydahl wrote:
>>>> 6. aug. 2019 kl. 17:35 skrev Daniel Gruno <hu...@apache.org>:
>>>>> Another question - I don't see mailing list stats for the list
>>>>> solr-user@lucene.apache.org <ma...@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-user@lucene.apache.org:lte=3M:
>>>>> <https://lists.apache.org/list.html?solr-user@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 general@lucene.apache.org, it will probably be tagged as
>>> increasing/decreasing every single quarter (10-30 email).
>>>
>>
>> Consider it done. All lists with fewer than 10 emails in
>> present/previous quarter (depending on the trend) are filtered out and
>> the rest are now all shown :) on the statistics page, that is.
>
> Request to never filter out dev@. If dev@ is really that quiet...we (PMC
> members, or the Board) should know about it.
I've added a special "if dev@" rule to always show the stats for that list.
>
> -Joan
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: [Lazy Consensus] Changing the default reporter tool
Posted by Joan Touzet <wo...@apache.org>.
On 2019-08-06 12:47, Daniel Gruno wrote:
> On 8/6/19 6:43 PM, Jan Høydahl wrote:
>>> 6. aug. 2019 kl. 17:35 skrev Daniel Gruno <hu...@apache.org>:
>>>> Another question - I don't see mailing list stats for the list
>>>> solr-user@lucene.apache.org <ma...@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-user@lucene.apache.org:lte=3M:
>>>> <https://lists.apache.org/list.html?solr-user@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 general@lucene.apache.org, it will probably be tagged as
>> increasing/decreasing every single quarter (10-30 email).
>>
>
> Consider it done. All lists with fewer than 10 emails in
> present/previous quarter (depending on the trend) are filtered out and
> the rest are now all shown :) on the statistics page, that is.
Request to never filter out dev@. If dev@ is really that quiet...we (PMC
members, or the Board) should know about it.
-Joan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: [Lazy Consensus] Changing the default reporter tool
Posted by Daniel Gruno <hu...@apache.org>.
On 8/6/19 6:43 PM, Jan Høydahl wrote:
>> 6. aug. 2019 kl. 17:35 skrev Daniel Gruno <hu...@apache.org>:
>>> Another question - I don't see mailing list stats for the list solr-user@lucene.apache.org <ma...@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-user@lucene.apache.org:lte=3M: <https://lists.apache.org/list.html?solr-user@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 general@lucene.apache.org, it will probably be tagged as increasing/decreasing every single quarter (10-30 email).
>
Consider it done. All lists with fewer than 10 emails in
present/previous quarter (depending on the trend) are filtered out and
the rest are now all shown :) on the statistics page, that is.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: [Lazy Consensus] Changing the default reporter tool
Posted by Jan Høydahl <ja...@cominvent.com>.
> 6. aug. 2019 kl. 17:35 skrev Daniel Gruno <hu...@apache.org>:
>> Another question - I don't see mailing list stats for the list solr-user@lucene.apache.org <ma...@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-user@lucene.apache.org:lte=3M: <https://lists.apache.org/list.html?solr-user@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 general@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 <hu...@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 <hu...@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 <hu...@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-unsubscribe@community.apache.org
>>>>>>> For additional commands, e-mail: dev-help@community.apache.org
>>>>>>>
>>>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>>>>> For additional commands, e-mail: dev-help@community.apache.org
>>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org <ma...@community.apache.org> <mailto:dev-unsubscribe@community.apache.org <ma...@community.apache.org>>
>>> For additional commands, e-mail: dev-help@community.apache.org <ma...@community.apache.org> <mailto:dev-help@community.apache.org <ma...@community.apache.org>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org <ma...@community.apache.org>
> For additional commands, e-mail: dev-help@community.apache.org <ma...@community.apache.org>
Re: [Lazy Consensus] Changing the default reporter tool
Posted by Daniel Gruno <hu...@apache.org>.
On 8/6/19 5:29 PM, Jan Høydahl wrote:
> This was for Lucene, https://reporter.apache.org/wizard/statistics?lucene
Turns out the age was being alphasorted, not numbersorted >_<. Fixed,
thanks for reporting!
>
> Another question - I don't see mailing list stats for the list solr-user@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-user@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.
>
> --
> Jan Høydahl, search solution architect
> Cominvent AS - www.cominvent.com
>
>> 6. aug. 2019 kl. 17:25 skrev Daniel Gruno <hu...@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 <hu...@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 <hu...@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-unsubscribe@community.apache.org
>>>>>> For additional commands, e-mail: dev-help@community.apache.org
>>>>>>
>>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>>>> For additional commands, e-mail: dev-help@community.apache.org
>>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org <ma...@community.apache.org>
>> For additional commands, e-mail: dev-help@community.apache.org <ma...@community.apache.org>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: [Lazy Consensus] Changing the default reporter tool
Posted by Jan Høydahl <ja...@cominvent.com>.
This was for Lucene, https://reporter.apache.org/wizard/statistics?lucene
Another question - I don't see mailing list stats for the list solr-user@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-user@lucene.apache.org:lte=3M:
--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com
> 6. aug. 2019 kl. 17:25 skrev Daniel Gruno <hu...@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 <hu...@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 <hu...@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-unsubscribe@community.apache.org
>>>>> For additional commands, e-mail: dev-help@community.apache.org
>>>>>
>>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>>> For additional commands, e-mail: dev-help@community.apache.org
>>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org <ma...@community.apache.org>
> For additional commands, e-mail: dev-help@community.apache.org <ma...@community.apache.org>
Re: [Lazy Consensus] Changing the default reporter tool
Posted by Daniel Gruno <hu...@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 <hu...@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 <hu...@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-unsubscribe@community.apache.org
>>>> For additional commands, e-mail: dev-help@community.apache.org
>>>>
>>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>> For additional commands, e-mail: dev-help@community.apache.org
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: [Lazy Consensus] Changing the default reporter tool
Posted by Jan Høydahl <ja...@cominvent.com>.
The reporter wizard is impressive, nice work!
One issue: the "Recent releases" section of the wizard shows the three OLDEST releases, not the newest :)
--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com
> 6. aug. 2019 kl. 12:16 skrev Daniel Gruno <hu...@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 <hu...@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-unsubscribe@community.apache.org
>>> For additional commands, e-mail: dev-help@community.apache.org
>>>
>>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org
>
Re: [Lazy Consensus] Changing the default reporter tool
Posted by Daniel Gruno <hu...@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 <hu...@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-unsubscribe@community.apache.org
>> For additional commands, e-mail: dev-help@community.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: [Lazy Consensus] Changing the default reporter tool
Posted by Maxim Solodovnik <so...@gmail.com>.
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@) ...
On Tue, 6 Aug 2019 at 17:00, Daniel Gruno <hu...@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-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org
>
>
--
WBR
Maxim aka solomax
Re: [Lazy Consensus] Changing the default reporter tool
Posted by Daniel Gruno <hu...@apache.org>.
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-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: [Lazy Consensus] Changing the default reporter tool
Posted by Christopher <ct...@apache.org>.
On Tue, Aug 6, 2019 at 2:04 AM Daniel Gruno <hu...@apache.org> wrote:
>
> On 8/6/19 2:54 AM, Christopher wrote:
> > The new reporter wizard helps folks create a board report, but it
> > doesn't seem to have any of the other features of the current
> > reporeter.a.o tool. For example, helping them to manage recorded
> > releases (https://reporter.apache.org/addrelease.html?<tlp>), view
> > community health score (https://reporter.apache.org/chi.py#<tlp>),
> > quickly view JIRA stats and PMC/committer changes, etc.
> >
> > Are all of those features available elsewhere, or will they be
> > replaced by the new tool?
>
> Hi Christopher,
> I am wondering if you are perhaps looking at an older cached version of
> the tool? Or maybe I am misunderstanding what you mean by having the
> information available, but I'll attempt to answer in any case.
>
> PMC/committer changes should still very much be in the editor, under
> "Membership data", including new information bits such as the age of the
> project and the ratio between committers and pmc members.
>
> JIRA stats and a whole bunch of new stats, are available in the
> Community Health section, though they are not inserted into the report
> itself by default, as the board have expressed countless times that they
> do not wish to just see these figures, but rather a description of the
> significance of the numbers. When you are in the community health
> section, the right hand panel will display statistics such as:
> - jiras opened/closed
> - github prs/issues opened/closed
> - emails sent
> - commits done, committers active
>
> It will also allow you to see the most discussed issues/emails, and as a
> new thing, it will display how tickets/code/committer figures relate to
> the previous quarter.
>
> The 'Project activity' section lists recent releases or, in the case of
> no such things found, the last three releases, and has a link to
> managing the release data.
>
> As for the CHI score, we can have that displayed in the tool....but,
> it's a rather arbitrary figure that I made up, and it has caused some
> confusion in the past. Perhaps that warrants a longer discussion :)
>
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.
> If, instead, you mean something along the lines of "I don't want help
> writing a report, I just want to casually look at the data available",
> perhaps what we could do is display that on a separate page that has the
> same information as the wizard, but just displays all the data on one
> big page?
>
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.
> With regards,
> Daniel.
>
> >
> > On Mon, Aug 5, 2019 at 4:41 AM Daniel Gruno <hu...@apache.org> wrote:
> >>
> >> Hi folks,
> >> I would like to change the default reporter.a.o[1] to be the new wizard
> >> tool[2]. I think it's a good overall improvement and honestly do not see
> >> any downsides to switching. So I'm calling a lazy consensus "vote" for
> >> this change. If there are people that strongly prefer the old one,
> >> please do let me know, and please elaborate on what you'd like to see
> >> changed in the new tool for it to become the default.
> >>
> >> I'll let this run for a few days and see if anyone objects :)
> >>
> >> With regards,
> >> Daniel.
> >>
> >> [1] https://reporter.apache.org/
> >> [2] https://reporter.apache.org/wizard/
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> >> For additional commands, e-mail: dev-help@community.apache.org
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> > For additional commands, e-mail: dev-help@community.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: [Lazy Consensus] Changing the default reporter tool
Posted by Daniel Gruno <hu...@apache.org>.
On 8/6/19 2:54 AM, Christopher wrote:
> The new reporter wizard helps folks create a board report, but it
> doesn't seem to have any of the other features of the current
> reporeter.a.o tool. For example, helping them to manage recorded
> releases (https://reporter.apache.org/addrelease.html?<tlp>), view
> community health score (https://reporter.apache.org/chi.py#<tlp>),
> quickly view JIRA stats and PMC/committer changes, etc.
>
> Are all of those features available elsewhere, or will they be
> replaced by the new tool?
Hi Christopher,
I am wondering if you are perhaps looking at an older cached version of
the tool? Or maybe I am misunderstanding what you mean by having the
information available, but I'll attempt to answer in any case.
PMC/committer changes should still very much be in the editor, under
"Membership data", including new information bits such as the age of the
project and the ratio between committers and pmc members.
JIRA stats and a whole bunch of new stats, are available in the
Community Health section, though they are not inserted into the report
itself by default, as the board have expressed countless times that they
do not wish to just see these figures, but rather a description of the
significance of the numbers. When you are in the community health
section, the right hand panel will display statistics such as:
- jiras opened/closed
- github prs/issues opened/closed
- emails sent
- commits done, committers active
It will also allow you to see the most discussed issues/emails, and as a
new thing, it will display how tickets/code/committer figures relate to
the previous quarter.
The 'Project activity' section lists recent releases or, in the case of
no such things found, the last three releases, and has a link to
managing the release data.
As for the CHI score, we can have that displayed in the tool....but,
it's a rather arbitrary figure that I made up, and it has caused some
confusion in the past. Perhaps that warrants a longer discussion :)
If, instead, you mean something along the lines of "I don't want help
writing a report, I just want to casually look at the data available",
perhaps what we could do is display that on a separate page that has the
same information as the wizard, but just displays all the data on one
big page?
With regards,
Daniel.
>
> On Mon, Aug 5, 2019 at 4:41 AM Daniel Gruno <hu...@apache.org> wrote:
>>
>> Hi folks,
>> I would like to change the default reporter.a.o[1] to be the new wizard
>> tool[2]. I think it's a good overall improvement and honestly do not see
>> any downsides to switching. So I'm calling a lazy consensus "vote" for
>> this change. If there are people that strongly prefer the old one,
>> please do let me know, and please elaborate on what you'd like to see
>> changed in the new tool for it to become the default.
>>
>> I'll let this run for a few days and see if anyone objects :)
>>
>> With regards,
>> Daniel.
>>
>> [1] https://reporter.apache.org/
>> [2] https://reporter.apache.org/wizard/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>> For additional commands, e-mail: dev-help@community.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: [Lazy Consensus] Changing the default reporter tool
Posted by Luciano Resende <lu...@gmail.com>.
On Mon, Aug 5, 2019 at 5:54 PM Christopher <ct...@apache.org> wrote:
>
> The new reporter wizard helps folks create a board report, but it
> doesn't seem to have any of the other features of the current
> reporeter.a.o tool. For example, helping them to manage recorded
> releases (https://reporter.apache.org/addrelease.html?<tlp>), view
> community health score (https://reporter.apache.org/chi.py#<tlp>),
> quickly view JIRA stats and PMC/committer changes, etc.
>
> Are all of those features available elsewhere, or will they be
> replaced by the new tool?
That was the exactly thing that came to mind, how about the actual
widget be an action available from the ui where then it start the
wizard to guide the creation of the report ?
--
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: [Lazy Consensus] Changing the default reporter tool
Posted by Christopher <ct...@apache.org>.
The new reporter wizard helps folks create a board report, but it
doesn't seem to have any of the other features of the current
reporeter.a.o tool. For example, helping them to manage recorded
releases (https://reporter.apache.org/addrelease.html?<tlp>), view
community health score (https://reporter.apache.org/chi.py#<tlp>),
quickly view JIRA stats and PMC/committer changes, etc.
Are all of those features available elsewhere, or will they be
replaced by the new tool?
On Mon, Aug 5, 2019 at 4:41 AM Daniel Gruno <hu...@apache.org> wrote:
>
> Hi folks,
> I would like to change the default reporter.a.o[1] to be the new wizard
> tool[2]. I think it's a good overall improvement and honestly do not see
> any downsides to switching. So I'm calling a lazy consensus "vote" for
> this change. If there are people that strongly prefer the old one,
> please do let me know, and please elaborate on what you'd like to see
> changed in the new tool for it to become the default.
>
> I'll let this run for a few days and see if anyone objects :)
>
> With regards,
> Daniel.
>
> [1] https://reporter.apache.org/
> [2] https://reporter.apache.org/wizard/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org