On Tue, Jun 27, 2006 at 08:59:37AM +0200, David N. Welton wrote: > [ Hi, this message doesn't seem to be going through - I'd appreciate it > if you'd forward it on, or quote it in a reply, in the hope that > whatever is causing mail problems sorts itself out today. Thanks! ] > > Justin Erenkrantz wrote: > > >Podlings are, by definition, not yet fully accepted as part of the > >Apache Software Foundation. Therefore, they are subject to additional > > branding constraints. > > >1. The podling MUST be referred to as "Apache <Podling>" > > If you take the 'view from 10000 feet up', this just doesn't clarify > things at all. I think it would be simpler and clearer to not allow > people to utilize the term Apache until the project is fully integrated > into Apache. Starting to use the term 'Apache' also makes it more > difficult for people to back out, which shouldn't actually be a "bad" > thing, nor difficult for them or us.
The issue is that if we don't do that, then there is no tie to Apache when the project graduates. After all, the purpose of Incubation is to establish the Apache-style community. I really think having the podlings use the Apache name is part of the tradeoff we make by opening ourselves up for new projects. If the podling 'fails', then they don't get to use the name. This question came up in our discussions here about Kabuki. Would we permit Zimbra to reuse the Kabuki name? That was an open question that doesn't have a real clear answer. It's a lot clearer if the project refers to itself as "Apache Kabuki" from the beginning. (But, per the suggestion from Susan, we wouldn't call it that until the podling is approved, lists created, and code checked in - which never happened.) My $.02. -- justin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
