On Wed, Aug 9, 2017 at 5:36 AM, sebb wrote:
> On 8 August 2017 at 13:09, Sam Ruby wrote:
>> The only use I recall for adding podlings to asf-auth was to have this
>> information show up in the apache phone book. These asf-auth entries
>> should be deleted (and the phone book should be updated, i
On Wed, Aug 9, 2017 at 7:31 AM, sebb wrote:
> Is this used?
> How is it maintained?
>
> dn: cn=podlings,ou=groups,dc=apache,dc=org
> cn: podlings
> creatorsName: uid=rubys,ou=people,dc=apache,dc=org
> createTimestamp: 20161221015843Z
> modifiersName: uid=rubys,ou=people,dc=apache,dc=org
> modifyTi
On Wed, Aug 9, 2017 at 7:36 AM, sebb wrote:
> The following are only in LDAP groups
> apsite
> committers
> concom
> infra
> member
> podlings
> security
>
> I think we'll probably need to keep these
TL;DR: I'd like to get rid of those.
Apsite is unused/unmaintained, and should be dropped.
Podl
The LDAP group ou=projects is used for PMCs and podlings. Possibly
other types as well.
Apps that read the file usually need to know if an entry is a PMC or a
podling or something else.
At present that means they also have to read other JSON files.
This is extra code to write and test.
It seems
The following are only in LDAP groups
apsite
committers
concom
infra
member
podlings
security
I think we'll probably need to keep these
The following are only in LDAP committees
tac
It would be tedious if LDAP committees had to be kept just to support tac
Is this used?
How is it maintained?
dn: cn=podlings,ou=groups,dc=apache,dc=org
cn: podlings
creatorsName: uid=rubys,ou=people,dc=apache,dc=org
createTimestamp: 20161221015843Z
modifiersName: uid=rubys,ou=people,dc=apache,dc=org
modifyTimestamp: 20170802021104Z
subschemaSubentry: cn=Subschema
hasSu
On 8 August 2017 at 13:09, Sam Ruby wrote:
> The only use I recall for adding podlings to asf-auth was to have this
> information show up in the apache phone book. These asf-auth entries
> should be deleted (and the phone book should be updated, if necessary,
> to no longer look for this informat
