community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henk P. Penning" <penn...@uu.nl>
Subject Re: [jira] [Commented] (COMDEV-248) add /dist/ health issues (fwd)
Date Wed, 24 Jan 2018 16:16:43 GMT
Hi,

   FYI ; the updated reporter is now in production ;

   diffs :

   http://svn.apache.org/viewvc/comdev/reporter.apache.org/trunk/site/getjson.py?view=diff&r1=1822083&r2=1822084&pathrev=1822084

   http://svn.apache.org/viewvc/comdev/reporter.apache.org/trunk/site/js/render.js?view=diff&r1=1822113&r2=1822114&pathrev=1822114

   Regards,

   HPP

------------------------------------------------------------   _
Henk P. Penning, ICT-beta                 R Uithof MG-403    _/ \_
Faculty of Science, Utrecht University    T +31 30 253 4106 / \_/ \
Leuvenlaan 4, 3584CE Utrecht, NL          F +31 30 253 4553 \_/ \_/
http://www.staff.science.uu.nl/~penni101/ M penning@uu.nl     \_/

---------- Forwarded message ----------
Date: Tue, 23 Jan 2018 17:55:23 +0100 (CET)
From: Henk P. Penning <penning@uu.nl>
To: dev@community.apache.org
Subject: Re: [jira] [Commented] (COMDEV-248) add /dist/ health issues

On Mon, 22 Jan 2018, Shane Curcuru wrote:

>  Date: Mon, 22 Jan 2018 16:07:20 -0500
>  From: Shane Curcuru <asf@shanecurcuru.org>
>  To: dev@community.apache.org
>  Subject: Re: [jira] [Commented] (COMDEV-248) add /dist/ health issues
>
>  Here's my +1 as a ComDev PMC member asking for Henk to get access to the
>  projects-vm where code behind the reporter tool (and other tools) lives,
>  so that he can continue the below work.
>
>  This is related to COMDEV-248 and:
>
>   https://issues.apache.org/jira/browse/INFRA-15867
>
>  Once this is debugged, we should look for volunteers to check their
>  project's reports for the new "Dist Checker" section of reports, and
>  make any suggestions for improving the docs.

Hi,

   Please try the new (test) reporter at

     https://reporter.apache.org/index-hppdev.html

    The new reporter adds a section "Dist Checker", but only if
    the checker[1] has found some errors in /dist/$project/ ;
    that is, those projects mentioned under "projects with problems"
    by the checker [e.g. aries, bigtop, cloudstack, ... ].

   [1] https://checker.apache.org/

   Any feedback is most welcome ; thanks ; groeten,

   Henk Penning

------------------------------------------------------------   _
Henk P. Penning, ICT-beta                 R Uithof MG-403    _/ \_
Faculty of Science, Utrecht University    T +31 30 253 4106 / \_/ \
Leuvenlaan 4, 3584CE Utrecht, NL          F +31 30 253 4553 \_/ \_/
http://www.staff.science.uu.nl/~penni101/ M penning@uu.nl     \_/

>  Shane Curcuru wrote on 1/18/18 9:45 AM:
>>  For those who don't know Henk, he's built tooling and websites for
>>  checking and understanding keysigning and releases here at Apache for
>>  ages and ages.  This would be a great addition to the reporter tool.
>>
>>  My only comment (for later) is to ensure that when issues are found in a
>>  project, we make sure that the documentation about what the problem is
>>  and how to fix is clear for newer committers.  Henk's already written
>>  this kind of stuff in the README page though, so that should be easy:
>>
>>    https://checker.apache.org/doc/README.html
>> 
>>
>>  Henk P. Penning wrote on 1/18/18 9:26 AM:
>>>  Hi,
>>>
>>>    Regarding : https://issues.apache.org/jira/browse/COMDEV-248
>>>
>>>    Talked with Shane Curcuru on infra hipchat.
>>>
>>>    BASE = https://checker.apache.org/json/
>>>
>>>    The idea is to include $BASE info in https://reporter.apache.org/ ;
>>>    conditionally : nothing is shown if there are no issues to report.
>>>
>>>    The idea is :
>>>
>>>    -- periodically fetch the BASE on projecs-vm.apache.org
>>>
>>>    -- to fix "getjson.py" so the output of (for instance)
>>>       https://reporter.apache.org/getjson.py?only=httpd
>>>       contains an attribute like
>>>         { ..., "checker" : { "httpd": { "problem_count" : N } }, ... }
>>>
>>>    -- fix render.js to (conditionally) show the count + one or two
>>>  references.
>>>
>>>    The plan is to :
>>>
>>>    -- confer with Daniel Gruno, the main author of reporter.
>>>    -- deploy a copy of getjson.py (as getjson-dev.py) and take it from
>>>  there.
>>>
>>>    As I'm new to community-dev and projects-vm.apache.org,
>>>    I have these questions :
>>>
>>>    -- Is this plan the proper way to fix stuff in reporter.apache.org ?
>>>    -- Can I get access to projects-vm.apache [necessary to understand
>>>       the current code ; not everything is in svn or git] ?
>>>
>>>    Thanks ; regards,
>>>
>>>    Henk Penning -- apache.org infrastructure ; dist & mirrors
>>>
>>>  ------------------------------------------------------------   _
>>>  Henk P. Penning, ICT-beta                 R Uithof MG-403   
_/ \_
>>>  Faculty of Science, Utrecht University    T +31 30 253 4106 / \_/ \
>>>  Leuvenlaan 4, 3584CE Utrecht, NL          F +31 30 253 4553 \_/ \_/
>>>  http://www.staff.science.uu.nl/~penni101/ M penning@uu.nl     \_/
>>>
>>>  ---------------------------------------------------------------------
>>>  To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>>>  For additional commands, e-mail: dev-help@community.apache.org
>>> 
>> 
>> 
> 
>
>  -- 
>
>  - Shane
>   https://www.apache.org/foundation/marks/resources
>
>  ---------------------------------------------------------------------
>  To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>  For additional commands, e-mail: dev-help@community.apache.org
> 
>

Mime
View raw message