Paul Fremantle wrote:
So here is a suggestion. Each incubator project could have nominated two or three PMC members whose job is to pay attention to the project. As opposed to a mentor - who is there to actively help, these PMC members would be there to pay enough attention to have an input on releases, status and graduation. They wouldn't need to be involved in the technical aspects of the project. The focus would be on understanding whether the project got the Apache way - votes, releases, community. To use a trendy word - governance.
I'm not quite certain how you separate these aspects? I've personally only voted on releases that I have time to unpack, grep for typical language that reflects an ASF incubating project as opposed to it's original origins, etc etc. If I can't do that, I can't +1 the release. I think it does much more damage if release after release is blindly +1'ed, and the project gets a brick wall upon it's graduate-from-incubator vote for entirely reasonable issues that weren't observed by the reviewers before. So I'd caution against designated release managers. One fun thing might be to add pending packages for review in the incubator's DOAP file, so more members could watch release activity via rss without being lost in the general drone of general@ discussion. A red letter day rss feed. Bill --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
