You are viewing a plain text version of this content. The canonical link for it is here.
Posted to adffaces-dev@incubator.apache.org by Matthias Wessendorf <ma...@apache.org> on 2007/02/26 10:19:52 UTC
Re: @author tags
moved discussion to dev, since this is a *public* topic
-M
On 2/25/07, Matthias Wessendorf <ma...@apache.org> wrote:
> Hi PPMC fellows,
>
> I'd like to plan to remove the @author tags in the code, since these
> aren't a good practice. For instance, when the @author tags belong to
> committers no longer active in the project so they no longer function
> as a "no trespassing" sign.
>
> Also on a incubator based discussion, Bill pointed out:
> <snip>
> In general, @author tags and attributions are poison to ASF-style
> collaboration, they are all about carving out niches in the code.
> The ASF-style development is about tearing down niches and promoting
> collaboration across an entire code base. Collaboration and ownership
> are generally mutually exclusive.
> </snip>
>
> What do you think?
> I am fine w/ removing them step by step (not now, but let's file a
> jira ticket, if you agree)
>
> Thanks,
> Matthias
>
> --
> Matthias Wessendorf
> http://tinyurl.com/fmywh
>
> further stuff:
> blog: http://jroller.com/page/mwessendorf
> mail: mwessendorf-at-gmail-dot-com
>
--
Matthias Wessendorf
http://tinyurl.com/fmywh
further stuff:
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com
Re: @author tags
Posted by Martin van den Bemt <ml...@mvdb.net>.
+1 to removing author tags.. I would like to see a contributors file though (adding to the pom would
probably a bit too much).
Btw there is a tool for this (relicense.pl), should probably be somewhere in the committers area I
guess :)
Mvgr,
Martin
Matthias Wessendorf wrote:
> moved discussion to dev, since this is a *public* topic
>
> -M
>
> On 2/25/07, Matthias Wessendorf <ma...@apache.org> wrote:
>> Hi PPMC fellows,
>>
>> I'd like to plan to remove the @author tags in the code, since these
>> aren't a good practice. For instance, when the @author tags belong to
>> committers no longer active in the project so they no longer function
>> as a "no trespassing" sign.
>>
>> Also on a incubator based discussion, Bill pointed out:
>> <snip>
>> In general, @author tags and attributions are poison to ASF-style
>> collaboration, they are all about carving out niches in the code.
>> The ASF-style development is about tearing down niches and promoting
>> collaboration across an entire code base. Collaboration and ownership
>> are generally mutually exclusive.
>> </snip>
>>
>> What do you think?
>> I am fine w/ removing them step by step (not now, but let's file a
>> jira ticket, if you agree)
>>
>> Thanks,
>> Matthias
>>
>> --
>> Matthias Wessendorf
>> http://tinyurl.com/fmywh
>>
>> further stuff:
>> blog: http://jroller.com/page/mwessendorf
>> mail: mwessendorf-at-gmail-dot-com
>>
>
>
Re: @author tags
Posted by Matthias Wessendorf <ma...@apache.org>.
to be honest;in an open source development, we all don't really like
to be bothered by something. We all are free to do what ever we want.
nobody of us want sb. to be his dev. leader. what we've done so far is
good. it is all up to US!!!
On 3/1/07, Simon Lessard <si...@gmail.com> wrote:
> Not exactly, SVN show only the name of the commiter, not the actual
> developper. However it's true that with SVN log you can get the JIRA issue
> number and then see who made the patch.
>
> On 3/1/07, Mike Kienenberger <mk...@gmail.com> wrote:
> >
> > There's already a system in place that tracks the changes and who made
> > them. It's called svn :-)
> > It's going to be far more accurate and complete than a system you
> > maintain manually :-)
> >
> > On 2/28/07, Simon Lessard <si...@gmail.com> wrote:
> > > I'm +0 about it. I think it's nice to know who wrote a piece of code
> > before
> > > you modify it, so you can ask a quick question to the author. The main
> > > example I can find in Trinidad is the use of Hashtable and Vector every
> > now
> > > and then, was it because of the old 1.2 codebase or was synchronization
> > > required? A simple mail to the author would have answered that question.
> > > Then again, I can see Craig's point as well as ASF concerns. The best
> > > compromise I can find is maintaining a history of changes in the Javadoc
> > > with the author names, but I really don't think many of us (starting
> > with
> > > me) will have the patience to keep such a thing up-to-date, hence the
> > +0.
> >
>
--
Matthias Wessendorf
http://tinyurl.com/fmywh
further stuff:
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com
Re: @author tags
Posted by Matthias Wessendorf <ma...@apache.org>.
also, the contrib. file, martin proposed is a good thing
-M
On 3/2/07, Adam Winer <aw...@gmail.com> wrote:
> We should be including the name of the patch author in
> every checkin message. I used to be in that habit,
> got out of it, and I'm trying to do a better job with it lately.
>
> -- Adam
>
>
> On 3/1/07, Simon Lessard <si...@gmail.com> wrote:
> >
> > Not exactly, SVN show only the name of the commiter, not the actual
> > developper. However it's true that with SVN log you can get the JIRA issue
> > number and then see who made the patch.
> >
> > On 3/1/07, Mike Kienenberger <mk...@gmail.com> wrote:
> > >
> > > There's already a system in place that tracks the changes and who made
> > > them. It's called svn :-)
> > > It's going to be far more accurate and complete than a system you
> > > maintain manually :-)
> > >
> > > On 2/28/07, Simon Lessard <si...@gmail.com> wrote:
> > > > I'm +0 about it. I think it's nice to know who wrote a piece of code
> > > before
> > > > you modify it, so you can ask a quick question to the author. The main
> > > > example I can find in Trinidad is the use of Hashtable and Vector
> > every
> > > now
> > > > and then, was it because of the old 1.2 codebase or was
> > synchronization
> > > > required? A simple mail to the author would have answered that
> > question.
> > > > Then again, I can see Craig's point as well as ASF concerns. The best
> > > > compromise I can find is maintaining a history of changes in the
> > Javadoc
> > > > with the author names, but I really don't think many of us (starting
> > > with
> > > > me) will have the patience to keep such a thing up-to-date, hence the
> > > +0.
> > >
> >
>
--
Matthias Wessendorf
http://tinyurl.com/fmywh
further stuff:
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com
Re: @author tags
Posted by Adam Winer <aw...@gmail.com>.
We should be including the name of the patch author in
every checkin message. I used to be in that habit,
got out of it, and I'm trying to do a better job with it lately.
-- Adam
On 3/1/07, Simon Lessard <si...@gmail.com> wrote:
>
> Not exactly, SVN show only the name of the commiter, not the actual
> developper. However it's true that with SVN log you can get the JIRA issue
> number and then see who made the patch.
>
> On 3/1/07, Mike Kienenberger <mk...@gmail.com> wrote:
> >
> > There's already a system in place that tracks the changes and who made
> > them. It's called svn :-)
> > It's going to be far more accurate and complete than a system you
> > maintain manually :-)
> >
> > On 2/28/07, Simon Lessard <si...@gmail.com> wrote:
> > > I'm +0 about it. I think it's nice to know who wrote a piece of code
> > before
> > > you modify it, so you can ask a quick question to the author. The main
> > > example I can find in Trinidad is the use of Hashtable and Vector
> every
> > now
> > > and then, was it because of the old 1.2 codebase or was
> synchronization
> > > required? A simple mail to the author would have answered that
> question.
> > > Then again, I can see Craig's point as well as ASF concerns. The best
> > > compromise I can find is maintaining a history of changes in the
> Javadoc
> > > with the author names, but I really don't think many of us (starting
> > with
> > > me) will have the patience to keep such a thing up-to-date, hence the
> > +0.
> >
>
Re: @author tags
Posted by Simon Lessard <si...@gmail.com>.
Not exactly, SVN show only the name of the commiter, not the actual
developper. However it's true that with SVN log you can get the JIRA issue
number and then see who made the patch.
On 3/1/07, Mike Kienenberger <mk...@gmail.com> wrote:
>
> There's already a system in place that tracks the changes and who made
> them. It's called svn :-)
> It's going to be far more accurate and complete than a system you
> maintain manually :-)
>
> On 2/28/07, Simon Lessard <si...@gmail.com> wrote:
> > I'm +0 about it. I think it's nice to know who wrote a piece of code
> before
> > you modify it, so you can ask a quick question to the author. The main
> > example I can find in Trinidad is the use of Hashtable and Vector every
> now
> > and then, was it because of the old 1.2 codebase or was synchronization
> > required? A simple mail to the author would have answered that question.
> > Then again, I can see Craig's point as well as ASF concerns. The best
> > compromise I can find is maintaining a history of changes in the Javadoc
> > with the author names, but I really don't think many of us (starting
> with
> > me) will have the patience to keep such a thing up-to-date, hence the
> +0.
>
Re: @author tags
Posted by Mike Kienenberger <mk...@gmail.com>.
There's already a system in place that tracks the changes and who made
them. It's called svn :-)
It's going to be far more accurate and complete than a system you
maintain manually :-)
On 2/28/07, Simon Lessard <si...@gmail.com> wrote:
> I'm +0 about it. I think it's nice to know who wrote a piece of code before
> you modify it, so you can ask a quick question to the author. The main
> example I can find in Trinidad is the use of Hashtable and Vector every now
> and then, was it because of the old 1.2 codebase or was synchronization
> required? A simple mail to the author would have answered that question.
> Then again, I can see Craig's point as well as ASF concerns. The best
> compromise I can find is maintaining a history of changes in the Javadoc
> with the author names, but I really don't think many of us (starting with
> me) will have the patience to keep such a thing up-to-date, hence the +0.
Re: @author tags
Posted by Matthias Wessendorf <ma...@apache.org>.
On 3/1/07, Simon Lessard <si...@gmail.com> wrote:
> I'm +0 about it. I think it's nice to know who wrote a piece of code before
> you modify it, so you can ask a quick question to the author. The main
that quick question, really belongs to the mailing list.
> example I can find in Trinidad is the use of Hashtable and Vector every now
> and then, was it because of the old 1.2 codebase or was synchronization
> required? A simple mail to the author would have answered that question.
> Then again, I can see Craig's point as well as ASF concerns. The best
> compromise I can find is maintaining a history of changes in the Javadoc
> with the author names, but I really don't think many of us (starting with
> me) will have the patience to keep such a thing up-to-date, hence the +0.
Well, for now, I'll create an issue in jira to make sure that we will remove
these tags.
-M
> On 2/28/07, Adam Winer <aw...@gmail.com> wrote:
> >
> > I agree as well. There's something a little nice about
> > @author tags as a way of giving credit to the people
> > who aren't the obvious people on a project. But they're
> > rarely kept up to date, and the implication of ownership
> > is not very OSS-friendly.
> >
> > -- Adam
> >
> >
> > On 2/26/07, Craig McClanahan <cr...@apache.org> wrote:
> > > On 2/26/07, Scott O'Bryan <da...@gmail.com> wrote:
> > > > -1 for removing them. I don't see this as an "ownership" issue. It's
> > > > helpful to know who in the community might be able to answer questions
> > > > on a particular piece of code. I know with the Portal work I did, it
> > > > was very handy to know WHO had written a piece of code, especially
> > since
> > > > they may not me monitoring the lists.
> > > >
> > >
> > > This argument does not scale in the long term. My own experience is a
> > > case in point -- my name is still splattered over lots of the Catalina
> > > sources inside Tomcat, even though:
> > >
> > > * I have not worked on them for four years (but I still get >20 personal
> > > emails for Tomcat help every week).
> > >
> > > * In many cases, the number of lines of code that were "mine" originally
> > > is less than half of the total -- so the tag is totally misleading.
> > >
> > > * The real people you want to talk to are the ones who have been making
> > > recent commits, not whoever wrote the code in the first place.
> > >
> > > I am strongly i+1 on removing @author tags, for the community related
> > > reasons that have been previously published.
> > >
> > > Craig McClanahan
> > >
> >
>
--
Matthias Wessendorf
http://tinyurl.com/fmywh
further stuff:
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com
Re: @author tags
Posted by Simon Lessard <si...@gmail.com>.
I'm +0 about it. I think it's nice to know who wrote a piece of code before
you modify it, so you can ask a quick question to the author. The main
example I can find in Trinidad is the use of Hashtable and Vector every now
and then, was it because of the old 1.2 codebase or was synchronization
required? A simple mail to the author would have answered that question.
Then again, I can see Craig's point as well as ASF concerns. The best
compromise I can find is maintaining a history of changes in the Javadoc
with the author names, but I really don't think many of us (starting with
me) will have the patience to keep such a thing up-to-date, hence the +0.
On 2/28/07, Adam Winer <aw...@gmail.com> wrote:
>
> I agree as well. There's something a little nice about
> @author tags as a way of giving credit to the people
> who aren't the obvious people on a project. But they're
> rarely kept up to date, and the implication of ownership
> is not very OSS-friendly.
>
> -- Adam
>
>
> On 2/26/07, Craig McClanahan <cr...@apache.org> wrote:
> > On 2/26/07, Scott O'Bryan <da...@gmail.com> wrote:
> > > -1 for removing them. I don't see this as an "ownership" issue. It's
> > > helpful to know who in the community might be able to answer questions
> > > on a particular piece of code. I know with the Portal work I did, it
> > > was very handy to know WHO had written a piece of code, especially
> since
> > > they may not me monitoring the lists.
> > >
> >
> > This argument does not scale in the long term. My own experience is a
> > case in point -- my name is still splattered over lots of the Catalina
> > sources inside Tomcat, even though:
> >
> > * I have not worked on them for four years (but I still get >20 personal
> > emails for Tomcat help every week).
> >
> > * In many cases, the number of lines of code that were "mine" originally
> > is less than half of the total -- so the tag is totally misleading.
> >
> > * The real people you want to talk to are the ones who have been making
> > recent commits, not whoever wrote the code in the first place.
> >
> > I am strongly i+1 on removing @author tags, for the community related
> > reasons that have been previously published.
> >
> > Craig McClanahan
> >
>
Re: @author tags
Posted by Adam Winer <aw...@gmail.com>.
I agree as well. There's something a little nice about
@author tags as a way of giving credit to the people
who aren't the obvious people on a project. But they're
rarely kept up to date, and the implication of ownership
is not very OSS-friendly.
-- Adam
On 2/26/07, Craig McClanahan <cr...@apache.org> wrote:
> On 2/26/07, Scott O'Bryan <da...@gmail.com> wrote:
> > -1 for removing them. I don't see this as an "ownership" issue. It's
> > helpful to know who in the community might be able to answer questions
> > on a particular piece of code. I know with the Portal work I did, it
> > was very handy to know WHO had written a piece of code, especially since
> > they may not me monitoring the lists.
> >
>
> This argument does not scale in the long term. My own experience is a
> case in point -- my name is still splattered over lots of the Catalina
> sources inside Tomcat, even though:
>
> * I have not worked on them for four years (but I still get >20 personal
> emails for Tomcat help every week).
>
> * In many cases, the number of lines of code that were "mine" originally
> is less than half of the total -- so the tag is totally misleading.
>
> * The real people you want to talk to are the ones who have been making
> recent commits, not whoever wrote the code in the first place.
>
> I am strongly i+1 on removing @author tags, for the community related
> reasons that have been previously published.
>
> Craig McClanahan
>
Re: @author tags
Posted by Scott O'Bryan <da...@gmail.com>.
Well the community seems to have spoken. I've just had the benefit of
dealing with a "niche" set of usecases and it helped to be able to track
down the original developer of some of the code because they no longer
monitor the lists. The snv blame tool (in ASF) pretty much tells you
who committed the code, not who knows it. Still, I do see the
compelling arguments to the contrary. I still hold though that @author
does not equal "owner" and that a community like Apache just needs to
get over that view of the world.
That being said, I suppose I don't feel too strongly about it. If
nobody knows about the code in general then chances are nobodies using
or maintaining the code and it's probably time to develop some new
expertise anyway. So I'll move to a +0 non-binding.
Scott
Matthias Wessendorf wrote:
>> My personal policy is to redirect personal appeals for help to the
>> appropriate user mailing list. I would encourage other developers who
>> receive individual help requests to do the same.
>
> +1
> doing the same. not getting 20 a day/week like you, but the pattern is
> a good one
>
> -M
>
>> Craig
>>
>>
>> > On 2/26/07, Matthias Wessendorf <ma...@apache.org> wrote:
>> > >
>> > > > * I have not worked on them for four years (but I still get >20
>> personal
>> > > > emails for Tomcat help every week).
>> > >
>> > > :-)
>> > >
>> > > but to be serious, here is something that Ted brought up on the same
>> > > discussion, which I also started over in MyFaces land
>> > >
>> > > <snip>
>> > > As to why, Greg Stein sums it up well here:
>> > >
>> > > * http://tinyurl.com/mw7t6
>> > >
>> > > This issues has been discussed at length on the board and member
>> > > lists, and the ASF does prefer that our code be free of author tags,
>> > > but we leave the final determination to the individual PMCs.
>> > > </snip>
>> > >
>> >
>>
>
>
Re: @author tags
Posted by Matthias Wessendorf <ma...@apache.org>.
> My personal policy is to redirect personal appeals for help to the
> appropriate user mailing list. I would encourage other developers who
> receive individual help requests to do the same.
+1
doing the same. not getting 20 a day/week like you, but the pattern is
a good one
-M
> Craig
>
>
> > On 2/26/07, Matthias Wessendorf <ma...@apache.org> wrote:
> > >
> > > > * I have not worked on them for four years (but I still get >20 personal
> > > > emails for Tomcat help every week).
> > >
> > > :-)
> > >
> > > but to be serious, here is something that Ted brought up on the same
> > > discussion, which I also started over in MyFaces land
> > >
> > > <snip>
> > > As to why, Greg Stein sums it up well here:
> > >
> > > * http://tinyurl.com/mw7t6
> > >
> > > This issues has been discussed at length on the board and member
> > > lists, and the ASF does prefer that our code be free of author tags,
> > > but we leave the final determination to the individual PMCs.
> > > </snip>
> > >
> >
>
--
Matthias Wessendorf
http://tinyurl.com/fmywh
further stuff:
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com
Re: @author tags
Posted by Craig McClanahan <cr...@apache.org>.
On 2/26/07, Matt Cooper <ma...@gmail.com> wrote:
> If you are looking to see who wrote a particular line of code, you can use
> SVN's blame tool which will also show you see the commit description which
> is helpful to see even who donated the code if a committer did the
> check-in. I think blame is more accurate than @author since it doesn't
> require a human to maintain up-to-date status of who committed the lines of
> code.
>
One point I left out of my earlier comments is also relevant here --
the communication itself should really be done on the mailing list
anyway (rather than a direct email to the author). That way, everyone
will be able to benefit from seeing the question asked and answered.
My personal policy is to redirect personal appeals for help to the
appropriate user mailing list. I would encourage other developers who
receive individual help requests to do the same.
Craig
> On 2/26/07, Matthias Wessendorf <ma...@apache.org> wrote:
> >
> > > * I have not worked on them for four years (but I still get >20 personal
> > > emails for Tomcat help every week).
> >
> > :-)
> >
> > but to be serious, here is something that Ted brought up on the same
> > discussion, which I also started over in MyFaces land
> >
> > <snip>
> > As to why, Greg Stein sums it up well here:
> >
> > * http://tinyurl.com/mw7t6
> >
> > This issues has been discussed at length on the board and member
> > lists, and the ASF does prefer that our code be free of author tags,
> > but we leave the final determination to the individual PMCs.
> > </snip>
> >
>
Re: @author tags
Posted by Matthias Wessendorf <ma...@apache.org>.
yap !
-M
On 2/26/07, Matt Cooper <ma...@gmail.com> wrote:
> If you are looking to see who wrote a particular line of code, you can use
> SVN's blame tool which will also show you see the commit description which
> is helpful to see even who donated the code if a committer did the
> check-in. I think blame is more accurate than @author since it doesn't
> require a human to maintain up-to-date status of who committed the lines of
> code.
>
> On 2/26/07, Matthias Wessendorf <ma...@apache.org> wrote:
> >
> > > * I have not worked on them for four years (but I still get >20 personal
> > > emails for Tomcat help every week).
> >
> > :-)
> >
> > but to be serious, here is something that Ted brought up on the same
> > discussion, which I also started over in MyFaces land
> >
> > <snip>
> > As to why, Greg Stein sums it up well here:
> >
> > * http://tinyurl.com/mw7t6
> >
> > This issues has been discussed at length on the board and member
> > lists, and the ASF does prefer that our code be free of author tags,
> > but we leave the final determination to the individual PMCs.
> > </snip>
> >
>
--
Matthias Wessendorf
http://tinyurl.com/fmywh
further stuff:
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com
Re: @author tags
Posted by Matt Cooper <ma...@gmail.com>.
If you are looking to see who wrote a particular line of code, you can use
SVN's blame tool which will also show you see the commit description which
is helpful to see even who donated the code if a committer did the
check-in. I think blame is more accurate than @author since it doesn't
require a human to maintain up-to-date status of who committed the lines of
code.
On 2/26/07, Matthias Wessendorf <ma...@apache.org> wrote:
>
> > * I have not worked on them for four years (but I still get >20 personal
> > emails for Tomcat help every week).
>
> :-)
>
> but to be serious, here is something that Ted brought up on the same
> discussion, which I also started over in MyFaces land
>
> <snip>
> As to why, Greg Stein sums it up well here:
>
> * http://tinyurl.com/mw7t6
>
> This issues has been discussed at length on the board and member
> lists, and the ASF does prefer that our code be free of author tags,
> but we leave the final determination to the individual PMCs.
> </snip>
>
Re: @author tags
Posted by Matthias Wessendorf <ma...@apache.org>.
> * I have not worked on them for four years (but I still get >20 personal
> emails for Tomcat help every week).
:-)
but to be serious, here is something that Ted brought up on the same
discussion, which I also started over in MyFaces land
<snip>
As to why, Greg Stein sums it up well here:
* http://tinyurl.com/mw7t6
This issues has been discussed at length on the board and member
lists, and the ASF does prefer that our code be free of author tags,
but we leave the final determination to the individual PMCs.
</snip>
Re: @author tags
Posted by Craig McClanahan <cr...@apache.org>.
On 2/26/07, Scott O'Bryan <da...@gmail.com> wrote:
> -1 for removing them. I don't see this as an "ownership" issue. It's
> helpful to know who in the community might be able to answer questions
> on a particular piece of code. I know with the Portal work I did, it
> was very handy to know WHO had written a piece of code, especially since
> they may not me monitoring the lists.
>
This argument does not scale in the long term. My own experience is a
case in point -- my name is still splattered over lots of the Catalina
sources inside Tomcat, even though:
* I have not worked on them for four years (but I still get >20 personal
emails for Tomcat help every week).
* In many cases, the number of lines of code that were "mine" originally
is less than half of the total -- so the tag is totally misleading.
* The real people you want to talk to are the ones who have been making
recent commits, not whoever wrote the code in the first place.
I am strongly i+1 on removing @author tags, for the community related
reasons that have been previously published.
Craig McClanahan
Re: @author tags
Posted by Scott O'Bryan <da...@gmail.com>.
BTW, this was non-binding.. Sorry/
Scott O'Bryan wrote:
> -1 for removing them. I don't see this as an "ownership" issue. It's
> helpful to know who in the community might be able to answer questions
> on a particular piece of code. I know with the Portal work I did, it
> was very handy to know WHO had written a piece of code, especially
> since they may not me monitoring the lists.
>
> Matt Cooper wrote:
>> +1 (non-binding) for removing them. I am very thankful for code that
>> people
>> donate to the project. However, in team/community settings I feel
>> ideally
>> that code "belongs" to everyone since it is everyone's responsibility to
>> maintain the code.
>>
>> On 2/26/07, Matthias Wessendorf <ma...@apache.org> wrote:
>>>
>>> moved discussion to dev, since this is a *public* topic
>>>
>>> -M
>>>
>>> On 2/25/07, Matthias Wessendorf <ma...@apache.org> wrote:
>>> > Hi PPMC fellows,
>>> >
>>> > I'd like to plan to remove the @author tags in the code, since these
>>> > aren't a good practice. For instance, when the @author tags
>>> belong to
>>> > committers no longer active in the project so they no longer function
>>> > as a "no trespassing" sign.
>>> >
>>> > Also on a incubator based discussion, Bill pointed out:
>>> > <snip>
>>> > In general, @author tags and attributions are poison to ASF-style
>>> > collaboration, they are all about carving out niches in the code.
>>> > The ASF-style development is about tearing down niches and promoting
>>> > collaboration across an entire code base. Collaboration and
>>> ownership
>>> > are generally mutually exclusive.
>>> > </snip>
>>> >
>>> > What do you think?
>>> > I am fine w/ removing them step by step (not now, but let's file a
>>> > jira ticket, if you agree)
>>> >
>>> > Thanks,
>>> > Matthias
>>> >
>>> > --
>>> > Matthias Wessendorf
>>> > http://tinyurl.com/fmywh
>>> >
>>> > further stuff:
>>> > blog: http://jroller.com/page/mwessendorf
>>> > mail: mwessendorf-at-gmail-dot-com
>>> >
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>> http://tinyurl.com/fmywh
>>>
>>> further stuff:
>>> blog: http://jroller.com/page/mwessendorf
>>> mail: mwessendorf-at-gmail-dot-com
>>>
>>
>
>
Re: @author tags
Posted by Scott O'Bryan <da...@gmail.com>.
-1 for removing them. I don't see this as an "ownership" issue. It's
helpful to know who in the community might be able to answer questions
on a particular piece of code. I know with the Portal work I did, it
was very handy to know WHO had written a piece of code, especially since
they may not me monitoring the lists.
Matt Cooper wrote:
> +1 (non-binding) for removing them. I am very thankful for code that
> people
> donate to the project. However, in team/community settings I feel
> ideally
> that code "belongs" to everyone since it is everyone's responsibility to
> maintain the code.
>
> On 2/26/07, Matthias Wessendorf <ma...@apache.org> wrote:
>>
>> moved discussion to dev, since this is a *public* topic
>>
>> -M
>>
>> On 2/25/07, Matthias Wessendorf <ma...@apache.org> wrote:
>> > Hi PPMC fellows,
>> >
>> > I'd like to plan to remove the @author tags in the code, since these
>> > aren't a good practice. For instance, when the @author tags belong to
>> > committers no longer active in the project so they no longer function
>> > as a "no trespassing" sign.
>> >
>> > Also on a incubator based discussion, Bill pointed out:
>> > <snip>
>> > In general, @author tags and attributions are poison to ASF-style
>> > collaboration, they are all about carving out niches in the code.
>> > The ASF-style development is about tearing down niches and promoting
>> > collaboration across an entire code base. Collaboration and ownership
>> > are generally mutually exclusive.
>> > </snip>
>> >
>> > What do you think?
>> > I am fine w/ removing them step by step (not now, but let's file a
>> > jira ticket, if you agree)
>> >
>> > Thanks,
>> > Matthias
>> >
>> > --
>> > Matthias Wessendorf
>> > http://tinyurl.com/fmywh
>> >
>> > further stuff:
>> > blog: http://jroller.com/page/mwessendorf
>> > mail: mwessendorf-at-gmail-dot-com
>> >
>>
>>
>> --
>> Matthias Wessendorf
>> http://tinyurl.com/fmywh
>>
>> further stuff:
>> blog: http://jroller.com/page/mwessendorf
>> mail: mwessendorf-at-gmail-dot-com
>>
>
Re: @author tags
Posted by Matt Cooper <ma...@gmail.com>.
+1 (non-binding) for removing them. I am very thankful for code that people
donate to the project. However, in team/community settings I feel ideally
that code "belongs" to everyone since it is everyone's responsibility to
maintain the code.
On 2/26/07, Matthias Wessendorf <ma...@apache.org> wrote:
>
> moved discussion to dev, since this is a *public* topic
>
> -M
>
> On 2/25/07, Matthias Wessendorf <ma...@apache.org> wrote:
> > Hi PPMC fellows,
> >
> > I'd like to plan to remove the @author tags in the code, since these
> > aren't a good practice. For instance, when the @author tags belong to
> > committers no longer active in the project so they no longer function
> > as a "no trespassing" sign.
> >
> > Also on a incubator based discussion, Bill pointed out:
> > <snip>
> > In general, @author tags and attributions are poison to ASF-style
> > collaboration, they are all about carving out niches in the code.
> > The ASF-style development is about tearing down niches and promoting
> > collaboration across an entire code base. Collaboration and ownership
> > are generally mutually exclusive.
> > </snip>
> >
> > What do you think?
> > I am fine w/ removing them step by step (not now, but let's file a
> > jira ticket, if you agree)
> >
> > Thanks,
> > Matthias
> >
> > --
> > Matthias Wessendorf
> > http://tinyurl.com/fmywh
> >
> > further stuff:
> > blog: http://jroller.com/page/mwessendorf
> > mail: mwessendorf-at-gmail-dot-com
> >
>
>
> --
> Matthias Wessendorf
> http://tinyurl.com/fmywh
>
> further stuff:
> blog: http://jroller.com/page/mwessendorf
> mail: mwessendorf-at-gmail-dot-com
>