Return-Path: X-Original-To: apmail-community-dev-archive@minotaur.apache.org Delivered-To: apmail-community-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 94BB217788 for ; Tue, 3 Mar 2015 14:11:06 +0000 (UTC) Received: (qmail 82931 invoked by uid 500); 3 Mar 2015 14:11:01 -0000 Delivered-To: apmail-community-dev-archive@community.apache.org Received: (qmail 82695 invoked by uid 500); 3 Mar 2015 14:11:01 -0000 Mailing-List: contact dev-help@community.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@community.apache.org Delivered-To: mailing list dev@community.apache.org Received: (qmail 82683 invoked by uid 99); 3 Mar 2015 14:11:01 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Mar 2015 14:11:01 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW X-Spam-Check-By: apache.org Received-SPF: error (nike.apache.org: local policy) Received: from [209.85.216.182] (HELO mail-qc0-f182.google.com) (209.85.216.182) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Mar 2015 14:10:35 +0000 Received: by qcyl6 with SMTP id l6so30528585qcy.2 for ; Tue, 03 Mar 2015 06:10:13 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=pVpYJ9ZBap9dqsD3RHjRzaDwwWKTZX02z8r8hEPTaus=; b=Qxf6vpLRFkYE4E00VjU3mPibOwFx2JXMtGaL99JdLgk/z8ijwpaZoMUHlWiSQSX93D 4YAb/HHrXkVfl8dBV1zCt3WIWOqRLcmbOiZYyAZQ5sYH0e7ABNvfE8TY6GY7jJL6XftV ++DH9jzpD4OnGqHdNpyya6kgaNR58DEZT0u7/p7B3L7WfEC2Jg72CaOE/iVoPMjMG8us b/elkb+VI7TRW6ZufpVXI9BsPMttlgJg68Iq3PCTS40ttanRaijMYBn5gZLhH0kQhfeL Dk8ZzTv/Iyr8YLri053GkoXPsqi6ghTtJb/OfPwCTc9iTmzjJksC0P5/mVPp5yS4ydgn 28eQ== X-Gm-Message-State: ALoCoQnSpVeTAwEirPceoGSCzPuiCBnR7zewLI2z7tG3+BosqmI1RIj7YNRQ2DbenJmqpD3A+tZV X-Received: by 10.55.16.97 with SMTP id a94mr12027407qkh.86.1425391813113; Tue, 03 Mar 2015 06:10:13 -0800 (PST) Received: from localhost.localdomain (cpe-74-138-23-246.swo.res.rr.com. [74.138.23.246]) by mx.google.com with ESMTPSA id 63sm461182qhw.30.2015.03.03.06.10.11 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 03 Mar 2015 06:10:11 -0800 (PST) Message-ID: <54F5C0C0.1050909@rcbowen.com> Date: Tue, 03 Mar 2015 09:10:08 -0500 From: Rich Bowen User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: dev@community.apache.org Subject: Re: Apache Reporter Service References: <54F591F8.8010305@apache.org> <54F5A039.7000005@apache.org> In-Reply-To: <54F5A039.7000005@apache.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On 03/03/2015 06:51 AM, Daniel Gruno wrote: > Hi Rob, > If the release you messed up is within the last 3 months, you can just > override it with a fake older date and make it go out of view (add the > release again and set the date to 1970-01-01 for instance). I'll work on > a smarter editing feature soon. Fake data in the system seems like something that we'll regret eventually. > > Viewing previous release cycles and such would indeed be cool, but I'd > probably need some sort of mock-up from you to be able to create it - > I'm not sure how it should be displayed and what info to include. I'm > not saying you should open up ye olde MS Paint and draw something, but > some sort of visual idea would be nice. > > With regards, > Daniel. > > On 2015-03-03 12:44, Rob Vesse wrote: >> Daniel >> >> This is really cool >> >> Quick question - how do we correct errors in the release data? I just >> went through and added all the releases for the PMC of which I am a >> member >> and realised I made a typo in the version number for one of our releases. >> Where do I go to correct this? >> >> Also it would be nice if the web UI would allow you to view all the >> releases and give you average release cadence >> >> Keep up the great work! >> >> Thanks, >> >> Rob >> >> On 03/03/2015 10:50, "Daniel Gruno" wrote: >> >>> Hi folks, >>> as some of you will have noticed, either by the commits I just made or >>> conversations going on elsewhere, I have started work on a new helper >>> system for PMCs called the Apache Reporter Service. This is sort of an >>> external addition to Whimsy, and shows various statistics and data for >>> projects, designed to aid chairs (and other lurkers) in viewing and >>> compiling data for board reports. >>> >>> The system is now live at: https://reporter.apache.org - you will need >>> to be a PMC member of a project to view this site, and you will - in >>> general - only be shown data for projects where you are on the PMC. >>> >>> The system will show you: >>> - Your next report date and the chair of the project >>> - PMC and committership changes over the past 3 months, as well as >>> latest additions if >3 months ago >>> - The latest releases done this quarter (if added by RMs) >>> - Mailing list statistics: number of subscribers as well as number of >>> emails sent this quarter and the previous >>> - JIRA tickets opened/closed this quarter (if correctly mapped within >>> the system) >>> - A mock-up of a board report, with the above data compiled into it (to >>> be edited heavily by the chair!) >>> >>> Quick-navigation (hot-links) can be done by using the LDAP name of a >>> project in the URL, for instance: https://reporter.apache.org/?apr would >>> navigate directly to the Apache Portable Runtime project if you are on >>> that PMC (or a member of the foundation). >>> >>> The report mock-up is meant as a help only, not a canonical template for >>> board reports. Vital items, such as community activity and board issues >>> are intentionally left for the reporter (chair) to fill out, and heaven >>> help the woman/man who submits a report with these fields left as >>> default ;). >>> >>> Later today, I plan to enable the distribution watching part of this >>> service, which will send reminders to anyone who pushes a release, that >>> they should (not required, but if they want to!) add their release data >>> to the system, so as to help others using the system to get an overview >>> of the status of any given project. >>> >>> I have already gotten a lot of really useful feedback, but if you see >>> something you'd like to change, either shoot me an email here on the >>> comdev list, or commit a change to the system in svn. >>> >>> With regards, >>> Daniel. >> >> >> > -- Rich Bowen - rbowen@rcbowen.com - @rbowen http://apachecon.com/ - @apachecon