From commits-return-2567-apmail-community-commits-archive=community.apache.org@community.apache.org Sun Oct 18 12:46:05 2015 Return-Path: X-Original-To: apmail-community-commits-archive@minotaur.apache.org Delivered-To: apmail-community-commits-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6922218135 for ; Sun, 18 Oct 2015 12:46:05 +0000 (UTC) Received: (qmail 19270 invoked by uid 500); 18 Oct 2015 12:46:05 -0000 Delivered-To: apmail-community-commits-archive@community.apache.org Received: (qmail 19239 invoked by uid 500); 18 Oct 2015 12:46:05 -0000 Mailing-List: contact commits-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 commits@community.apache.org Received: (qmail 19229 invoked by uid 99); 18 Oct 2015 12:46:05 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 18 Oct 2015 12:46:05 +0000 Date: Sun, 18 Oct 2015 12:46:05 +0000 (UTC) From: "Sebb (JIRA)" To: commits@community.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (COMDEV-174) projects.json is inaccurate for graduated podlings MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Sebb created COMDEV-174: --------------------------- Summary: projects.json is inaccurate for graduated podlings Key: COMDEV-174 URL: https://issues.apache.org/jira/browse/COMDEV-174 Project: Community Development Issue Type: Bug Components: Reporter Tool Reporter: Sebb The entries in projects.json come from scraping the page http://people.apache.org/committer-index.html This includes both LDAP groups and auth groups that are defined in the asf-authorization-template file. The script takes note of when a group is first seen, any subsequent changes are regarded as additions to the group. The reporter tool is supposed to show what changes the PMC has made. However, when a podling graduates, the template group is converted into the corresponding LDAP unix group. This means that changes to the podling group are recorded from the start of the podling rather than the start of the PMC. One way to fix this might be to ignore changes that occurred before the PMC creation date. Unfortunately the exact creation date is not currently recorded in the committee-info data file (only the month/year is stated). It should be possible to deduce the actual date from the earliest joining dates (assuming these are accurate). -- This message was sent by Atlassian JIRA (v6.3.4#6332)