[
https://issues.apache.org/jira/browse/COMDEV-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962341#comment-14962341
]
Sebb commented on COMDEV-174:
-----------------------------
Going forward, it would be better to ignore committer-index.html and use the
LDAP groups directly.
(There is some work in progress to do this)
There would then be no ambiguity regarding podling unix groups.
[Note that the LDAP pmc group does not exist for podlings]
> 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)
