Menu
▾
▴
cvs-syncmail-talk
|
From: Kevin R. <ke...@ro...> - 2002-11-08 04:22:21
|
Hello CVS-Syncmail list,
I started usign cvs-syncmail and I like it a lot. I'd like to package
this for the Debian GNU/Linux distribution. I see a copyright in
docs/syncmail.sgml, but there is no license that specifies rights of
use or redistribution for cvs-syncmail. Without such a license, I
can't distribute cvs-syncmail as a Debian package.
What is the license for cvs-syncmail?
Thanks for your time and the excellent tool.
--
Kevin Rosenberg | .''`. ** Debian GNU/Linux **
http://b9.com/debian.html | : :' : The universal
GPG signed and encrypted | `. `' Operating System
messages accepted. | `- http://www.debian.org/
|
|
From: Fred L. D. Jr. <fd...@ac...> - 2002-11-08 04:37:41
|
Kevin Rosenberg writes: > I started usign cvs-syncmail and I like it a lot. I'd like to package > this for the Debian GNU/Linux distribution. I see a copyright in > docs/syncmail.sgml, but there is no license that specifies rights of > use or redistribution for cvs-syncmail. Without such a license, I > can't distribute cvs-syncmail as a Debian package. I don't think we've ever really talked much about the license for syncmail, and I'm not sure where to find what license information was provided to SourceForge. Barry, do you remember how you set it up? If no one can remember what the license is, I'll propose we stick the PSF license on it. ;-) -Fred -- Fred L. Drake, Jr. <fdrake at acm.org> PythonLabs at Zope Corporation |
|
From: <ba...@zo...> - 2002-11-08 15:20:10
|
>>>>> "Fred" == Fred L Drake, Jr <fd...@ac...> writes:
>> I started usign cvs-syncmail and I like it a lot. I'd like to
>> package this for the Debian GNU/Linux distribution. I see a
>> copyright in docs/syncmail.sgml, but there is no license that
>> specifies rights of use or redistribution for
>> cvs-syncmail. Without such a license, I can't distribute
>> cvs-syncmail as a Debian package.
Fred> I don't think we've ever really talked much about the
Fred> license for syncmail, and I'm not sure where to find what
Fred> license information was provided to SourceForge. Barry, do
Fred> you remember how you set it up?
I'm nearly positive I chose "Python license" when I set up the
project. Certainly the intent was to put a Pythonic license on the
thing, and perhaps eventually donate it to the PSF.
Fred> If no one can remember what the license is, I'll propose we
Fred> stick the PSF license on it. ;-)
Unfortunately, if you actually read the PSF license for Python, it's
pretty specific to Python and the fact that the PSF is the entity that
is actually doing the licensing. It doesn't really apply out of the
box to syncmail.
We certainly could donate syncmail to the PSF, but there (still :(
) isn't a really great mechanism for doing. The best that's out there
is a proposed contribution form:
http://www.python.org/psf/psf-contributor-agreement.html
BTW, I brought this up on the PSF mailing lists back in May, specific
for syncmail. Like too many other things, we lost interest and the
thread died without traction (I blame myself for that). At the time,
I proposed the following license. Note that that it would require
donating the software to the PSF, and then there's the question of who
would need to do the donating (everyone who's committed changes to the
code, just me, etc...)
-Barry
-------------------- snip snip --------------------
PSF LICENSE AGREEMENT 1.0
-------------------------
1. This LICENSE AGREEMENT is between the Python Software Foundation
("PSF"), and the Individual or Organization ("Licensee") accessing and
otherwise using PSF software ("the Software") in source or binary form
and its associated documentation.
2. Subject to the terms and conditions of this License Agreement, PSF
hereby grants Licensee a nonexclusive, royalty-free, world-wide
license to reproduce, analyze, test, perform and/or display publicly,
prepare derivative works, distribute, and otherwise use the Software
alone or in any derivative version, provided, however, that PSF's
License Agreement and PSF's notice of copyright are retained in the
Software alone or in any derivative version prepared by Licensee.
3. In the event Licensee prepares a derivative work that is based on
or incorporates the Software or any part thereof, and wants to make
the derivative work available to others as provided herein, then
Licensee hereby agrees to include in any such work a brief summary of
the changes made to the Software.
4. PSF is making the Software available to Licensee on an "AS IS"
basis. PSF MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR
IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, PSF MAKES NO AND
DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS
FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE WILL NOT
INFRINGE ANY THIRD PARTY RIGHTS.
5. PSF SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF THE
SOFTWARE FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS
AS A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING THE
SOFTWARE, OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE
POSSIBILITY THEREOF.
6. This License Agreement will automatically terminate upon a material
breach of its terms and conditions.
7. Nothing in this License Agreement shall be deemed to create any
relationship of agency, partnership, or joint venture between PSF and
Licensee. This License Agreement does not grant permission to use PSF
trademarks or trade name in a trademark sense to endorse or promote
products or services of Licensee, or any third party.
8. By copying, installing or otherwise using the Software, Licensee
agrees to be bound by the terms and conditions of this License
Agreement.
|
|
From: Kevin R. <ke...@ro...> - 2002-11-08 15:46:39
|
Barry A. Warsaw wrote: > I'm nearly positive I chose "Python license" when I set up the > project. Certainly the intent was to put a Pythonic license on the > thing, and perhaps eventually donate it to the PSF. Hi Barry, thanks for the reply. > Unfortunately, if you actually read the PSF license for Python, it's > pretty specific to Python and the fact that the PSF is the entity that > is actually doing the licensing. It doesn't really apply out of the > box to syncmail. Yeah, I saw that. > We certainly could donate syncmail to the PSF, but there (still :( > ) isn't a really great mechanism for doing. The best that's out there > is a proposed contribution form: > > http://www.python.org/psf/psf-contributor-agreement.html I'm not familiar with other software that has had copyrights assigned to the PSF, but I suspect that it has happed. > BTW, I brought this up on the PSF mailing lists back in May, specific > for syncmail. Like too many other things, we lost interest and the > thread died without traction (I blame myself for that). At the time, > I proposed the following license. Note that that it would require > donating the software to the PSF, and then there's the question of who > would need to do the donating (everyone who's committed changes to the > code, just me, etc...) The PSF License looks fine. On the other hand, it is very similar to a BSD license except that the copyright is owned by the PSF. Rather that going through the efforts of assigning copyrights, perhaps sometime like the below would be acceptable. Thanks again for discussing this. I hope that a license is chosen soon so that I can add your fine product to the Debian distribution. -- Kevin Rosenberg | .''`. ** Debian GNU/Linux ** http://b9.com/debian.html | : :' : The universal GPG signed and encrypted | `. `' Operating System messages accepted. | `- http://www.debian.org/ Copyright (C) Barry Warsaw, Fred Drake, and contributors. 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 name of the author may not be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE AUTHOR 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 REGENTS 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. |
|
From: <ba...@zo...> - 2002-11-08 16:03:13
|
>>>>> "KR" == Kevin Rosenberg <ke...@ro...> writes:
>> We certainly could donate syncmail to the PSF, but there (still
>> :( ) isn't a really great mechanism for doing. The best that's
>> out there is a proposed contribution form:
>> http://www.python.org/psf/psf-contributor-agreement.html
KR> I'm not familiar with other software that has had copyrights
KR> assigned to the PSF, but I suspect that it has happed.
You might be wrong about that. ;)
KR> The PSF License looks fine. On the other hand, it is very
KR> similar to a BSD license except that the copyright is owned by
KR> the PSF. Rather that going through the efforts of assigning
KR> copyrights, perhaps sometime like the below would be
KR> acceptable.
I'd be happy with that. It's in the spirit of the original Python
license. Fred, Greg, and Zooko, what do you guys think?
KR> Thanks again for discussing this. I hope that a license is
KR> chosen soon so that I can add your fine product to the Debian
KR> distribution.
-Barry
|
|
From: Zooko <zo...@zo...> - 2002-11-08 20:02:09
|
> I'd be happy with that. It's in the spirit of the original Python > license. Fred, Greg, and Zooko, what do you guys think? +1 on BSD-ish license |
|
From: Fred L. D. Jr. <fd...@ac...> - 2002-11-08 21:21:30
|
Barry A. Warsaw writes: > I'd be happy with that. It's in the spirit of the original Python > license. Fred, Greg, and Zooko, what do you guys think? I'm fine with a BSDish license. -Fred -- Fred L. Drake, Jr. <fdrake at acm.org> PythonLabs at Zope Corporation |
|
From: Greg W. <gw...@py...> - 2002-11-11 17:23:35
|
On 08 November 2002, Barry A. Warsaw said:
> KR> The PSF License looks fine. On the other hand, it is very
> KR> similar to a BSD license except that the copyright is owned by
> KR> the PSF. Rather that going through the efforts of assigning
> KR> copyrights, perhaps sometime like the below would be
> KR> acceptable.
>
> I'd be happy with that. It's in the spirit of the original Python
> license. Fred, Greg, and Zooko, what do you guys think?
Whatever. As long as it's open source I don't much care.
Greg
--
Greg Ward <gw...@py...> http://www.gerg.ca/
I have the power to HALT PRODUCTION on all TEENAGE SEX COMEDIES!!
|
|
From: <ba...@py...> - 2002-11-08 22:05:46
|
I'm going to make a leap of faith and assume Greg's on board with the BSD-ish license. ;) I just checked in a LICENSE file and added copyright notices to the file. I hope that'll be enough for Kevin to add it to Debian. I stil want to leave open the possibility of PSF donation, if the PSF ever starts accepting such things. ;) -Barry |
|
From: Kevin R. <ke...@ro...> - 2002-11-08 23:45:02
|
Barry A. Warsaw wrote:
> I'm going to make a leap of faith and assume Greg's on board with the
> BSD-ish license. ;) I just checked in a LICENSE file and added
> copyright notices to the file. I hope that'll be enough for Kevin to
> add it to Debian.
Great -- I'm very happy to be able to redistribute this very helpful
product.
> I stil want to leave open the possibility of PSF donation, if the PSF
> ever starts accepting such things. ;)
Since you own the copyright, you can always change the licensing on
any time. Of course, copies of your software distributed with the
current license stay with the current license. But, that doesn't
affect your ability to relicense or to assign your copyright.
Thanks very much for your gift.
--
Kevin Rosenberg | .''`. ** Debian GNU/Linux **
http://b9.com/debian.html | : :' : The universal
GPG signed and encrypted | `. `' Operating System
messages accepted. | `- http://www.debian.org/
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X