Sylvain Wallez wrote:
Thomas Dudziak wrote:
<snip/>
If now for instance, the DB PMC would somehow automatically get the
the incubation mails for the projects that it voted into incubation
and its reports, oversight from this PMC might enhance. After all it
involves more work to actively delete mails than to not get them in
the first place.
And thus potential problems with incubated problems would surface
sooner, and the workload of the Incubator PMC might decrease - one
individual PMC has only a few projects in incubation whereas the
Incubator PMC has to take care of all incubated projects.
Interesting idea. Now forced distribution of emails won't work IMO as
it's easy to delete without actually reading. So a way to ensure
oversight of the originating PMC it to require a status update about
related incubating projects in the quarterly board report.
+1. This is another "well, yes, *obviously* it should be that way" kind
of idea. If the sponsoring PMC isn't taking an active role in the
incubation process, it seems a pretty good chance that things are
getting dropped or confused.
--
Rich Bowen
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
