community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <seb...@gmail.com>
Subject Re: [reporter] Confusing PMC/Committeer/Committee/LDAP report format
Date Thu, 22 Oct 2015 10:38:08 GMT
On 22 October 2015 at 11:29, Tony Stevenson <tony@pc-tony.com> wrote:
>
> On Thu, 22 Oct 2015, at 11:17 AM, sebb wrote:
>
>> The LDAP group is used for granting karma, not for determining PMC
>> membership.
>
> That is simply not necessarily true Sebb.

What is not true?
The LDAP committee group is definitely used for determining karma.
It is used for granting access to the PMC-private area of SVN and by
default to give write access to the dist/release areas.

And PMC membership is defined by the committee-info.txt file.

> There are two LDAP groups per
> TLP/PMC.  ou=groups,cn=httpd   and  ou=pmc,ou=groups,cn=httpd - there
> are even groups that do no represent a TLP/PMC in the same OU.

True but not really relevant here.

> PMC chairs are told to add new PMC members to the PMC group, while new
> committers (where a TLP does not operate that a committer is not also a
> PMC member (ala Subversion)) are only added to the 'Unix' group.

Again true but not relevant here

> This is in fairness a carry over from the old minotaur days.  The former
> was known as the PMC unix group, and the latter was a group created to
> define the PMC membership.

As I recall, the PMC groups were created to grant access to the
PMC-private areas of SVN, not to define the PMC membership.
At the time, the definitive record of PMC membership was the board
reports and ACK mails on the board list.

> You should never a group either defines, or does not define access
> control.

Cannot parse that last sentence.

Mime
View raw message