Re: [VOTE] Removing author tags
Sylvain Wallez wrote: Hi all, We discussed more that one year ago the removal of @author tags in our source files (see [1] and [2]) but although the consensus was to remove them, we never actually did it. Now most if not all new classes added since then have no @author tag, leading to a strange situation where old authors are named but not newer ones. So I propose to remove @author tags with people names from all our source files. +1 However it cannot be automated. As Antonio reminded us, there are some files e.g. htmlArea that are not able to be changed. Don't forget the XML files too. Additionally, if you agree with removing names, do you want source files to have: [+1] no @author tag at all, [ ] @author The Cocoon development team [ ] @author . (something else) Please cast your votes. Additionally, non-committers that have contributed significant portions of code and think they will lose visibility with this removal can make their voice heard. We will consider updating either the release notes or the credits file. One reason that the removal of all authors was delayed last time, was that we decided that we needed to ensure that those people were mentioned in status.xml --David
Re: [VOTE] Removing author tags
On Mon, May 02, 2005 at 11:52:50PM +0200, Sylvain Wallez wrote: [+1] no @author tag at all, [+0] @author The Cocoon development team -- Giacomo Pati Otego AG, Switzerland - http://www.otego.com Orixo, the XML business alliance - http://www.orixo.com smime.p7s Description: S/MIME cryptographic signature
Re: [VOTE] Removing author tags
On Tuesday 03 May 2005 23:07, Ralph Goers wrote: Well, that may be true, but not being a lawyer I really don't know. As I read it I understood Larry basically saying, We provide the legal guidance, but we can't make you do anything. However, I guess I'd like somebody to clarify this to the point that we really understand what we should be doing. For those who doesn't follow legal-discuss@ mailing list, this issue is even more complex than @author tags and Copyright notices at the top of each file. The discussion has been revolving around the necessity for employees (esp in the USA) to get the Corporate CLA signed by his/her employer even if no OSS development was happening at work. The bottom line was basically, No matter when an employee produces IP, the employer can claim it., but I got the strong impression that this is not the case in Europe, where the employer can not claim IP (even with IP transfer contracts) if it has been produced without any assistance of the employer (i.e. bandwidth, computers, office space, et cetera) I am sure more rigid recommendations around ICLA, CCLA and Copyright notices will emerge from the legal group in due time. Meanwhile, since many other Apache projects have removed @author tags, and have Copyright notice set to ASF, the Cocoon project will not inflict any additional damage if this is not correct procedure, until told otherwise. Cheers Niclas
Re: [VOTE] Removing author tags
On Tue, 3 May 2005, Sylvain Wallez wrote: Vadim Gritsenko wrote: Just for fun, and for meaningless PR statements like Cocoon is a result of work of 12345 developers! 8-O, we can aggregate all names of all contributors into one file. Very cool ;-) Dw
Re: [VOTE] Removing author tags
Niclas Hedhman wrote: On Tuesday 03 May 2005 23:07, Ralph Goers wrote: Well, that may be true, but not being a lawyer I really don't know. As I read it I understood Larry basically saying, We provide the legal guidance, but we can't make you do anything. However, I guess I'd like somebody to clarify this to the point that we really understand what we should be doing. For those who doesn't follow legal-discuss@ mailing list, this issue is even more complex than @author tags and Copyright notices at the top of each file. The discussion has been revolving around the necessity for employees (esp in the USA) to get the Corporate CLA signed by his/her employer even if no OSS development was happening at work. The bottom line was basically, No matter when an employee produces IP, the employer can claim it., but I got the strong impression that this is not the case in Europe, where the employer can not claim IP (even with IP transfer contracts) if it has been produced without any assistance of the employer (i.e. bandwidth, computers, office space, et cetera) I am sure more rigid recommendations around ICLA, CCLA and Copyright notices will emerge from the legal group in due time. Meanwhile, since many other Apache projects have removed @author tags, and have Copyright notice set to ASF, the Cocoon project will not inflict any additional damage if this is not correct procedure, until told otherwise. The copyright attribution to the ASF seems to be problematic as it seems that, at least in some countries, an author cannot give its copyright. At Jackrabbit for example, they have no author tags and their source files start with Copyright 2004-2005 The Apache Software Foundation or its licensors, as applicable. This should cover both the collective work on which the ASF has copyright and the copyright of individual contributors that have licenced their work to the ASF. Sylvain -- Sylvain WallezAnyware Technologies http://apache.org/~sylvainhttp://anyware-tech.com Apache Software Foundation Member Research Technology Director
Re: [VOTE] Removing author tags
On 2 May 2005, at 22:52, Sylvain Wallez wrote: So I propose to remove @author tags with people names from all our source files. +1 Additionally, if you agree with removing names, do you want source files to have: [ X ] no @author tag at all, [ ] @author The Cocoon development team [ ] @author . (something else) regards Jeremy If email from this address is not signed IT IS NOT FROM ME Always check the label, folks ! smime.p7s Description: S/MIME cryptographic signature
Re: [VOTE] Removing author tags
On Wednesday 04 May 2005 16:16, Sylvain Wallez wrote: The copyright attribution to the ASF seems to be problematic as it seems that, at least in some countries, an author cannot give its copyright. Exactly. All variants exist, and effectively creating a nightmare. Furthermore, I assume it is even more difficult considering some people who are residing/working/citizen of more than one country, and/or work for companies in yet more countries. What I am worried about is that employees of USA companies will not be able to contribute to the ASF, due to this legal BS. (Getting a (large) company to sign the CCLA without any direct benefits will barely ever happen.) At Jackrabbit for example, they have no author tags and their source files start with Copyright 2004-2005 The Apache Software Foundation or its licensors, as applicable. This should cover both the collective work on which the ASF has copyright and the copyright of individual contributors that have licenced their work to the ASF. And on legal-discuss@ this formulation has come up, and deemed (by the lawyers) not valid. Cheers Niclas
Re: [VOTE] Removing author tags
Vadim Gritsenko wrote: ... Just for fun, and for meaningless PR statements like Cocoon is a result of work of 12345 developers! 8-O, we can aggregate all names of all contributors into one file. Cool! :-D In this case we have change the thread to: [VOTE] Refactor @author tags in a single file :-P -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) -
Re: [VOTE] Removing author tags
Nicola Ken Barozzi wrote: Vadim Gritsenko wrote: ... Just for fun, and for meaningless PR statements like Cocoon is a result of work of 12345 developers! 8-O, we can aggregate all names of all contributors into one file. Cool! :-D In this case we have change the thread to: [VOTE] Refactor @author tags in a single file :-P +1, seriously! Sylvain -- Sylvain WallezAnyware Technologies http://apache.org/~sylvainhttp://anyware-tech.com Apache Software Foundation Member Research Technology Director
RE: [VOTE] Removing author tags
-Original Message- From: Sylvain Wallez [mailto:[EMAIL PROTECTED] Sent: Montag, 2. Mai 2005 23:53 To: dev@cocoon.apache.org Subject: [VOTE] Removing author tags So I propose to remove @author tags with people names from all our source files. +1 Additionally, if you agree with removing names, do you want source files to have: [x] no @author tag at all, [ ] @author The Cocoon development team [ ] @author . (something else) Cheers, Alfred. This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please notify the sender urgently and then immediately delete the message and any copies of it from your system. Please also immediately destroy any hardcopies of the message. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. The sender's company reserves the right to monitor all e-mail communications through their networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of the sender's company.
Re: [VOTE] Removing author tags
Sylvain Wallez wrote:
Hi all,
We discussed more that one year ago the removal of @author tags in our
source files (see [1] and [2]) but although the consensus was to remove
them, we never actually did it. Now most if not all new classes added
since then have no @author tag, leading to a strange situation where
old authors are named but not newer ones.
So I propose to remove @author tags with people names from all our
source files.
+1
Additionally, if you agree with removing names, do you want source files
to have:
[X] no @author tag at all,
[ ] @author The Cocoon development team
[ ] @author . (something else)
Please cast your votes.
Additionally, non-committers that have contributed significant portions
of code and think they will lose visibility with this removal can make
their voice heard. We will consider updating either the release notes or
the credits file.
I think we should mention everybody who contributes to Cocoon, either in
status.xml or credits.txt and make references in our commit messages. See
Bertrands ideas in [2]
Sylvain
[1] http://marc.theaimsgroup.com/?l=xml-cocoon-devm=107783914605693w=2
[2] http://marc.theaimsgroup.com/?l=xml-cocoon-devm=108089900026744w=2
--
Reinhard Pötz Independent Consultant, Trainer (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
Re: [VOTE] Removing author tags
Sylvain Wallez wrote: So I propose to remove @author tags with people names from all our source files. Additionally, if you agree with removing names, do you want source files to have: [+1] no @author tag at all, [ ] @author The Cocoon development team [ ] @author . (something else) -- Leszek Gawron MobileBox [EMAIL PROTECTED] http://www.mobilebox.pl
Re: [VOTE] Removing author tags
Il giorno 02/mag/05, alle 23:52, Sylvain Wallez ha scritto: [ X] no @author tag at all, [ ] @author The Cocoon development team [ ] @author . (something else) Ugo -- Ugo Cei Tech Blog: http://agylen.com/ Source.zone: http://sourcezone.info/ Wine Food Blog: http://www.divinocibo.it/ smime.p7s Description: S/MIME cryptographic signature
Re: [VOTE] Removing author tags
Sorry, voting again, since in my previous message I didn't state an explicit +1 to the first question (although it could have been inferred from the answer to the second one). So I propose to remove @author tags with people names from all our source files. +1 Additionally, if you agree with removing names, do you want source files to have: [X ] no @author tag at all, [ ] @author The Cocoon development team [ ] @author . (something else) Ugo -- Ugo Cei Tech Blog: http://agylen.com/ Source.zone: http://sourcezone.info/ Wine Food Blog: http://www.divinocibo.it/ smime.p7s Description: S/MIME cryptographic signature
Re: [VOTE] Removing author tags
On 5/2/05, Sylvain Wallez [EMAIL PROTECTED] wrote: So I propose to remove @author tags with people names from all our source files. +1 Additionally, if you agree with removing names, do you want source files to have: [X ] no @author tag at all, [ ] @author The Cocoon development team [ ] @author . (something else) Ciao, -- Gianugo Rabellino Pro-netics s.r.l. - http://www.pro-netics.com Orixo, the XML business alliance: http://www.orixo.com (blogging at http://www.rabellino.it/blog/)
Re: [VOTE] Removing author tags
On 5/2/05, Sylvain Wallez [EMAIL PROTECTED] wrote: So I propose to remove @author tags with people names from all our source files. +1 Additionally, if you agree with removing names, do you want source files to have: [X] no @author tag at all, Additionally, non-committers that have contributed significant portions of code and think they will lose visibility with this removal can make their voice heard. We will consider updating either the release notes or the credits file. I'd rather add them automatically as Stefano suggests, though I expect this will be commonly forgotten. Geoff
Re: [VOTE] Removing author tags
On 2 May 2005, at 22:52, Sylvain Wallez wrote: So I propose to remove @author tags with people names from all our source files. +1 Additionally, if you agree with removing names, do you want source files to have: [+1] no @author tag at all, [ ] @author The Cocoon development team [ ] @author . (something else) Andrew. -- Andrew Savory, Managing Director, Luminas Limited Tel: +44 (0)870 741 6658 Fax: +44 (0)700 598 1135 Web: http://www.luminas.co.uk/ Orixo alliance: http://www.orixo.com/
Re: [VOTE] Removing author tags
Ralph Goers wrote: Daniel Fagerstrom wrote: Sylvain Wallez wrote: So I propose to remove @author tags with people names from all our source files. +1 Well, I'm not really sure how to vote on this. I've pasted an email from Larry Rosen to the Apache Legal list that seems to say that the Cocoon source files should not have the Apache copyright in them, but instead have the copyright of the committers who made the contibution. Obviously, this is in direct contrast to what we are doing and frankly, I think its nuts. While this doesn't have a lot to do with the @author tags, per se, it does seem to indicate that the files should have a record of ownership. Oh my... do we have to add a copyright notice for every one-line patch send by people? I see a difference in Larry's post between original work that pre-existed outside the ASF and is later contributed to the ASF, and work that was developped directly for the ASF. So this non-ASF copyright could be applicable to donations, but not to our collective everyday work on the code base. Sylvain -- Sylvain WallezAnyware Technologies http://apache.org/~sylvainhttp://anyware-tech.com Apache Software Foundation Member Research Technology Director
Re: [VOTE] Removing author tags
Stefano Mazzocchi wrote: Sylvain Wallez wrote: Hi all, We discussed more that one year ago the removal of @author tags in our source files (see [1] and [2]) but although the consensus was to remove them, we never actually did it. Now most if not all new classes added since then have no @author tag, leading to a strange situation where old authors are named but not newer ones. So I propose to remove @author tags with people names from all our source files. +1 Additionally, if you agree with removing names, do you want source files to have: [X] no @author tag at all, Additionally, non-committers that have contributed significant portions of code and think they will lose visibility with this removal can make their voice heard. We will consider updating either the release notes or the credits file. I think this should be done automatically, not depending on their voices being raised or not. Bertrand's script already extracted all @author tags, which allows automated processing to build an authors file. Also, when we commit a patch, the rule is to add the name of the patch contributor status.xml. Is it enough or should we also add it to a global authors file? Sylvain -- Sylvain WallezAnyware Technologies http://apache.org/~sylvainhttp://anyware-tech.com Apache Software Foundation Member Research Technology Director
Re: [VOTE] Removing author tags
Sylvain Wallez wrote: Also, when we commit a patch, the rule is to add the name of the patch contributor status.xml. Is it enough or should we also add it to a global authors file? Just for fun, and for meaningless PR statements like Cocoon is a result of work of 12345 developers! 8-O, we can aggregate all names of all contributors into one file. Vadim
Re: [VOTE] Removing author tags
Sylvain Wallez wrote: Ralph Goers wrote: Well, I'm not really sure how to vote on this. I've pasted an email from Larry Rosen to the Apache Legal list that seems to say that the Cocoon source files should not have the Apache copyright in them, but instead have the copyright of the committers who made the contibution. Obviously, this is in direct contrast to what we are doing and frankly, I think its nuts. While this doesn't have a lot to do with the @author tags, per se, it does seem to indicate that the files should have a record of ownership. Oh my... do we have to add a copyright notice for every one-line patch send by people? I see a difference in Larry's post between original work that pre-existed outside the ASF and is later contributed to the ASF, and work that was developped directly for the ASF. So this non-ASF copyright could be applicable to donations, but not to our collective everyday work on the code base. Well, that may be true, but not being a lawyer I really don't know. As I read it I understood Larry basically saying, We provide the legal guidance, but we can't make you do anything. However, I guess I'd like somebody to clarify this to the point that we really understand what we should be doing. Ralph
Re: [VOTE] Removing author tags
Vadim Gritsenko wrote: Sylvain Wallez wrote: Also, when we commit a patch, the rule is to add the name of the patch contributor status.xml. Is it enough or should we also add it to a global authors file? Just for fun, and for meaningless PR statements like Cocoon is a result of work of 12345 developers! 8-O, we can aggregate all names of all contributors into one file. That would be interesting! And better IMO that adding a notice in each file mentioning each and every person that has provided patches. Sylvain -- Sylvain WallezAnyware Technologies http://apache.org/~sylvainhttp://anyware-tech.com Apache Software Foundation Member Research Technology Director
Re: [VOTE] Removing author tags
Sylvain Wallez wrote: Hi all, We discussed more that one year ago the removal of @author tags in our source files (see [1] and [2]) but although the consensus was to remove them, we never actually did it. Now most if not all new classes added since then have no @author tag, leading to a strange situation where old authors are named but not newer ones. So I propose to remove @author tags with people names from all our source files. +1 Additionally, if you agree with removing names, do you want source files to have: [X] no @author tag at all, [ ] @author The Cocoon development team [ ] @author . (something else) Sylvain -- Sylvain WallezAnyware Technologies http://apache.org/~sylvainhttp://anyware-tech.com Apache Software Foundation Member Research Technology Director
Re: [VOTE] Removing author tags
Sylvain Wallez wrote: So I propose to remove @author tags with people names from all our source files. +1 Additionally, if you agree with removing names, do you want source files to have: [ x ] no @author tag at all, [ ] @author The Cocoon development team [ ] @author . (something else) /Daniel
Re: [VOTE] Removing author tags
Sylvain Wallez wrote: Hi all, We discussed more that one year ago the removal of @author tags in our source files (see [1] and [2]) but although the consensus was to remove them, we never actually did it. Now most if not all new classes added since then have no @author tag, leading to a strange situation where old authors are named but not newer ones. So I propose to remove @author tags with people names from all our source files. +1 Additionally, if you agree with removing names, do you want source files to have: [X] no @author tag at all, Additionally, non-committers that have contributed significant portions of code and think they will lose visibility with this removal can make their voice heard. We will consider updating either the release notes or the credits file. I think this should be done automatically, not depending on their voices being raised or not. -- Stefano.
Re: [VOTE] Removing author tags
On Lun, 2 de Mayo de 2005, 16:52, Sylvain Wallez dijo: So I propose to remove @author tags with people names from all our source files. +1 Additionally, if you agree with removing names, do you want source files to have: [+0] no @author tag at all, [+0] @author The Cocoon development team [ ] @author . (something else) Additionally, non-committers that have contributed significant portions of code and think they will lose visibility with this removal can make their voice heard. We will consider updating either the release notes or the credits file. Same as Stefano, should be fair for people to include them somewhere. But we cannot remove the tags 100% automatically. There are some files, that seems to be taken from other parties. Best Regards, Antonio Gallardo
[Fwd: Re: [VOTE] Removing author tags]
Sorry if this shows up twice, but I posted it two hours ago and it still hasn't hit the list... Original Message Subject: Re: [VOTE] Removing author tags Date: Mon, 02 May 2005 16:28:11 -0700 From: Ralph Goers [EMAIL PROTECTED] To: dev@cocoon.apache.org References: [EMAIL PROTECTED] [EMAIL PROTECTED] Daniel Fagerstrom wrote: Sylvain Wallez wrote: So I propose to remove @author tags with people names from all our source files. +1 Well, I'm not really sure how to vote on this. I've pasted an email from Larry Rosen to the Apache Legal list that seems to say that the Cocoon source files should not have the Apache copyright in them, but instead have the copyright of the committers who made the contibution. Obviously, this is in direct contrast to what we are doing and frankly, I think its nuts. While this doesn't have a lot to do with the @author tags, per se, it does seem to indicate that the files should have a record of ownership. So before I add my +1 I'd at least like to know if our policy of attributing the copyrights to Apache and not the authors needs to be changed (at which point the @author tags could go away anyway). Ralph List-Help: mailto:[EMAIL PROTECTED] List-Unsubscribe: mailto:[EMAIL PROTECTED] List-Post: mailto:[EMAIL PROTECTED] List-Id: legal-discuss.apache.org Delivered-To: mailing list [EMAIL PROTECTED] From: Lawrence Rosen [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: RE: Copyright text, and javadoc license Date: Sat, 5 Mar 2005 08:24:06 -0800 Has there been any progress on the issue of Copyright [] The Apache Software Foundation or its licensors, as applicable vs Copyright (c) 2001-2004 - Apache Software Foundation? During the past few weeks Robyn Wagner, Jennifer Machovec, Jim Barnett and I discussed this issue via email. I drafted for their review an email that I proposed to send to legal-discuss to summarize the legal requirements for copyright notices on Apache works; I now step up to the plate and copy that summary below. Both Jennifer and Jim agree that the summary is legally correct, but they worry that the Apache members want to do it differently. I have suggested that lawyers should tell clients what the law is, but it is up to the clients to decide whether to follow the law. So here it is (with apologies for its length) for your review and discussion: * There have been concerns raised recently about copyright notices on software distributed by ASF. Here's basically what the law allows: We can place an ASF copyright notice on any original works of authorship authored or owned by the Apache Software Foundation, and nowhere else. Since we do not author contributions as such - our Contributors do! - which original works of authorship can actually bear the ASF copyright notice? An ASF copyright notice can be placed only (1) on the ASF website itself and on related expressive pronouncements of the ASF board of directors, its officers or agents created on behalf of ASF and published to the world as ASF's voice; (2) on the CVS data bases containing the Contributions collected, selected and arranged in accordance with ASF-authorized processes. The former are generally *original work* copyrights; the latter are *collective work* copyrights. (A more general term for collective works under US copyright law would be a *compilation work* but that's not an important distinction for this thread and would be confusing to all programmers.) In some cases, third parties or the ASF itself may create modifications of (1) and (2). Only if ASF itself does the modification may it (3) place its *derivative work* copyright notice on that work. See 17 USC 101. In all such cases, the copyright notice for ASF's copyrightable works published this year would be: Copyright 2005 Apache Software Foundation. The form of the ASF copyright notice is specified in 17 USC 401 to include just three components: the word Copyright, the year of first publication, and the name of the owner of the copyright in the work. It is never necessary to identify in the notice itself whether the claimed copyright is for an original work, a collective work, or a derivative work. Those details are not for the notice; instead, they are specified in an application for registration ASF may file with the Library of Congress - and which we must file if ASF ever intends to enforce its copyrights in federal court. (The topic of registering ASF's copyrights is reserved for another thread.) The confusion on this list has been over the collective (or compilation) work copyrights that Apache can rightfully claim in its collection of Contributions. Merely by collecting Contributions according to established and intelligent procedures, ASF has made a sufficient level of creative input to claim a collective work copyright in the entire collection of ASF code. The law is clear, however: ASF's copyright in a collective work does not extend
Re: [VOTE] Removing author tags
Daniel Fagerstrom wrote: Sylvain Wallez wrote: So I propose to remove @author tags with people names from all our source files. +1 Well, I'm not really sure how to vote on this. I've pasted an email from Larry Rosen to the Apache Legal list that seems to say that the Cocoon source files should not have the Apache copyright in them, but instead have the copyright of the committers who made the contibution. Obviously, this is in direct contrast to what we are doing and frankly, I think its nuts. While this doesn't have a lot to do with the @author tags, per se, it does seem to indicate that the files should have a record of ownership. So before I add my +1 I'd at least like to know if our policy of attributing the copyrights to Apache and not the authors needs to be changed (at which point the @author tags could go away anyway). Ralph List-Help: mailto:[EMAIL PROTECTED] List-Unsubscribe: mailto:[EMAIL PROTECTED] List-Post: mailto:[EMAIL PROTECTED] List-Id: legal-discuss.apache.org Delivered-To: mailing list [EMAIL PROTECTED] From: Lawrence Rosen [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: RE: Copyright text, and javadoc license Date: Sat, 5 Mar 2005 08:24:06 -0800 Has there been any progress on the issue of Copyright [] The Apache Software Foundation or its licensors, as applicable vs Copyright (c) 2001-2004 - Apache Software Foundation? During the past few weeks Robyn Wagner, Jennifer Machovec, Jim Barnett and I discussed this issue via email. I drafted for their review an email that I proposed to send to legal-discuss to summarize the legal requirements for copyright notices on Apache works; I now step up to the plate and copy that summary below. Both Jennifer and Jim agree that the summary is legally correct, but they worry that the Apache members want to do it differently. I have suggested that lawyers should tell clients what the law is, but it is up to the clients to decide whether to follow the law. So here it is (with apologies for its length) for your review and discussion: * There have been concerns raised recently about copyright notices on software distributed by ASF. Here's basically what the law allows: We can place an ASF copyright notice on any original works of authorship authored or owned by the Apache Software Foundation, and nowhere else. Since we do not author contributions as such - our Contributors do! - which original works of authorship can actually bear the ASF copyright notice? An ASF copyright notice can be placed only (1) on the ASF website itself and on related expressive pronouncements of the ASF board of directors, its officers or agents created on behalf of ASF and published to the world as ASF's voice; (2) on the CVS data bases containing the Contributions collected, selected and arranged in accordance with ASF-authorized processes. The former are generally *original work* copyrights; the latter are *collective work* copyrights. (A more general term for collective works under US copyright law would be a *compilation work* but that's not an important distinction for this thread and would be confusing to all programmers.) In some cases, third parties or the ASF itself may create modifications of (1) and (2). Only if ASF itself does the modification may it (3) place its *derivative work* copyright notice on that work. See 17 USC 101. In all such cases, the copyright notice for ASF's copyrightable works published this year would be: Copyright 2005 Apache Software Foundation. The form of the ASF copyright notice is specified in 17 USC 401 to include just three components: the word Copyright, the year of first publication, and the name of the owner of the copyright in the work. It is never necessary to identify in the notice itself whether the claimed copyright is for an original work, a collective work, or a derivative work. Those details are not for the notice; instead, they are specified in an application for registration ASF may file with the Library of Congress - and which we must file if ASF ever intends to enforce its copyrights in federal court. (The topic of registering ASF's copyrights is reserved for another thread.) The confusion on this list has been over the collective (or compilation) work copyrights that Apache can rightfully claim in its collection of Contributions. Merely by collecting Contributions according to established and intelligent procedures, ASF has made a sufficient level of creative input to claim a collective work copyright in the entire collection of ASF code. The law is clear, however: ASF's copyright in a collective work does not extend to the preexisting materials placed there by its Contributors. 17 USC 103. Whoever owns the copyrights in those Contributions retains that ownership despite their licensing it to ASF for inclusion into ASF's collective works. Some attorneys refer to the copyright in a collective work as thin because its owner can only prevent
Re: [VOTE] Removing author tags
Wow. it finally showed up. I wonder where it went in the meantime? Ralph Goers wrote: Daniel Fagerstrom wrote: Sylvain Wallez wrote: So I propose to remove @author tags with people names from all our source files. +1 Well, I'm not really sure how to vote on this. I've pasted an email from Larry Rosen to the Apache Legal list that seems to say that the Cocoon source files should not have the Apache copyright in them, but instead have the copyright of the committers who made the contibution. Obviously, this is in direct contrast to what we are doing and frankly, I think its nuts. While this doesn't have a lot to do with the @author tags, per se, it does seem to indicate that the files should have a record of ownership. So before I add my +1 I'd at least like to know if our policy of attributing the copyrights to Apache and not the authors needs to be changed (at which point the @author tags could go away anyway).
Re: [VOTE] Removing author tags
On Lun, 2 de Mayo de 2005, 18:28, Ralph Goers dijo: Daniel Fagerstrom wrote: Sylvain Wallez wrote: So I propose to remove @author tags with people names from all our source files. +1 Well, I'm not really sure how to vote on this. I've pasted an email from Larry Rosen to the Apache Legal list that seems to say that the Cocoon source files should not have the Apache copyright in them, but instead have the copyright of the committers who made the contibution. Obviously, this is in direct contrast to what we are doing and frankly, I think its nuts. While this doesn't have a lot to do with the @author tags, per se, it does seem to indicate that the files should have a record of ownership. So before I add my +1 I'd at least like to know if our policy of attributing the copyrights to Apache and not the authors needs to be changed (at which point the @author tags could go away anyway). Hmm... given the lastest facts (thanks Ralph!). Now is no clear what is the right thing to do. AFAIK a Contributor != an ASF committer. We should look for an explanation, please post to the legal@ for getting a final decision of this. Best Regards, Antonio Gallardo
Re: [VOTE] Removing author tags
Le 2 mai 05, à 23:52, Sylvain Wallez a écrit : ..So I propose to remove @author tags with people names from all our source files. +1 Additionally, if you agree with removing names, do you want source files to have: [X ] no @author tag at all, -Bertrand smime.p7s Description: S/MIME cryptographic signature
