You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Sylvain Wallez <sy...@anyware-tech.com> on 2005/05/02 23:52:50 UTC
[VOTE] Removing author tags
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.
Additionally, if you agree with removing names, do you want source files
to have:
[ ] 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.
Sylvain
[1] http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=107783914605693&w=2
[2] http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=108089900026744&w=2
--
Sylvain Wallez Anyware Technologies
http://apache.org/~sylvain http://anyware-tech.com
Apache Software Foundation Member Research & Technology Director
Re: [VOTE] Removing author tags
Posted by Jeremy Quinn <je...@apache.org>.
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 !!!!!
--------------------------------------------------------
Re: [VOTE] Removing author tags
Posted by Sylvain Wallez <sy...@apache.org>.
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 Wallez Anyware Technologies
http://apache.org/~sylvain http://anyware-tech.com
Apache Software Foundation Member Research & Technology Director
Re: [VOTE] Removing author tags
Posted by Leszek Gawron <lg...@apache.org>.
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
lgawron@apache.org http://www.mobilebox.pl
Re: [VOTE] Removing author tags
Posted by Gianugo Rabellino <gi...@gmail.com>.
On 5/2/05, Sylvain Wallez <sy...@anyware-tech.com> 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
Posted by Antonio Gallardo <ag...@agssa.net>.
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
Re: [VOTE] Removing author tags
Posted by Geoff Howard <ge...@gmail.com>.
On 5/2/05, Sylvain Wallez <sy...@anyware-tech.com> 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
Posted by Ugo Cei <ug...@apache.org>.
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/
Re: [VOTE] Removing author tags
Posted by Antonio Gallardo <ag...@agssa.net>.
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
Posted by Ralph Goers <Ra...@dslextreme.com>.
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
Posted by Niclas Hedhman <ni...@hedhman.org>.
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
Posted by Sylvain Wallez <sy...@apache.org>.
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 Wallez Anyware Technologies
http://apache.org/~sylvain http://anyware-tech.com
Apache Software Foundation Member Research & Technology Director
Re: [VOTE] Removing author tags
Posted by Niclas Hedhman <ni...@hedhman.org>.
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
Posted by Ralph Goers <Ra...@dslextreme.com>.
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
Posted by Sylvain Wallez <sy...@apache.org>.
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 Wallez Anyware Technologies
http://apache.org/~sylvain http://anyware-tech.com
Apache Software Foundation Member Research & Technology Director
Re: [VOTE] Removing author tags
Posted by Ralph Goers <Ra...@dslextreme.com>.
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: <ma...@apache.org>
List-Unsubscribe: <ma...@apache.org>
List-Post: <ma...@apache.org>
List-Id: <legal-discuss.apache.org>
Delivered-To: mailing list legal-discuss@apache.org
From: "Lawrence Rosen" <lr...@rosenlaw.com>
To: <sk...@apache.org>, <le...@apache.org>
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 [yyyy] 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 infringement of the collective
work itself, not of the individual components. Even thin copyrights can be
very valuable, however, because of the additional effects of trademark
protection (e.g., the Apache brand) and the persuasive authority of a
respected board of directors and the community of Contributors it
represents.
Every Contributor should be encouraged to place appropriate copyright
notices in the source code of its own copyrightable works at the time of its
contribution. ASF is not responsible for doing so, nor is it responsible for
the accuracy of those notices placed in source code by its Contributors. The
Apache Software License effectively disclaims the warranty of
non-infringement, so other people's copyright disputes are not our legal
concern. Furthermore, ASF's Contributor Agreements protect ASF from
liability.
Any downstream recipient of ASF's collective works takes those works subject
to all upstream licenses even if the only copyright notice appearing on the
work is that reflecting the ASF *collective work* copyright. Any downstream
recipient is on notice that the software cannot be copied except under the
terms and conditions specified in the Apache Software License. The ASF
website contains all important license notices and text. The source code
with the original copyright notices supplied by the Contributors is
available on ASF's website for all to see. No responsible commercial entity
who mattered would dare claim ignorance of Apache's license and processes.
ASF's copyright notice is all the notice needed, because our copyrightable
work is available only under the terms of our license, which explains the
rules for all.
ASF will not remove (indeed, should not remove) any pre-existing copyright
notices. This rule applies to contributed source code only. Downstream
licensees are entitled to that information so they can know their rights and
obligations, particularly if they use the source code to create derivative
works. But there is no requirement to publish the original copyright notices
when "compiling" source code into executable code or when distributing
executable versions of software. Such transformations are derivative works
owned by ASF or by the person who performed the transformations, and deserve
a new copyright notice.
Once again, the only legitimate places where ASF may place its copyright
notice are on its website, on its publications, and on its collected data
bases of contributed software. In the latter situation, ASF may claim a
collective work copyright by virtue simply of having collected it. In all
such cases, the only legitimate ASF copyright notice is:
Copyright 2005 Apache Software Foundation.
************************************
I also copy below the email exchange between Jennifer and me about the
expressed desire of Apache members to remove copyright noticed placed by
Contributors into their contributions for Apache. That correspondence is
copied below, with Jennifer's note at the bottom and my response above it:
Hi Jennifer,
Thanks for your input and for explaining the history that guided your
previous decisions.
You are absolutely right that it would be improper to place an ASF copyright
notice on files that are "contributed in their entirety and are not modified
by ASF or other contributors." What I don't then understand is why the ASF
should want to change those existing copyright notices at all. Just leave
them alone.
Regardless of the "*very* strong feeling" by ASF members that they want to
highlight the ASF identity rather than that of the contributors, modifying
or removing existing copyright notices in source code of contributions is
not the way to do that. It has the great disadvantage of obscuring the
provenance of the code, and it can lead to misunderstandings and grievances
later if contributors should want to use their own code in other ways. No
matter how adamant the members and board are, it is appropriate for lawyers
like us to say "you shouldn't be doing that."
If copyright owners like BEA and IBM acquiesce in the removal of their own
copyright notices, they may be denying themselves the full protection of the
copyright law. (See 17 USC 405(e).) And they needn't do so as long as a
*valid* Apache copyright notice is placed on the entire collective work.
(See 17 USC 404(a).)
You were concerned about the location of the Apache copyright notices on the
collective work. I'm not sure why that's become such an issue. The Apache
website is where that code is made available. What's wrong with a standard
Apache copyright notice on every such download page?
I'm certainly willing to take this issue back to ASF for reconsideration. If
I didn't feel strongly about this point I wouldn't have spent as much time
as I already did trying to explain it. My objective in reviewing the draft
with you all first was to see if perhaps we attorneys could present a common
front at least as to the interpretation of the law. Then, as we all know, if
the client still insists on doing foolish or bizarre things, it isn't our
fault.
/Larry
Re: [VOTE] Removing author tags
Posted by Daniel Fagerstrom <da...@nada.kth.se>.
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
Posted by Reinhard Poetz <re...@apache.org>.
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-dev&m=107783914605693&w=2
> [2] http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=108089900026744&w=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
Posted by Dirk-Willem van Gulik <di...@webweaving.org>.
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
Posted by Sylvain Wallez <sy...@apache.org>.
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 Wallez Anyware Technologies
http://apache.org/~sylvain http://anyware-tech.com
Apache Software Foundation Member Research & Technology Director
Re: [VOTE] Removing author tags
Posted by Sylvain Wallez <sy...@apache.org>.
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 Wallez Anyware Technologies
http://apache.org/~sylvain http://anyware-tech.com
Apache Software Foundation Member Research & Technology Director
Re: [VOTE] Removing author tags
Posted by Nicola Ken Barozzi <ni...@apache.org>.
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 nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: [VOTE] Removing author tags
Posted by Vadim Gritsenko <va...@reverycodes.com>.
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
Posted by Sylvain Wallez <sy...@apache.org>.
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 Wallez Anyware Technologies
http://apache.org/~sylvain http://anyware-tech.com
Apache Software Foundation Member Research & Technology Director
Re: [VOTE] Removing author tags
Posted by Stefano Mazzocchi <st...@apache.org>.
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
Posted by David Crossley <cr...@apache.org>.
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
Posted by Ugo Cei <ug...@apache.org>.
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/
Re: [VOTE] Removing author tags
Posted by Bertrand Delacretaz <bd...@apache.org>.
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
Re: [VOTE] Removing author tags
Posted by Andrew Savory <an...@luminas.co.uk>.
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
Posted by Giacomo Pati <gi...@apache.org>.
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