[
https://issues.apache.org/jira/browse/WHIMSY-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075300#comment-16075300
]
Sam Ruby commented on WHIMSY-112:
---------------------------------
Describing how it currently works (as opposed to how it should work):
The view iterates over @committer.committees:
https://github.com/apache/whimsy/blob/5ecb10839fa582eb472db9c31b069d43a5c4803d/www/roster/views/person.js.rb#L30
The server provides this value by calling person.committees:
https://github.com/apache/whimsy/blob/5ecb10839fa582eb472db9c31b069d43a5c4803d/www/roster/models/committer.rb#L58
Which is, indeed, loaded from LDAP:
https://github.com/apache/whimsy/blob/5ecb10839fa582eb472db9c31b069d43a5c4803d/lib/whimsy/asf/ldap.rb#L600
> Board and President's committees not displayed in roster
> --------------------------------------------------------
>
> Key: WHIMSY-112
> URL: https://issues.apache.org/jira/browse/WHIMSY-112
> Project: Whimsy
> Issue Type: Bug
> Components: Roster
> Reporter: Shane Curcuru
>
> Reported by [~clr]
> As above: Board/Pres committees are neither displayed in the roster tool as a
> group (where they fit organizationally better than "PMCs"), and are also not
> displayed for committer/ detail pages.
> I'm guessing new code needs to be added, since the default
> ASF::Committee.pmcs method which is normally called explicitly excludes these
> nonpmcs, or possibly because ldap.rb#L936 only calls LDAP groups?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
