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

Sebb commented on WHIMSY-270:
-----------------------------

[~rubys] I was thinking the same.

[~cml] I think this needs a bit more study.
I think it's vital that each nonPMC only has one LDAP group, otherwise the 
groups can get out of step.
At present some of the nonPMC groups use ou=auth (e.g. fundraising, trademarks)
Presumably there was a good reason for choosing ou=auth.
We should not change the LDAP schema just because it makes coding easier; seems 
to me that the correct schema is more important.

> non-PMC groups need to be treated as projects
> ---------------------------------------------
>
>                 Key: WHIMSY-270
>                 URL: https://issues.apache.org/jira/browse/WHIMSY-270
>             Project: Whimsy
>          Issue Type: New Feature
>            Reporter: Chris Lambertus
>            Priority: Major
>
> For groups such as D&I or others under 
> https://whimsy.apache.org/roster/nonpmc/ there should be the ability to 
> "press the button" to create and maintain the LDAP groups under ou=project. 
> This will provide the following benefits:
> - allow LDAP management of the nonPMC
> - allow self-service github repo creation
> - allow proper github authorization for repos
> I am not aware of any downsides for this approach. I have not reviewed the 
> code, but I am hoping it would be fairly trivial to implement, and would 
> quickly unblock INFRA-18453.
> The current state of affairs would require infra to manually create and 
> populate the LDAP group for D&I, which we'd prefer to avoid.



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

Reply via email to