Return-Path: Delivered-To: apmail-jakarta-httpcomponents-dev-archive@www.apache.org Received: (qmail 39573 invoked from network); 13 Dec 2006 00:07:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 13 Dec 2006 00:07:33 -0000 Received: (qmail 42891 invoked by uid 500); 13 Dec 2006 00:07:40 -0000 Delivered-To: apmail-jakarta-httpcomponents-dev-archive@jakarta.apache.org Received: (qmail 42873 invoked by uid 500); 13 Dec 2006 00:07:40 -0000 Mailing-List: contact httpcomponents-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "HttpComponents Project" Delivered-To: mailing list httpcomponents-dev@jakarta.apache.org Received: (qmail 42864 invoked by uid 99); 13 Dec 2006 00:07:40 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Dec 2006 16:07:40 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of mbecke@gmail.com designates 66.249.82.230 as permitted sender) Received: from [66.249.82.230] (HELO wx-out-0506.google.com) (66.249.82.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Dec 2006 16:07:30 -0800 Received: by wx-out-0506.google.com with SMTP id h27so8096wxd for ; Tue, 12 Dec 2006 16:07:10 -0800 (PST) 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=GtBmv9p9qiyXT9FEenu8X5+Bo8o5DHB3ZgVcx77KMZaDAQPFyo8K6oMZyL6lXD9HclzT+V947NCmUNCfBUQ9ow86MwSFKmxVyrau5OzguDDMBnhmTAxxUbhjBxwk7Z1C8Mz0TQFev3E8SnQ5ZITaRCz+p8EPqcnk2PorUylsqRQ= Received: by 10.70.125.2 with SMTP id x2mr342055wxc.1165968429991; Tue, 12 Dec 2006 16:07:09 -0800 (PST) Received: by 10.70.26.11 with HTTP; Tue, 12 Dec 2006 16:07:09 -0800 (PST) Message-ID: <78f7873e0612121607k5790d6a5q8c544274e0b7fd70@mail.gmail.com> Date: Tue, 12 Dec 2006 16:07:09 -0800 From: "Michael Becke" To: "HttpComponents Project" Subject: Re: The use of @author tag policy revisited In-Reply-To: <1165922285.11778.24.camel@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20061208205944.290C11A9846@eris.apache.org> <457A50C7.5080905@dubioso.net> <1165694804.5092.38.camel@localhost.localdomain> <457BE4F4.8000208@dubioso.net> <457C9359.2060904@odi.ch> <25aac9fc0612110754r4c7f3dcdubdb4ab2bed34b505@mail.gmail.com> <1165922285.11778.24.camel@localhost.localdomain> X-Virus-Checked: Checked by ClamAV on apache.org Works for me. Mike On 12/12/06, Oleg Kalnichevski wrote: > On Mon, 2006-12-11 at 15:54 +0000, sebb wrote: > > On 10/12/06, Ortwin Gl=FCck wrote: > > > Roland Weber wrote: > > > > on second thoughts: do we really want to deal with charsets and cha= racter > > > > encodings in our source code? If so, which should it be? ISO-Latin-= 15? > > > > Unicode in UTF-8? (I don't know a russian codepage as another examp= le :-) > > > > Will we run into conversion problems, from Subversion or our editor= s? > > > > I haven't yet figured out how to make Emacs load and store UTF-8. > > > > > > Roland, > > > > > > Feel free to use the German ASCII replacement in my Name: "Glueck". > > > > > > > The alternative is to declare the source code US-ASCII, and to use = the > > > > standard Java mechanisms (\unnnn) or, for JavaDocs, HTML escapes > > > > (&#xnnn; ü) for special characters. > > > > > > > BTW, there has been some discussion as to whether the @author tags > > should be present in ASF code at all; not sure that it was decided > > finally either way... > > > > S. > > > > Hi Sebastian, > > I personally do not fully agree with the arguments frequently given as > the rationale for not using @author tags. As far as I know there is no > official policy regarding the use of @author tags, so it is ultimately > up to individual projects to decide. > > The issue was discussed before on this list and the outcome was to keep > @author tags but to require all new contributors who wish to have > authorship attribution in the source code to have a CLA on file. (1) > This ensures contributors may not claim copyright based on the fact they > are mentioned as co-authors of some components in an ASF owned project. > (2) The hassle of having to go though the trouble of filing a CLA should > also act as a rather significant discouragement for those folks who may > otherwise be tempted to ask for an @author entry based on submission of > a one-liner fix. > > Folks, does this agreement still hold? Is it time we revisited the > decision? > > Oleg > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: httpcomponents-dev-unsubscribe@jakarta.apache.o= rg > > For additional commands, e-mail: httpcomponents-dev-help@jakarta.apache= .org > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: httpcomponents-dev-unsubscribe@jakarta.apache.org > For additional commands, e-mail: httpcomponents-dev-help@jakarta.apache.o= rg > > --------------------------------------------------------------------- To unsubscribe, e-mail: httpcomponents-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: httpcomponents-dev-help@jakarta.apache.org