[
https://issues.apache.org/jira/browse/WHIMSY-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16853937#comment-16853937
]
Sebb commented on WHIMSY-270:
-----------------------------
The nonPMC list is derived from section 1 -- Board Committees and President's
Committees - of committee-info.txt
Not all of these have entries in section 3.
As it happens, the ones that have ou=project LDAP also have entries in section
3, so Whimsy is able to edit committee-info.txt.
This will need to be addressed in Whimsy and/or CI if further committees are
moved to ou=project LDAP.
> 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)
