Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:34222
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.198.184 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references;
        b=eFEuMMFnAgDR+LJ01rclfdu8Fb2I3ZeTs+VHNqvqgd80Xnh408E8sltpX1XZwf3FL2iUa3RG5IMkKOa/KfSF94+WbnKF+EF4G5m2DZABxg0jXw3DaY9nF26dhRPLfvnb948EoHh38m8eHK7tGVaFwm1o3zsSDnzdYdykrC04r0w=
Message-ID: <52dbac0f0712221143x7d74a40by59380c81100663c1@mail.gmail.com>
Date: Sat, 22 Dec 2007 16:43:40 -0300
To: "Christian Seiler" <chris_se@gmx.net>
Cc: internals@lists.php.net
In-Reply-To: <476D2854.5070803@gmx.net>
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_3331_4132090.1198352620672"
References: <98b8086f0712150818n40056cedyf0aae7a5a08a27b7@mail.gmail.com>
	 <476582E6.7020808@zend.com>
	 <D1011E25-76DB-4936-AF3B-F98F19DC2139@procata.com>
	 <200712172130.08216.larry@garfieldtech.com>
	 <4FADC266-873E-4FD2-BEC8-28EA9D833297@procata.com>
	 <476D2854.5070803@gmx.net>
Subject: Re: [PHP-DEV] PATCH: Implementing closures in PHP (was: anonymous functions in PHP)
From: malterisio777@gmail.com ("Martin Alterisio")

------=_Part_3331_4132090.1198352620672
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

2007/12/22, Christian Seiler <chris_se@gmx.net>:
>
>
> PPS: Oh, yeah, if it should be legally necessary, I grant the right to
> anybody to use this patch under any OSI certified license you may want
> to choose.
>
>
That's very kind of you but, if I was explained right, you don't have
copyright on a patch. If I understood the legalese correctly, you retain
authorship on the code provided, but this kind of derived work, which has no
purpose outside the original, cannot be claimed through copyright. You
specially did it for the php codebase, and has not a meaning outside it.

Consider what happens to the code you make to maintain an in-house
application of a company. You cannot claim copyright on that codebase, it
remains to the company. But, if you were to develop an app from scratch for
the same company, the company has the right to use it in-house, but if they
want to distribute it, they have to require your consent, because you're one
of the copyright holders.

Also consider what happens to reviewers that check and correct works from
other people, such as syntax and grammar checking in literature, or code
reviewing in software. They can claim authorship on their corrections, but
they cannot claim copyright.

Anyway, it's too complicate. The bottom line is that copyright cannot be
claimed on patches. Which makes complete sense, imagine what would happen to
open-source if it wasn't this way... the licensing documentation would
occupy more than the code itself...

------=_Part_3331_4132090.1198352620672--