incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dave Fisher <>
Subject Re: Reporting due dates
Date Fri, 02 Aug 2013 23:48:48 GMT
Hi Marvin,

It would be good to get shepherd assignments. I have some travel coming ...


On Aug 2, 2013, at 2:33 PM, Marvin Humphrey wrote:

> Greets,
> "Marvin" sent out report reminders earlier today.  Here's my proposed timeline
> for preparing our August report:
>    Wed August 7 -- Podling reports due by end of day
>    Tue August 13 -- Mentor signoff due by end of day
>    Tue August 13 -- Shepherd reviews due by end of day
>    Tue August 13 -- Summary due by end of day
>    Wed August 14 -- IPMC Chair submits report (on time!)
>    Wed August 21 -- Board meeting
> Note that this month's schedule differs from the one I laid out for our July
> report, primarily because of a mistake I made last month -- I had thought that
> "Marvin" gave podlings a week and a half to submit their reports rather than
> only five days.  This time I'm proposing that we adhere to Marvin's compressed
> schedule -- so podling reports are due in less than a week.
> In the future, I would like to send out podling reminders one week earlier.
> That way, podlings will get the same amount of time that TLPs get, while still
> allowing the IPMC several days for Mentor signoff and Shepherd review before
> the Chair submits the report -- on time for a change, instead of a couple days
> late as has been the Incubator's bad habit.
> I believe that changing the timing for reminders will require modifications to
> the script (a.k.a. "Marvin"), which is tricky because it looks
> like it's hard to run without actually sending email.
> What I'm tempted to do is refactor some of the code in into a
> handful of modules which can be run in non-production mode, making it
> possible to write some tests and make changes with greater confidence.
> Although this would be a fair amount of work, it's probably less in the long run
> than making blind, untestable changes to the current monolithic script and
> then cleaning up the huge mess when things go wrong (e.g. because every TLP
> receives a reminder with the wrong date).
> Thoughts?
> Marvin Humphrey
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message