Craig Russell wrote: > Robert Burrell Donkin wrote: > > A practical problem with this approach is that reports are submitted > > right up to the deadline
> I'm not sure I understand your point. The deadline is the Wednesday a
> week ahead of the board meeting.
I believe that Robert was pointing out that the reality (aka, the
practical problem) is that people are submitting right up to the (board)
deadline, and not getting them in when we've asked for them.
> I think that mentors have the responsibility to create a report on
> behalf of the podlings to start. Yes, it's all on them. After a few
> reports, the mentor gets the community to step up and create the
> reports. The mentor then just needs to monitor things and step in if
> things don't get done.
This depends on what you mean by responsible. Unless the Mentor is going
to be the PMC Chair, the Community had better start getting it done. We
may consider the Mentor to be responsible to the PMC, but I think that it
would be fair for the Mentor to be responsible for saying *something*,
even if just to say that the Community is not meeting its responsibility
of getting a proper report done. And in that case, we'd consider it as if
they had missed the report, and start to consider appropriate and
corrective action.
> Perhaps the missing link is a reminder
Volunteers for the automation task?
--- Noel
smime.p7s
Description: S/MIME cryptographic signature
