Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 35327 invoked from network); 28 Apr 2006 15:30:24 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 28 Apr 2006 15:30:24 -0000 Received: (qmail 13188 invoked by uid 500); 28 Apr 2006 15:30:22 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 12921 invoked by uid 500); 28 Apr 2006 15:30:21 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 12909 invoked by uid 99); 28 Apr 2006 15:30:20 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Apr 2006 08:30:20 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of flamefew@gmail.com designates 64.233.166.179 as permitted sender) Received: from [64.233.166.179] (HELO pproxy.gmail.com) (64.233.166.179) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Apr 2006 08:30:20 -0700 Received: by pproxy.gmail.com with SMTP id t32so2244298pyc for ; Fri, 28 Apr 2006 08:29:59 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=lT78xKdESi8DYhST98tBB+cOQn4DuZX8CCIdKWW/9vagldkjThIwF/WztbTSTpPFpEeEg+2CaCGQ4v9Rz7ZPMB4B/sLiItD5rMuW7sCIQY8EtDToi+zvL2HbaS7oN7E4Sxy8xX8MDiQgFI2HxvIF23CDvcMpXu2qC1XhW6Yrx7Y= Received: by 10.35.77.18 with SMTP id e18mr1526803pyl; Fri, 28 Apr 2006 08:29:59 -0700 (PDT) Received: by 10.35.22.15 with HTTP; Fri, 28 Apr 2006 08:29:59 -0700 (PDT) Message-ID: <31cc37360604280829t666e034fm1325facba120b6da@mail.gmail.com> Date: Fri, 28 Apr 2006 08:29:59 -0700 From: "Henri Yandell" To: "Jakarta Commons Developers List" Subject: Re: Jira id naming convention for Jakarta projects; WAS Re: [all] Jira? In-Reply-To: <4451CC25.1060201@apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <31cc37360604252145g1c82264amfc0a30ce6de59e94@mail.gmail.com> <31cc37360604271356q666e4e72o48780ccb055e9554@mail.gmail.com> <4451533E.6090004@btopenworld.com> <31cc37360604271706g5f84e12ap8bff69e945a14009@mail.gmail.com> <4451CC25.1060201@apache.org> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On 4/28/06, Oleg Kalnichevski wrote: > I also find JHCHTTPCORE absolutely horrible. I chose this id as I > thought it would be the most "politically correct" one. I would very > much rather prefer HTTPCORE or JHTTPCORE. Do you envisage a particular > Jira id naming convention for Jakarta projects? At this point it is > still not too late for us to scrap the project and start over with a > different (better) project id. I don't think it's important to have a scheme - it's just a project id that is used in such a way that users are aware of it. HCO, HTCO, JHTC. Doesn't matter and I agree with the Atlassian advice on it being a 3 or 4 letter code. So: LANG IO COLL CODX (though tempting to go with 5 letters when it fits, CODEC etc) ATTR BEAN etc. Dunno if that matches with the infra@ view. Having something with 11 letters is a pain in the arse given that the only time I ever find myself using the id is: a) to discuss something outside of Jira and b) to enter into the find box in the top right. Hen --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org