community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Isabel Drost-Fromm (JIRA)" <>
Subject [jira] [Closed] (COMDEV-174) projects.json is inaccurate for graduated podlings
Date Wed, 24 Jan 2018 08:58:00 GMT


Isabel Drost-Fromm closed COMDEV-174.
    Resolution: Won't Fix

Hasn't been touched in years. Please reopen if still needed

> projects.json is inaccurate for graduated podlings
> --------------------------------------------------
>                 Key: COMDEV-174
>                 URL:
>             Project: Community Development
>          Issue Type: Bug
>          Components: Reporter Tool
>            Reporter: Sebb
>            Priority: Major
> The entries in projects.json come from scraping the page
> This includes both LDAP groups and auth groups that are defined in the asf-authorization-template
> 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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message