Fair enough. Could you offer some suggestions for concise changes
that would help fix the problem?
Thanks.
On 9/18/05, Søren Wedel Nielsen <[EMAIL PROTECTED]> wrote:
> fre, 16 09 2005 kl. 14:27 -0400, skrev Timothy Miller:
> > I had some hardware down time, and as a result, I'm quite certain that
> > I missed a suggestion someone made. If so, please remind me. This is
> > the latest revision of the license for your criticism.
> >
> > Thanks.
> >
> >
> > /*
> > DUAL LICENSING
> >
> > "modifications"
> >
> > (0) This "Work" is defined to be this document or source code, parts of
> > this document or source code, or derivative works of this document or
> > source code. Use of the Work, in whole or in part, must comply with
> > the licensing terms below.
> >
> > (1) This Work is licensed under LGPL 2.0 or newer. You have the right to
>
> > use and modify this Work, as long as you publish your changes to the
> Work.
>
>
> Why not follow the recommendations in the LGPL on how to apply it to your
> code:
> ------------------------------------------------------------------------
> How to Apply These Terms to Your New Libraries
>
> If you develop a new library, and you want it to be of the greatest
> possible use to the public, we recommend making it free software that
> everyone can redistribute and change. You can do so by permitting
> redistribution under these terms (or, alternatively, under the terms of
> the
> ordinary General Public License).
>
> To apply these terms, attach the following notices to the library. It is
> safest to attach them to the start of each source file to most
> effectively
> convey the exclusion of warranty; and each file should have at least the
> "copyright" line and a pointer to where the full notice is found.
>
> <one line to give the library's name and a brief idea of what it does.>
> Copyright (C) <year> <name of author>
>
> This library is free software; you can redistribute it and/or
> modify it under the terms of the GNU Lesser General Public
> License as published by the Free Software Foundation; either
> version 2 of the License, or (at your option) any later version.
>
> This library is distributed in the hope that it will be useful,
> but WITHOUT ANY WARRANTY; without even the implied warranty of
> MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
> Lesser General Public License for more details.
>
> You should have received a copy of the GNU Lesser General Public
> License along with this library; if not, write to the Free Software
> Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307
> USA
>
> Also add information on how to contact you by electronic and paper mail.
> ------------------------------------------------------------------------
>
>
> The (L)GPLv2 does not require that you publish your changes, only that
> you offer to distribute the code if you distribute binaries. So I
> think the condition "as long as you publish your changes to the Work" is
> inconsistent with the terms of the LGPL, which state
>
> "You may not impose any further restrictions on the recipients' exercise
> of the rights granted herein."
>
>
> > (2) This Work is also licensed as a proprietary work, all rights
> > belonging to Traversal Technology. Traversal Technology may use this
> > Work under those terms and has the right to publish, license, and sell
> > this Work and derivative works as they see fit. To remove these rights,
> > you must remove this clause.
> >
> > (3) Use of this Work without clause (2) forfeits the right to use any
> > trademarks owned by Traversal Technology, the Open Graphics Project, or
> > related organizations.
> >
> > (4) Patches, modifications, and extensions (collectively, "Changes")
> > to this Work that are submitted to the Open Graphics Project, the Open
> > Graphics Mailing List, directly to Traversal Technology, or to an agent
> > thereof must be SIGNED by the author of said Change, granting
> > Traversal Technology "rights to use" under clause (2), as well as
> > clause (1).
> > Unsigned Changes will be ignored.
> >
> > (5) Changes committed directly to an officially recognized source code
> > repository are signed implicitly. Those who have write access to such
> > a repository and who commit Changes to that repository grant rights to
> > Traversal Technology under clause (2), as well as clause (1), by virtue
> > of having write access and choosing to submit Changes.
> >
> > (6) It is the responsibility of the submitter of a Change to ensure that
> > they have the right to do so and that they have necessary permissions
> > from any other contributors or third parties. This pertains to both
> > patents and copyrights.
> >
> > (7) An implementation of this Work that is considered analogous to a
> > "binary distribution" is defined as any form that is not easily
> > readable by humans ("non-preferred"), which includes, but is not
> > limited to: Fixed-function IC (e.g. ASIC), fixed-function IC masks
> > or other fabrication intermediate step, variable-function IC (e.g.
> > FPGA), FPGA bitfile, compiled or translated simulation model.
> >
> > (8) Traversal Technology does not require an exclusive license to your
> > work. You retain the right to use the contents of your Changes, and you
> > may retain copyright to your Changes. Clauses (1) through (7) still
> > apply. At your discretion, you are encouraged to add comments to the
> > "contributions" section of this Work, indicating the nature of your
> > Change.
> > */
> >
> > _______________________________________________
> > Open-graphics mailing list
> > [email protected]
> > http://lists.duskglow.com/mailman/listinfo/open-graphics
> > List service provided by Duskglow Consulting, LLC (www.duskglow.com)
>
> _______________________________________________
> Open-graphics mailing list
> [email protected]
> http://lists.duskglow.com/mailman/listinfo/open-graphics
> List service provided by Duskglow Consulting, LLC (www.duskglow.com)
>
_______________________________________________
Open-graphics mailing list
[email protected]
http://lists.duskglow.com/mailman/listinfo/open-graphics
List service provided by Duskglow Consulting, LLC (www.duskglow.com)
