[
https://issues.apache.org/jira/browse/WHIMSY-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17840520#comment-17840520
]
Shane Curcuru commented on WHIMSY-414:
--------------------------------------
Agreed: each PMC's roll calls should only be accessible by that PMC by default
(and all Members as well per usual policy). This is data the board needs quick
and simple access to, because the board is evaluating project health; but it's
not something we otherwise should be providing access to.
Any potential workflow should also store:
* Director leading the roll call
* date started / date expected to be finished (commits are fine after that
date, but having a report on what was done before the X days deadline is useful)
* (bonus) paragraph of what the Director writes as to why the board is asking
for a roll call, so we can store at least some hand-written explanation of why
this was done at that time.
> Roll call tool to simplify PMC roll calls
> -----------------------------------------
>
> Key: WHIMSY-414
> URL: https://issues.apache.org/jira/browse/WHIMSY-414
> Project: Whimsy
> Issue Type: New Feature
> Components: Roster
> Reporter: Craig L Russell
> Priority: Major
>
> During review of project board reports, directors encounter projects that
> seem to be in decline. In order to determine whether the PMC is healthy
> enough for proper oversight, the board requests a roll call and assigns an
> action item to a director.
> To start the roll call, a director goes to the Whimsy roster page for the
> PMC, and clicks "send roll call". Director writes out an explanation of any
> specific board concerns, which is then sent out along with a boilerplate
> explanation of the roll call process, along with a "reply by this date to
> roll call here" link.
> PMC members click the link (which auth's them), fill out short form, and
> click submit. The board really needs to know the "how engaged are you"
> detail, and we could also have an extra comments field where PMC members
> might add extra data.
> Every submission results in a commit (by Whimsy) into a private repository
> (visible to Members and Officers) as well as an email to board@ and
> private@<project>. The repository should be easy to search by name by
> logged-in users, e.g.
> [https://svn.apache.org/repos/private/pmc/<project>/|https://svn.apache.org/repos/private/pmc/]roll-call/2024-04-01/<apache-id>.json.
>
> The above directory will be created at the time the roll call request is
> being executed. The private/pmc/<project>/ directory might need to be created
> by Whimsy if no roll call or other reason has been seen for this PMC.
>
> PMC members should be allowed to save their responses in a specific roll call
> request directory
> PMC members should be allowed to review/read responses from their peers in
> any of their svn project roll call directories
> Members and Officers should be allowed to review/read responses from any of
> the repositories
> Other access should be disallowed
> It's easy to track responses by Apache ID, and by date of response, as well
> as have a simple read-only dashboard showing the outcome of each roll call,
> assuming the right privileges.
> PMC members could also see each others' responses in email.
> Working example (you will be auth'd by your Apache ID):
> [https://whimsy.apache.org/officers/surveys?survey=test-rollcall.json]
> In this POC, commits go to foundation/officers/surveys.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
