Thanks - I've now had a couple of responses, and the conclusion is that I can leave it as OSI-Approved.
Peace - John On Aug 1, 2007, at 12:48 PM, Alexey Zakhlestin wrote: > well… as far as I understand, INRIA license is basically a "new BSD- > license" > which is OSI-approved too > > On 8/1/07, John Ridgway <[EMAIL PROTECTED]> wrote: >> Friends - >> I'm working on an update to the aspectj port, and I need advice on >> what to fill in for the License field. The current value is OSI- >> Approved, which is probably incorrect. AspectJ (TM) is distributed >> under the EPL, which is OSI-Approved, but it includes Third Party >> Content licensed under the Apache Software License (also OSI- >> Approved). It also includes ASM v2.2.1, which is licensed by INRIA >> under the following conditions: >> >> >> Copyright (c) 2000-2005 INRIA, France Telecom >> All rights reserved. >> >> Redistribution and use in source and binary forms, with or without >> modification, are permitted provided that the following conditions >> are met: >> >> 1. Redistributions of source code must retain the above copyright >> notice, this list of conditions and the following disclaimer. >> >> 2. Redistributions in binary form must reproduce the above copyright >> notice, this list of conditions and the following disclaimer >> in the >> documentation and/or other materials provided with the >> distribution. >> >> 3. Neither the name of the copyright holders nor the names of its >> contributors may be used to endorse or promote products >> derived from >> this software without specific prior written permission. >> >> THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS >> "AS IS" >> AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, >> THE >> IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR >> PURPOSE >> ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR >> CONTRIBUTORS BE >> LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR >> CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF >> SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR >> BUSINESS >> INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, >> WHETHER IN >> CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR >> OTHERWISE) >> ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF >> ADVISED OF >> THE POSSIBILITY OF SUCH DAMAGE. >> >> >> What value should I use for the license field? >> >> Peace >> - John >> >> >> --------------------------------------------------------------------- >> ---- >> This SF.net email is sponsored by: Splunk Inc. >> Still grepping through log files to find problems? Stop. >> Now Search log events and configuration files using AJAX and a >> browser. >> Download your FREE copy of Splunk now >> http://get.splunk.com/ >> _______________________________________________ >> Fink-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/fink-devel >> > > > -- > Alexey Zakhlestin > http://blog.milkfarmsoft.com/ > ---------------------------------------------------------------------- > --- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a > browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Fink-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/fink-devel ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Fink-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fink-devel
