[
https://issues.apache.org/jira/browse/WHIMSY-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Craig L Russell updated WHIMSY-358:
-----------------------------------
Description:
It should be easy for PMC members to elect new committers and PMC members. The
roster tool already provides for making changes to the PMC roster via simple
push-button. But there is no provision for electing new PMC members or
committers.
The roster for a PMC should provide new buttons to initiate votes, vote, and
close votes. The buttons should only be available to existing PMC members.
To initiate a vote, a new screen allows the nominator to enter the full name,
optional github id, optional apache id, and a paragraph of why this nominee
should become a PMC member or committer. Email is sent to the private list with
a link to the PMC roster so PMC members can vote. All current votes are listed
when PMC members visit the roster page.
To vote, a new screen allows any PMC member to view all comments and to vote.
The vote is recorded in a file keyed on the PMC name and the full name of the
nominee.
To close a vote for a PMC member, a new screen allows the nominator to record
success or failure of the vote. Success for a vote sends email to the board, cc
the PMC list, and starts the 72 hour timer. Expiration of the timer enables a
new button to send email to the nominee with an invitation and a link to click
to finalize the process. When the nominee accepts, a new button appears which
allows any PMC member to finalize the process, update LDAP and
committee-info.txt, and send email to the PMC list.
To close a vote for a new committer, a new screen allows the nominator to
record success or failure of the vote. Success for a vote sends email to the
nominee, cc the PMC list, and invites them to choose an id and submit an ICLA.
The id, email address, project, and full name are already filled in the ICLA
via this process. When the ICLA is received, the normal request for infra to
create an account is processed.
was:
It should be easy for PMC members to elect new committers and PMC members. The
roster tool already provides for making changes to the PMC roster via simple
push-button. But there is no provision for electing new PMC members or
committers.
The roster for a PMC should provide new buttons to initiate votes, vote, and
close votes. The buttons should only be available to existing PMC members.
To initiate a vote, a new screen allows the nominator to enter the full name,
optional github id, optional apache id, and a paragraph of why this nominee
should become a PMC member or committer. Email is sent to the private list with
a link to the PMC roster so PMC members can vote. All current votes are listed
when PMC members visit the roster page.
To vote, a new screen allows any PMC member to view all comments and to vote.
The vote is recorded in a file keyed on the PMC name and the full name of the
nominee.
To close a vote, a new screen allows the nominator to record success or failure
of the vote. Success for a PMC member sends email to the board, cc the PMC
list, and starts the 72 hour timer.
When the 72 hour timer expires, a new button appears which allows any PMC
member to finalize the process, update LDAP and committee-info.txt, and send
email to the PMC list.
> Provide easy way to vote new PMC members and committers
> -------------------------------------------------------
>
> Key: WHIMSY-358
> URL: https://issues.apache.org/jira/browse/WHIMSY-358
> Project: Whimsy
> Issue Type: New Feature
> Components: Roster
> Reporter: Craig L Russell
> Priority: Major
>
> It should be easy for PMC members to elect new committers and PMC members.
> The roster tool already provides for making changes to the PMC roster via
> simple push-button. But there is no provision for electing new PMC members or
> committers.
> The roster for a PMC should provide new buttons to initiate votes, vote, and
> close votes. The buttons should only be available to existing PMC members.
> To initiate a vote, a new screen allows the nominator to enter the full name,
> optional github id, optional apache id, and a paragraph of why this nominee
> should become a PMC member or committer. Email is sent to the private list
> with a link to the PMC roster so PMC members can vote. All current votes are
> listed when PMC members visit the roster page.
> To vote, a new screen allows any PMC member to view all comments and to vote.
> The vote is recorded in a file keyed on the PMC name and the full name of the
> nominee.
> To close a vote for a PMC member, a new screen allows the nominator to record
> success or failure of the vote. Success for a vote sends email to the board,
> cc the PMC list, and starts the 72 hour timer. Expiration of the timer
> enables a new button to send email to the nominee with an invitation and a
> link to click to finalize the process. When the nominee accepts, a new button
> appears which allows any PMC member to finalize the process, update LDAP and
> committee-info.txt, and send email to the PMC list.
> To close a vote for a new committer, a new screen allows the nominator to
> record success or failure of the vote. Success for a vote sends email to the
> nominee, cc the PMC list, and invites them to choose an id and submit an
> ICLA. The id, email address, project, and full name are already filled in the
> ICLA via this process. When the ICLA is received, the normal request for
> infra to create an account is processed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
