On 20 October 2011 09:26, Daniel Shahaf <d...@daniel.shahaf.name> wrote: > David Crossley wrote on Thu, Oct 20, 2011 at 19:00:58 +1100: >> This reporting stuff is getting harder to manually manage. >> We now have sixty (yes 60) podlings currently in incubation. >> >> Can anyone see a way to improve this process?
Maybe we can extend podlings.xml with a reporting section. This would need to define which quarterly shedule to use for each podling. It could also have a "monthly" override flag with an end-date. This would work for both initial monthly reporting, and potentially for monthly exit reporting (there was some talk of requiring monthly reporing for projects nearly ready to graduate) - just set a date far into the future. If the end-date was omitted, it could be derived from the project start date. I think this data would generally only need to be set once, and everything could be generated from it. However, at present the Reporting Schedule does act as a cross-check of podlings.xml. Would it matter if this cross-check were lost? > Isn't it a solved problem? The board does *something* to manage > quarterly report from the ~100 PMCs it has... That something is committee-info.txt. However, that only sends e-mails to the PMC chair, which is not entirely suitable here. > --------------------------------------------------------------------- > 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
