[Python-Dev] release forms? (was: [Patches] New sys method to return total reference count in debug builds.)

[Greg Stein]

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 <mhammond@skippinet.com.au>
To: patches@python.org
Subject: [Patches] New sys method to return total reference count in debug
    builds.

[... snip ...]

Release info:

I confirm that, to the best of my knowledge and belief, this contribution
is free of any claims of third parties under copyright, patent or other
rights or interests ("claims").  To the extent that I have any such claims,
I hereby grant to CNRI a nonexclusive, irrevocable, royalty-free, worldwide
license to reproduce, distribute, perform and/or display publicly, prepare
derivative versions, and otherwise use this contribution as part of the
Python software and its related documentation, or any derivative versions
thereof, at no cost to CNRI or its licensed users, and to authorize others
to do so.

I acknowledge that CNRI may, at its sole discretion, decide whether or not
to incorporate this contribution in the Python software and its related
documentation.  I further grant CNRI permission to use my name and other
identifying information provided to CNRI by me for use in connection with
the Python software and its related documentation.

Mark.


_______________________________________________
Patches mailing list
Patches@python.org
http://www.python.org/mailman/listinfo/patches