Hi, Excuse me if this is a silly question..
> The QPL uses the same tactic to control distribution of customized versions > of Qt. But this creates is a pain for developers and end-users alike. The pain you speak of, is this from a purely "legal" stand point? If so, in what manner does it hinder or "cause pain" to an end user? The reason I ask is I am thinking of implementing something similar to this in my soon to be released framework in the hopes that it will provide a higher level of quality for the end users. As most programmers know, moduler applications can become diluted over time with third party "plug-ins/addons", some to the point where Module "A" by company x can not be used with Module "B" by company z, and it's the end user who gets screwed. I am not a lawyer, just a guy who writes a ton of code so please excuse my ignorance on this point. Thanks to all who contribute to the legal/license stuff, guys like me would be lost without you :) Have a great day! Mike Wattier On Wednesday 20 November 2002 11:50 pm, Bruce Dodson wrote: > The QPL uses the same tactic to control distribution of customized versions > of Qt. But this creates is a pain for developers and end-users alike. At > least your term #8 provides an alternative, changing this "requirement" to > distribute patches into something that's optional. But it's confusing the > way 7 and 8 seem to contradict one another. As a licensee, I would be > scratching my head, unsure whether I was compliant or not. > > Please consider dropping term 7, and simply leaving term 8. Given the > choice, most developers would choose that option anyway, because > distributing patches creates extra burden for the end-user. > > Even term 8 creates a difficult situation. You have a license whose first > line says, "The software is called RAINBOW", and then says that for > modified works, "The software must not be called RAINBOW". > > If I were you, I would check out the AFL 1.2. That version might not have > been approved yet when you made your request. Depending on what "business > requirement" points 7 and 8 of your license are meant to serve, you might > find that the AFL's Attribution Rights provision can be leveraged to > deliver the same business value in a different way. Then you'd have a > professionally written license, you wouldn't have to go through a long > drawn out process to try to get your license approved, and you can get on > with writing your software. > > ----- Original Message ----- > From: "Graziano Poretti" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Thursday, November 21, 2002 12:01 AM > Subject: discuss: Duemetri Public License (DPL) Version 1.0 > > > [ Please discuss this license. Graziano reports that the only change > > from the Zope license are terms 7 and 8. -russ ] > > > > hi > > we would like to start an open source project on a product called > > "rainbow". > > the 1st version of the license is at > > <http://www.duemetri.it/licenza.htm> http://www.duemetri.it/licenza.htm > > the most similar license is the ZOPE public license. the changes occur > > for the "Integrity of The Author's Source Code" - point #4 of OSD. > > according with this point, we prefer that the free distribution of > > source and binary would be granted with the release of official versions > > and modifications can be installed using the patch files only. the > > developers community will check and test all the patches in order to > > release the new official version including all new features (tested and > > with a sufficient documentation). > > > > thanks for ur time ... > > > > sincerely > > > > > > ------- > > Graziano Poretti - DUE METRI > > http://support.facile.duemetri.net <http://support.facile.duemetri.net/> > > - Per creare e gestire un portale in 20 minuti > > http://www.duemetri.it <http://www.duemetri.it/> > > tel.: 0039 184 42163 > > Fax: 0039 184 462673 > > > > -- License follows > > > > Duemetri Public License (DPL) Version 1.0 > > > > 1. The software is called ``RAINBOW'' > > 2. This software is Copyright (c) Duemetri sas (tm) and Contributors. > > All rights reserved > > 3. Redistributions in source code must retain the above copyright > > notice, this list of conditions, and the following disclaimer. > > 4. 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. > > 5. The name Duemetri sas (tm) must not be used to endorse or promote > > products derived from this software without prior written permission > > from Duemetri sas > > 6. If any files are modified, you must cause the modified files to carry > > prominent notices stating that you changed the files and the date of any > > change. > > > > Disclaimer > > > > THIS SOFTWARE IS PROVIDED BY DUEMETRI SAS ''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 DUEMETRI SAS 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. > > > > 7. The official version of the product will be released by Duemetri sas. > > The distribution of the modified product in source or binary form is > > allowed as official version and ``patch files''. > > 8. The distribution of modified versions of the software without using > > ``patch files'' is allowed. In this case is fobidden to use the term > > ``Rainbow'' as the name (or part of it) of the product > > > > > > -- License ends > > -- > > license-discuss archive is at http://crynwr.com/cgi-bin/ezmlm-cgi?3 -- license-discuss archive is at http://crynwr.com/cgi-bin/ezmlm-cgi?3
