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 CurcuruTo: 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 UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@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 penn...@uu.nl \_/ - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org -- - Shane https://www.apache.org/foundation/marks/resources - 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
Re: Old JIRA issues - close?
On Tue, Jan 23, 2018 at 1:39 PM, Isabel Drost-Frommwrote: > ...Would it > make sense to close the ones that haven't received any activity since 2016?... +1, if needed they can be reopened or recreated. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Old JIRA issues - close?
Isabel Drost-Fromm wrote on 1/23/18 7:39 AM: > Hi, > > within the COMDEV Jira there are a couple JIRA issues that haven't received > any > comments in the past few years, in addition there are a couple issues that > based > on their description or labels were created for GSoC in previous years. Would > it > make sense to close the ones that haven't received any activity since 2016? We started in Nov, and yes, it still needs work to keep JIRA clean: https://lists.apache.org/thread.html/16edd8b507af8bcf3a2259b11231570d56496222c13d73d2f6bea411@%3Cdev.community.apache.org%3E Some individual projects may still want to use their past GSoC issues for the new year, so... check first (or remind people that issues can always be re-opened). Thanks! -- - Shane https://www.apache.org/foundation/marks/resources - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Created] (COMDEV-253) Add mission statement to project web page
Isabel Drost-Fromm created COMDEV-253: - Summary: Add mission statement to project web page Key: COMDEV-253 URL: https://issues.apache.org/jira/browse/COMDEV-253 Project: Community Development Issue Type: Improvement Components: Projects Website Reporter: Isabel Drost-Fromm Attachments: add_mission_to_website.diff A while ago Rich proposed to adopt a new mission for comdev. I only heard positive feedback for that. Nothing of it is reflected in the comdev web page though. The intention of this patch is to add the proposed mission statement front and center to the comdev web page. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Old JIRA issues - close?
+1 On Tue, Jan 23, 2018 at 7:39 PM, Isabel Drost-Frommwrote: > Hi, > > within the COMDEV Jira there are a couple JIRA issues that haven't > received any > comments in the past few years, in addition there are a couple issues that > based > on their description or labels were created for GSoC in previous years. > Would it > make sense to close the ones that haven't received any activity since 2016? > > > Isabel > > > -- > Sorry for any typos: Mail was typed in vim, written in mutt, via ssh (most > likely involving some kind of mobile connection only.) > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > > -- WBR Maxim aka solomax
[jira] [Commented] (COMDEV-52) Launch ASF Mentor programme
[ https://issues.apache.org/jira/browse/COMDEV-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16335714#comment-16335714 ] Isabel Drost-Fromm commented on COMDEV-52: -- Is this issue still valid? It seems fairly dated... > Launch ASF Mentor programme > --- > > Key: COMDEV-52 > URL: https://issues.apache.org/jira/browse/COMDEV-52 > Project: Community Development > Issue Type: Task > Components: Comdev >Reporter: Ross Gardler >Priority: Critical > > The ASF mentoring programme is designed to assist people who wish to > understand how the ASF works. > See http://community.apache.org/mentoringprogramme.html > This is a parent task to track the creation and implementation of the mentor > programme. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org