infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gavin (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (INFRA-16193) Issues with mail-private
Date Sun, 25 Mar 2018 23:57:00 GMT

     [ https://issues.apache.org/jira/browse/INFRA-16193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gavin closed INFRA-16193.
-------------------------

I'd rather we didnt create a meta ticket and keep re-opening this ticket.
Each new thing you find is a separate job, that takes time to investigate and resolve.

I'll create two new tickets from your latest findings.

> Issues with mail-private
> ------------------------
>
>                 Key: INFRA-16193
>                 URL: https://issues.apache.org/jira/browse/INFRA-16193
>             Project: Infrastructure
>          Issue Type: Improvement
>          Components: Mail Archives
>            Reporter: Sebb
>            Assignee: Gavin
>            Priority: Major
>
> Not all PMCs have ou=pmc LDAP groups any more. E.g. PMC members of jmeter and whimsy
cannot access the pmc archives.
> The members of such groups are only in the ou=projects LDAP group. However this also
includes podlings.
> One way to fix the permissions issue would be to allow PPMC members to access their lists.
This would mean that the ou=projects LDAP group could be used for both the list of (P)PMCs
and their members. A few names would need to be adjusted (e.g. httpcomponents==hc; whimsy)
but it should be relatively simple to convert between directory name and LDAP group.
> The PMC drop-down list should only include (P)PMC-related lists.
> It should not include lists that are inaccessible to PMC members such as apachecon and
other private lists.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message