[ 
https://issues.apache.org/jira/browse/WHIMSY-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16843487#comment-16843487
 ] 

Shane Curcuru commented on WHIMSY-264:
--------------------------------------

Color me corrected!  (embarrassed grin) I guess simply ensuring Agenda parsing 
(as may be used by other tools, or minutes sectioning) does something useful 
for F2F minutes/agendas is all we need.

> Agenda handling of F2F agenda/minutes
> -------------------------------------
>
>                 Key: WHIMSY-264
>                 URL: https://issues.apache.org/jira/browse/WHIMSY-264
>             Project: Whimsy
>          Issue Type: Improvement
>          Components: BoardAgenda
>            Reporter: Shane Curcuru
>            Priority: Minor
>
> Adding partial support for handing F2F meeting agendas and minutes thereof 
> would be helpful.
>  * Detect a F2F meeting and display a simplified agenda
>  * No preapprovals or shepherds needed; traditional officer reports may not 
> be present; PMC reports will *not* be present
>  * Having Whimsy *display* either the agenda (Before meeting) or minutes 
> (afterwards) would be very useful; we do not particularly need 
> queue/shepherd/running through items features, since at a F2F we often work 
> differently than traditional telecons.
>  * *Important:* F2F agendas should *only* ever be managed in /foundation 
> private repo.  Any post-meeting tasks or publishing minutes must 
> *definitively not* publish F2F publicly (if it turns out we do publish 
> publicly, we can do that manually).
>  * But would be useful: displaying F2F minutes as a past set of minutes for 
> board approval.  That is, the board should approve any prior F2F minutes, and 
> then publish *only* to /foundation repo privately.
> Suggested special case trigger, item 3., if "Schedule", then F2F.
> This is important to document (even if we don't fully implement) before the 
> next monthly board meeting.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to