Clarification, please

Bryan George lyricos at mindspring.com
Sun Sep 9 19:45:48 UTC 2001


The first paragraph of http://www.opensource.org/licenses/index.html
states:

"For your convenience, we have collected here copies of the licenses
approved by OSI. If you distribute your software under one of these
licenses, you are permitted to say that your software is "OSI Certified
Open Source Software.""

However, if I choose to distribute my software under the Apache license,
I clearly don't want to use the verbatim license.  How much leeway do I
have in modifying the wording of a license derived from one of the
canonical forms while still claiming to distribute my software under the
terms of that license?

For reference, I am attaching a copy of the derived license in
question.  Sorry, I know the question is a bit challenged, but there are
no real guidelines for this on 'opensource.org' that I can see.

Thanks in advance for your assistance,

Bryan

--
Bryan George             Email: lyricos at mindspring.com
5 Butternut Way          Web:   http://www.mindspring.com/~lyricos
Sterling, VA 20164       Phone: (703) 707-8578 (H), (801) 740-5156 (F)
-------------- next part --------------
Copyright (c) 2001 by Bryan George. 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. The end-user documentation included with the redistribution, if
any, must include the following acknowledgment:

     "This product includes software developed by the
     Lyricos Project (http://www.lyricos.org/)."

Alternately, this acknowledgment may appear in the software itself, if
and wherever such third-party acknowledgments normally appear.

4. The names "Lyricos" and "Lyricos Project" must not be used to
endorse or promote products derived from this software without prior
written permission of Bryan George. For written permission, please
contact bgeorge at lyricos.org.

5. Products derived from this software may not be called "Multiple
Data Type Matrix Library" or "MDTM", nor may "Multiple Data Type
Matrix Library" or "MDTM" appear in their name, without prior written
permission of Bryan George.

THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED 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 BRYAN GEORGE OR THE LYRICOS PROJECT OR
ITS 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.


More information about the License-discuss mailing list