On Aug 31, 2005, at 2:01 PM, Cliff Schmidt wrote:
- change the Incubator PMC charter (not that we have a official charter) to include approving of all new projects, so that once a sponsor PMC (if not the Incubator PMC) approves a new project, the Incubator PMC still has to give a final approval.
+1
- ensure all proposals use the same standard template -- we've recently gotten proposals that simply copied some other proposal they saw -- we're not really making sure that any one set of standard questions is answered.
+1
- add a question to the template asking whether the person(s) proposing are aware of similar open source projects inside or outside the ASF. I'm not suggesting that a project wouldn't get approved if there is some similar high profile open source project, but at least we are explicitly asking the question and getting the information.
Sure, why not.
- consider having a formal liaison at a few key external open source communities to give a friendly notice to whenever the Incubator PMC knows there's a proposal that could be controversial. This really only works if we add the new proposal question mentioned above and create a more centralized process of looping the Incubator PMC in *before* a project is approved.
-1
- require that the Incubator PMC loops in the PRC on any project that could have any chance of media attention (either because of the overall significance of the project, the potential for controversy, expected vendor press releases, or the opportunity to release a joint statement with some other organization).
I think, instead, that podlings should be prevented from doing any PR without checking with the PRC. That is, it isn't an Incubator responsibility, but a PPMC one. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
