On 30/11/2007, Marcus Boerger <[EMAIL PROTECTED]> wrote: > Hello Philip, > > for the future please do not accept any copyright other than > "The PHP Group" or "The PHP documentation Grroup". Thanks. > Otherwise comanies are going to own PHP piece by piece. > > marcus > > Thursday, November 29, 2007, 9:59:08 PM, you wrote: > > > On Nov 29, 2007, at 11:26 AM, Steph Fox wrote: > > >>>>> We do have peer-review after all. > >>>> > >>>> Not on CLA'd code we don't. > >>> > >>> Steph the CLA seems to just relate to the docbook xml specifications > >>> for PDO. > >> > >> Someone told you that, or have you developed psychic powers? > >> > >> The same applies, regardless. If a commit to that module breaks the > >> PHP manual build, you or I can't fix it. There was a time before > >> now when a CLA'd module broke the snaps build, same problem. > > > FWIW, there is an IBM copyright attached to the "PDO Driver How-To" > > document here: > > > http://php.net/manual/en/internals2.pdo.php > > > However, a ~couple months ago IBM gave permission to remove this > > copyright (because the authors are listed as general contributors, > > thus representing IBM) although we've not yet implemented this > > removal. We did [temporary] remove it about six months ago but... > > I'll make the update today. > > > Regards, > > Philip
In that case, you should: 1) Have a legal entity that you can assign copyright to (PHP Group and PHP Documentation Group are not legal entities and therefore cannot hold copyright) and 2) Have a legal form that people "sign" (could be a simple DCO attached to a submission) to assign their copyright to that legal entity We have neither of these things, so we're gesturing wildly and passionately about copyright statements but ultimately looking rather foolish. In the world of academic publishing, the open access movement is fighting hard to ensure that authors _retain_ copyright when they submit an article to a journal. Researchers license journals to publish their articles, so that we don't have to pay multiple times to access funded research (pay once to support the research, pay a second time to subscribe to the journal in which the research has been published). You're confusing copyright with licenses. Copyright should be retained by the author (of code or of documentation) - if they assign copyright to another entity, they waive any right to reuse their own work in a different forum - except under the terms under which that work is licensed by the entity that now has the copyright for that material. So an author can and should maintain copyright over the material they contribute, but they contribute it under a license that specifies the terms under which that material can be used (the PHP License, for this project) by others. -- Dan Scott Laurentian University -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
