[jira] [Comment Edited] (INFRA-9942) Allow reporter.apache.org access to committee-info.txt

["Sebb (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/INFRA-9942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14621516#comment-14621516 ] 

Sebb edited comment on INFRA-9942 at 7/11/15 12:11 AM:
-------------------------------------------------------

The scripts for people.apache.org use the role 'apsiteread' which gives read access to asf-authorization etc. It would actually be useful for people to have access to committee-info.txt as well.

If access were granted to apsiteread then this could be used for reporter.apache.org and projects-new.apache.org as well.

This does not require setting up any new role accounts (just a simple change to [/committers/board] in pit-auth) Note that rptremind already has read access to this directory.


was (Author: sebb@apache.org):
The scripts for people.apache.org use the role 'apsite' which gives read access to asf-authorization etc. It would actually be useful for people to have access to committee-info.txt as well.

If access were granted to apsite then this could be used for reporter.apache.org and projects-new.apache.org as well.

This does not require setting up any new role accounts (just a simple change to [/committers/board] in pit-auth) Note that rptremind already has read access to this directory.

> Allow reporter.apache.org access to committee-info.txt
> ------------------------------------------------------
>
>                 Key: INFRA-9942
>                 URL: https://issues.apache.org/jira/browse/INFRA-9942
>             Project: Infrastructure
>          Issue Type: Wish
>            Reporter: Sebb
>
> At present, reporter.apache.org has no access to committee-info.txt (CI), so it cannot access the canonical source of information for committee membership and joining dates etc.
> Instead, it assumes that changes to the LDAP committee groups are synchronised with CI. This is often not the case, so the generated information can be inaccurate. [For example, LDAP may be updated days before or after CI or not at all]
> It would be very useful to give read-only access to CI.
> As far as I can tell, the file does not contain any sensitive information.
> Also the file is RW to all ASF committers anyway and reporter.apache.org requires a valid login.
> Possible options:
> - a role account for reporter.apache.org with RO access to the file
> - make the file world readable



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)