Hi Justin,

I can help, just let me know the tasks you want me to do.

Thanks,
Regards
JB

On Thu, May 12, 2022 at 9:15 AM Justin Mclean <jus...@classsoftware.com> wrote:
>
> Hi,
>
> As noted here [2] the board report should not be the sole responsibility of 
> the chair to put together.
>
> Here's what is roughly needed for each board report.
>
> After the board meeting:
> - Update podlings.xml to mark podling that did not report, ones whose report 
> was missing but reported and podlings at the end of their monthly reporting 
> period
> - assign podling shepherds using assign_shepherds.py
> - run clutch script (./clutch2.sh) and generate report 
> template(clutch2report.py)
> - Update wiki report page to have correct podling listed (may need to remove 
> graduated and retired podlings and add new podlings)
> - Add any new PPMCs to the wiki so they can edit their report
> - Send out email containing list of podlings to report and dates
>
> During the month:
> - Send out 2 or 3 reminders using report_reminders.py
>
> Before the report is due:
> - Write a summary of what has happened on the mailing list with anything of 
> interest
> - List all releases made during the month /  check if incubator votes match 
> with what’s in the release area
> - List who been added/removed to IPMC during the month
> - Check that PPMC members have been added correctly
> - Remove the non-reporting podlings sections from the report and note them as 
> not reporting
> - Note any podlings that didn’t get mentor sign off
> - Reflow the report and fix the report formatting including remove text 
> prompts for mentor activity and branding questions
> - Lock the wiki page so it can’t be edited
> - Send email to this list for review
> - Submit the report to the board
>
> If anyone would like to do any of these tasks just ask. If you need more 
> detail on how to do them just ask. The report run book report_reminders.py 
> and these pages [1][2] can also help. If no one volunteers then I’ll do them. 
> I’ll also check the report’s format and details if we do get volunteers.
>
> One thing it might be useful to look into is to see if we can automate 
> sending out the reminders each month rather than having it as a manual task.
>
> Kind Regards,
> Justin
>
> 1. https://cwiki.apache.org/confluence/display/INCUBATOR
> 2. https://incubator.apache.org/guides/chair.html#board_report
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Reply via email to