Over in pyx-user we've been discussing adding "ColorBrewer" color
schemes (www.colorbrewer.org). Here's the license (below). It's
"Apache-like". If we were to use them, it's clearly "source form"
redistribution. I don't think adding the
copyright/conditions/disclaimer is a problem, or the acknowledgement,
or putting the appropriate text in the manual. The only thing I don't
know about is the compatibility of this license with the GPL.
Thoughts?

JDO

# Copyright (c) 2002 Cynthia Brewer, Mark Harrower, and The
# Pennsylvania State University. All rights reserved. Redistribution
# and use in source and binary forms, with or without modification,
# are permitted provided that the following conditions are met:
# 
# -  Redistributions as source code must retain the above copyright
#    notice, this list of conditions and the following disclaimer.
# -  The end-user documentation included with the redistribution, if
#    any, must include the following acknowledgment:
#      This product includes color specifications and designs
#      developed by Cynthia Brewer (http://colorbrewer.org/).
#    Alternately, this acknowledgment may appear in the software
#    itself, if and wherever such third-party acknowledgments normally
#    appear.
# -  The name "ColorBrewer" must not be used to endorse or promote
#    products derived from this software without prior written
#    permission. For written permission, please
#    contact Cynthia Brewer at [EMAIL PROTECTED]
# -  Products derived from this software may not be called
#    "ColorBrewer", nor may "ColorBrewer" appear in their name, without
#    prior written permission of Cynthia Brewer.
# 
# 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 CYNTHIA BREWER, MARK HARROWER, OR THE PENNSYLVANIA
# STATE UNIVERSITY 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.


_______________________________________________
PyX-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pyx-devel

Reply via email to