Return-Path: Delivered-To: apmail-commons-dev-archive@www.apache.org Received: (qmail 93046 invoked from network); 10 Jan 2008 20:47:05 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 10 Jan 2008 20:47:05 -0000 Received: (qmail 39916 invoked by uid 500); 10 Jan 2008 20:46:53 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 39850 invoked by uid 500); 10 Jan 2008 20:46:53 -0000 Mailing-List: contact dev-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list dev@commons.apache.org Received: (qmail 39841 invoked by uid 99); 10 Jan 2008 20:46:53 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Jan 2008 12:46:53 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [62.179.121.50] (HELO viefep32-int.chello.at) (62.179.121.50) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Jan 2008 20:46:28 +0000 Received: from [192.168.1.101] (really [84.113.196.60]) by viefep32-int.chello.at (InterMail vM.7.08.02.02 201-2186-121-104-20070414) with ESMTP id <20080110204626.NVYN26521.viefep32-int.chello.at@[192.168.1.101]> for ; Thu, 10 Jan 2008 21:46:26 +0100 Subject: Re: [IO] Planning IO 1.4 release From: simon To: Jakarta Commons Developers List In-Reply-To: <47867BFC.2020809@apache.org> References: <191539.44918.qm@web86511.mail.ird.yahoo.com> <25aac9fc0801100832x55890248k6ef511e1473478f8@mail.gmail.com> <55afdc850801100839m383f1dfh95b90b1382667093@mail.gmail.com> <25aac9fc0801100901n5734d06atf07ffa2d2dfed565@mail.gmail.com> <47867BFC.2020809@apache.org> Content-Type: text/plain Date: Thu, 10 Jan 2008 21:46:26 +0100 Message-Id: <1199997986.14527.29.camel@simon-laptop> Mime-Version: 1.0 X-Mailer: Evolution 2.12.1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On Thu, 2008-01-10 at 21:11 +0100, Dennis Lundberg wrote: > sebb wrote: > > AIUI, the NOTICE file is not about dependencies, it is about the > > artefacts that are actually included in the distribution. > > > > In the case of Commons, dependencies are normally not included in the > > distribution, and should therefore not be included in NOTICE. > > Now I better understand why you feel the way you do about this. > > The approach that mrrp takes is to inform about software that is either > included *or* used by the current project. So it behaves differently > than you expect it to. I don't have much insight into the legal stuff > surrounding these files, but mrrp is used by lots of ASF project. So I > suspect that the generated NOTICE files comply with ASF policy. In legal terms, things like "I don't have much insight into the legal stuff" and "I suspect that that generated NOTICE files comply.." worry me a lot. It also bothers me that "lots of projects" appear to have changed their legal process without asking on legal-discuss. Now I don't have much insight into legal issues either, and it may well be that you are right and I am wrong. But if processes are to be *changed*, then surely we need to validate the change before applying it. Just making changes to the legal processes without any expert opinion seems to be asking for trouble. Which projects are using mrrp auto-notice generation, and since when? Regards, Simon --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org For additional commands, e-mail: dev-help@commons.apache.org