From general-return-22032-apmail-incubator-general-archive=incubator.apache.org@incubator.apache.org Tue May 12 21:00:34 2009 Return-Path: Delivered-To: apmail-incubator-general-archive@www.apache.org Received: (qmail 33856 invoked from network); 12 May 2009 21:00:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 12 May 2009 21:00:29 -0000 Received: (qmail 15187 invoked by uid 500); 12 May 2009 21:00:28 -0000 Delivered-To: apmail-incubator-general-archive@incubator.apache.org Received: (qmail 15006 invoked by uid 500); 12 May 2009 21:00:28 -0000 Mailing-List: contact general-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@incubator.apache.org Delivered-To: mailing list general@incubator.apache.org Received: (qmail 14992 invoked by uid 99); 12 May 2009 21:00:28 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 May 2009 21:00:28 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [209.85.217.225] (HELO mail-gx0-f225.google.com) (209.85.217.225) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 May 2009 21:00:18 +0000 Received: by gxk25 with SMTP id 25so193068gxk.12 for ; Tue, 12 May 2009 13:59:35 -0700 (PDT) MIME-Version: 1.0 Sender: les.hazlewood@anjinllc.com Received: by 10.90.69.15 with SMTP id r15mr79478aga.90.1242161946316; Tue, 12 May 2009 13:59:06 -0700 (PDT) In-Reply-To: <88f6e29a0905121255pd80b1fcq253ed268ace9d85b@mail.gmail.com> References: <8EB750A4-D2B1-4C7C-8888-776A398D691D@toolazydogs.com> <08CB8E49-E904-4C1D-89EE-AE36D8CF6468@toolazydogs.com> <652137D2-60D8-4309-B9C2-0E204F94BC83@SUN.com> <88f6e29a0905121255pd80b1fcq253ed268ace9d85b@mail.gmail.com> Date: Tue, 12 May 2009 16:58:59 -0400 X-Google-Sender-Auth: e9c6ac4c99cb4801 Message-ID: <44b57a610905121358y23c07559nfa582596760bae0b@mail.gmail.com> Subject: Re: This problem of mine From: Les Hazlewood To: general@incubator.apache.org Content-Type: multipart/alternative; boundary=0016364ee1e49059460469bd5ddc X-Virus-Checked: Checked by ClamAV on apache.org --0016364ee1e49059460469bd5ddc Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit On Tue, May 12, 2009 at 3:55 PM, Bernd Fondermann < bernd.fondermann@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 --0016364ee1e49059460469bd5ddc--