[
https://issues.apache.org/jira/browse/WHIMSY-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16084831#comment-16084831
]
Christopher Tubbs commented on WHIMSY-116:
------------------------------------------
[[email protected]], I intentionally did not elaborate on what I tried and what
did or did not work, because that's not the point of this issue and I don't
want to distract from the core issue, which is that there is a documentation
mismatch with respect to what tooling should be used, and how it should be
used. It was filed here, under the "roster" component, because I think the
folks maintaining that are best capable of updating the documentation
accurately, based on how Whimsy is supposed to be used for maintaining rosters.
However, since you asked, I will elaborate a bit:
I tried to go to the roster tool, and thought I'd be able to add a PMC member
there: https://whimsy.apache.org/roster/committee/accumulo
I was able to do this for a PPMC: https://whimsy.apache.org/roster/ppmc/fluo
and expected similar functionality as a PMC member of Accumulo.
However, I did not have any options to update anything there. It is probably
restricted to only PMC Chairs for TLPs, and any PPMC member for Podlings.
However, the scripts used to (and still do) allow other PMC members (maybe just
ASF members?) to perform this on behalf of the PMC Chair if they are not
available. Most of what is described on http://www.apache.org/dev/pmc.html can
be satisfied by another PMC member if the Chair is not available, such as
notifying the board of a proposed new PMC member, submitting board reports,
other PMC members can update committee-info.txt, etc. Since this was possible
from the scripts, I assumed that this might also be possible at some point with
Whimsy.
Having used Whimsy to update the PPMC for a podling before, I'm aware of the
lack of a feature to remove individuals, once added (a feature in the scripts
for regular LDAP groups). From that experience, I know that Whimsy does not
have all the features of the scripts, but do not know which will be added, and
which will remain omitted.
At this point, all I know is that it did not work for me. It may work perfectly
as intended for PMC Chairs. Functionality may be added in the future to allow
other PMC members to use certain features, and ASF Members. I cannot say. What
I do know right now, is that I have no idea what the process should look like
when it works, because it did not work for me, and it is not documented in the
places where updating rosters is described in ASF documentation.
> Update documentation to add new PMC member
> ------------------------------------------
>
> Key: WHIMSY-116
> URL: https://issues.apache.org/jira/browse/WHIMSY-116
> Project: Whimsy
> Issue Type: Task
> Components: Roster
> Reporter: Christopher Tubbs
>
> I tried to use Whimsy to add a new PMC member, but wasn't able to get it to
> work. I'm a PMC member and an ASF Member, and was performing this because our
> PMC chair was not immediately available (and also I wanted to learn the
> process).
> So, I followed the old procedure of updating committee-info.txt with SVN (is
> that still necessary with Whimsy? It's not clear.) and manually running the
> ldap scripts, as described on http://www.apache.org/dev/pmc.html
> However, that page seems out of date. It does not describe the correct way to
> do it with Whimsy, and the instructions for using the ldap scripts no longer
> work, because the scripts have been "disabled" with a message to use Whimsy.
> (FWIW, I ended up copying the scripts, and commenting out the "exit" line
> which disabled them. The scripts should probably not be disabled unless
> Whimsy works in all cases, and should probably remain available as a backup
> when Whimsy fails.)
> The purpose of this issue is to fix the outdated documentation at
> http://www.apache.org/dev/pmc.html (assuming Whimsy is working 100%) or to
> restore the currently documented functionality.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
