+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 [EMAIL PROTECTED]
On 2/26/07, Scott O'Bryan [EMAIL PROTECTED] 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
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
yap !
-M
On 2/26/07, Matt Cooper [EMAIL PROTECTED] 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
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
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
