Forwarding an exerpt of one of my answer to Richard reply. I really think it's worth discussing it anyway.
Most of the TLP I know about that have subprojects usually refer to those subprojects as Apache Foo and not Apache Bar Foo. So this would mean Apache iPojo and not Apache Felix iPojo, ditto for other subprojects. I also think the "branding" problem should be addressed (if possible) by renaming either the framework or the TLP. It looks to me that renaming the TLP (even if I think would better) might be more difficult to achieve from an infra pov, but I may be wrong (I know there are some tools for migrating mailing lists and such, so it might not be so difficult). I'd like to hear other's thoughts. ---------- Forwarded message ---------- From: Guillaume Nodet <gno...@gmail.com> Date: Tue, Sep 1, 2009 at 17:45 Subject: Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi To: gene...@incubator.apache.org The problem I have with Felix is really a branding problem. While *we* (as developers) very well know that all the subprojects of Felix are not tied to the Felix Framework itself, it's really difficult to spread this word around to non techies. The name Felix is often associated to the OSGi framework implementation itself, and it's kinda hard to remove this tie unless either the project or the framework change its name to something else. For example, the framework could be referred to as Apache Foo and other subprojects as Apache iPojo or Apache Karaf. I think it would help removing this tie. The other way around is possible too, rename the project to something else, and keep Apache Felix as referring to the framework itself (which might be even better, but slightly more difficult to actually achieve). I'm not sure there is a very easy way, but d...@felix.a.o would a better place to discuss that. -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
