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 <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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
