release forms? (was: [Patches] New sys method to return total reference count in debug builds.)
Given the New World Order, how does that impact the need for these release
statements and/or wet signatures?
Or a better way to put it, who "owns" Python now? Given a "who", then we
can ask that person/entity whether they want release statements.
Given that Python is now on SourceForge, and there are multiple people (at
CNRI and otherwise) that can directly make modifications, then the release
below is certainly a bit "off". For example, David Ascher has commit
privs, so at his "sole discretion, [he may] decide whether or not to
incorporiate this contribution..." :-)
Thoughts?
Cheers,
-g
p.s. IMO, I'd like to see Guido own the Copyright for all current and
future Python development
--
Greg Stein, http://www.lyra.org/
---------- Forwarded message ----------
Date: Mon, 5 Jun 2000 09:18:30 +1000
From: Mark Hammond
Off the top of my head, I'd say that your questions aren't going to get answered until Guido gets back and gets a chance to answer them. In the interim, I think we should stick with the current approach. In the long run, of course, you won't need to grant CNRI permission to do anything with a submission. Jeremy
"GS" == Greg Stein
writes:
GS> Given the New World Order, how does that impact the need for GS> these release statements and/or wet signatures? GS> Or a better way to put it, who "owns" Python now? Given a GS> "who", then we can ask that person/entity whether they want GS> release statements. GS> Given that Python is now on SourceForge, and there are GS> multiple people (at CNRI and otherwise) that can directly make GS> modifications, then the release below is certainly a bit GS> "off". For example, David Ascher has commit privs, so at his GS> "sole discretion, [he may] decide whether or not to GS> incorporiate this contribution..." :-) I talked to Guido briefly about this. Since 1.6 is the last "CNRI release", he wants to continue along the current path for the time being. I'm sure he'll be just as happy to chuck all this crap as Greg, and we probably will for 1.7. -Barry
On 04 June 2000, Greg Stein said:
p.s. IMO, I'd like to see Guido own the Copyright for all current and future Python development
Second that. Given that I work for CNRI and was forced (at gunpoint, as I recall) to sign an incredibly draconian IP agreement -- along the lines of "everything you have ever created, or will ever consider creating, in any medium whatsoever, no matter where you did it or who pays for it, is the property of CNRI for all time" -- I'd have a hard time getting away with slapping "Copyright (c) 1999-2000 Gregory P. Ward" all over the Distutils code. And given that fair chunks of that code have been contributed by other people, I couldn't even ethically do that. So, given that I probably can't claim ownership in the code, and that CNRI has absolutely no moral right to it (although probably some legal right), I'd prefer to sign it away to Guido. Or optionally, to some legal fiction that represents the Python community; preferably *not* the Python Consortium, as long as CNRI is in any way connected. Death to the lawyers! Greg -- Greg Ward - software developer gward@mems-exchange.org MEMS Exchange / CNRI voice: +1-703-262-5376 Reston, Virginia, USA fax: +1-703-262-5367
On Wed, 7 Jun 2000, Greg Ward wrote:
CNRI has absolutely no moral right to it (although probably some legal right), I'd prefer to sign it away to Guido. Or optionally, to some legal fiction that represents the Python community; preferably *not* the Python Consortium, as long as CNRI is in any way connected.
Who's in charge of the PSA?
Or should we form *another* non-profit, and sign it over to it?
(Personally, I couldn't care less who I transfer copyright over my Python
contributions to -- I'd put it in the public domain if that's what it
took)
--
Moshe Zadka
"MZ" == Moshe Zadka
writes:
MZ> Who's in charge of the PSA? Or should we form *another* MZ> non-profit, and sign it over to it? (Personally, I couldn't MZ> care less who I transfer copyright over my Python MZ> contributions to -- I'd put it in the public domain if that's MZ> what it took) Please remember that the copyright holder can release the code under whatever license they want, even multiple different licenses. Copyright != license. I'm not sure what the right thing to do here is. On the one hand, Bob Kahn always said nobody would use Python if its heritage (i.e. copyright ownership) were not nailed down like Java. On the other hand, there's a lot of nobodies out there right now :). For GNU projects, the FSF wants to own all the copyrights to the code. They actually want you to legally assign the copyright to them. Their explanation for this onerous requirement is that if they were not the copyright holder, they would not have the legal standing to defend GPL violations, or would have to coordinate with a ton of developers, making such legal defenses practically impossible. Python is in a different situation, IMO, because it has a /less/ restrictive license than the GPL, so there's less to get all huffy about in court. If someone builds a binary-only proprietary blend of Python and starts selling it without source code, well, there's no license violation there, so what's to defend? The argument has been made that without clear legal title, someone could claim that some of the donated code in Python violated a copyright or patent and try to stop 3rd parties from using Python. Who knows what the actual legal possibility of that happening are, but I don't see how 1) we could take any real defense against this or 2) it affects Python any differently than any other large multi-contributor open source system. -Barry
On Wed, Jun 07, 2000 at 05:33:10PM +0300, Moshe Zadka wrote:
On Wed, 7 Jun 2000, Greg Ward wrote:
CNRI has absolutely no moral right to it (although probably some legal right), I'd prefer to sign it away to Guido. Or optionally, to some legal fiction that represents the Python community; preferably *not* the Python Consortium, as long as CNRI is in any way connected.
Who's in charge of the PSA?
CNRI Effectively, the PSA is a legal fiction for collecting donations to further the development of Python. The Consortium is similar, but members have the actual/explicit capability to steer Python's development. I believe this ability to steer the development is (was?) rooted in the fact that CNRI employed Guido. I have no idea how that will work now -- the "steering" will (essentially) have to rely entirely on Guido's good graces. Guido is an excellent listener to people's needs, so there is no immediate problem here.
Or should we form *another* non-profit, and sign it over to it?
The Apache Software Foundation is already a legal, formed, non-profit corporation. If the desire is to transfer copyright to a non-profit, then I'd recommend reusing the ASF rather than trying to start a new one. Recognize that running a company (even a non-profit) is not a "zero cost" item. Somebody would have to put that time in. CNRI is also non-profit, but its members/board/directors/etc are not as Open Source minded as the ASF.
(Personally, I couldn't care less who I transfer copyright over my Python contributions to -- I'd put it in the public domain if that's what it took)
As Barry said: license and copyright are different. Since you own the copyright, then you *can* put it into the public domain Right Now. I've done that with some of my modules (e.g. qp_xml and imputil). Here is the header from qp_xml.py: # # qp_xml: Quick Parsing for XML # # Written by Greg Stein. Public Domain. # No Copyright, no Rights Reserved, and no Warranties. # Fun, huh? :-) On the other hand, I have given Guido two pieces of code: httplib.py and davlib.py: # # DAV client library # # Copyright (C) 1998-1999 Guido van Rossum. All Rights Reserved. # Written by Greg Stein. Given to Guido. Licensed using the Python license. # Oh. I need to update his copyright year :-) Want to know something really funny? Presuming my httplib.py goes into the Python distribution, that will be the first piece of code that Guido truly owns in Python. All the other code he wrote is owned by CWI or CNRI.... Cheers, -g -- Greg Stein, http://www.lyra.org/
"GS" == Greg Stein
writes:
GS> On Wed, Jun 07, 2000 at 05:33:10PM +0300, Moshe Zadka wrote:
On Wed, 7 Jun 2000, Greg Ward wrote:
CNRI has absolutely no moral right to it (although probably some legal > right), I'd prefer to sign it away to Guido. Or optionally, to some > legal fiction that represents the Python community; preferably *not* the > Python Consortium, as long as CNRI is in any way connected.
Who's in charge of the PSA?
GS> CNRI GS> Effectively, the PSA is a legal fiction for collecting donations GS> to further the development of Python. The Consortium is similar, GS> but members have the actual/explicit capability to steer GS> Python's development. I believe this ability to steer the GS> development is (was?) rooted in the fact that CNRI employed GS> Guido. I have no idea how that will work now -- the "steering" GS> will (essentially) have to rely entirely on Guido's good GS> graces. Guido is an excellent listener to people's needs, so GS> there is no immediate problem here. The description of the PSA isn't exactly right. The PSA FAQ has an official explanation, which may not be right either, but at least it's what CNRI wants you to think. (And it may be right; I don't mean to suggest a nefarious plot, just that the relationship is convoluted enough that the explanation could be wrong.) http://www.python.org/psa/FAQ.html An abbreviated version follows: |Where does the money from membership fees go and who pays the rest? | | The money goes towards the salary of those who maintain and | coordinate the Python web site, ftp server, mailing lists, | conference expenses etc.... The case for these expenditures is | that a seed community is being incubated. CNRI officers and | directors see proof of the existence of such a community from the | fact that some members of that community are willing to pay some | of their own money to foster the activity. | |Who funds Python's development? | PSA fees do not fund the Python development effort.... CNRI is no longer maintaining python.org, although it still owns the domain and maintains the equipment it runs on. The existence of a community should be obvious now, without the need for people to pay money to prove it. Jeremy
participants (5)
-
bwarsaw@python.org
-
Greg Stein
-
Greg Ward
-
Jeremy Hylton
-
Moshe Zadka