[
https://issues.apache.org/jira/browse/WHIMSY-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16739263#comment-16739263
]
Sebb commented on WHIMSY-232:
-----------------------------
There are several other non-PMC (i.e. Board or President's) Committees which
are listed in committee-info.txt
For example:
Brand Management, Fundraising, Security, Travel Assistance - all have teams
listed in CI
Conferences, Data Privacy, Finance, Marketing and Publicity - only a chair is
noted in CI
==
I've just discovered that the ones with LDAP groups do appear under
roster/committee/name.
However they are not listed in the roster/committee index.
Also the committee pages use the heading 'PMC' for the entries in CI.
Further, there is a marker against the chair if they don't happen to be in
pmc-chairs.
This is confusing.
I think it would make sense to create a separate roster section, with its own
index, for the non-PMC committees.
[Probably does not make sense to separate the Board Committees from the
President's Committees]
[Might also make sense to have a separate (read-only) section for Officers]
> Allow whimsy roster tool to manage Legal Committee
> --------------------------------------------------
>
> Key: WHIMSY-232
> URL: https://issues.apache.org/jira/browse/WHIMSY-232
> Project: Whimsy
> Issue Type: New Feature
> Reporter: Roman Shaposhnik
> Priority: Major
>
> Following up from https://issues.apache.org/jira/browse/INFRA-17288
> As per Sam's comments: the whimsy roster tool doesn't particularly care
> whether the data is in SVN (e.g. committee-info.txt) or LDAP. SVN has
> superior tracking and version control. LDAP can be directly used to control
> access to resources (e.g. SVN repositories).
> It would be great if Whimsy can start using committee-info.txt for managing
> Legal Committee the way it does for all the other PMCs
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
