On Tue, May 12, 2009 at 3:55 PM, Bernd Fondermann < bernd.fonderm...@googlemail.com> wrote:
What I don't get is why would anyone want to keep the name if there > are potential overlaps or troubles ahead? > I mean, there are probably better (coding) and harder (releasing, > graduating) things to do than getting stuck about the name. > Why don't you (as a podling) simply move on with another cool name, > for example, just brainstorming here... "JSecurity"... or something > similar? JSecurity was deemed as a potential naming conflict risk (much in the same way Ki is now), so we dropped it, and finally came to a vote to change the name to Ki. But this resolution took over 4 or 5 months to finally come to a favorable vote, so we didn't want to go through that painful process all over again, since it seemed like no one was willing to come to consensus on other names. It is very difficult to find an even remotely-correlated name in the security space that might not infringe on another site/company/product/trademark/patent. Given the difficulty and the enormous amount of time spent already, we just wanted to move on to focus exactly on the things you mention, and only worry about changing the name yet again if it was absolutely required by the Incubator to do so. That being said, if the Incubator says "the Ki podling must change its name", then fine, we'll be happy to do so, but most of us didn't want to spend the effort worrying about it unless necessary. Regards, Les
