From: Richard C. <ri...@cy...> - 2004-03-25 00:12:24
|
From: "Brian G. Peterson" <br...@ex...> > Of course it would be best for everyone if interested parties (such as > Justin) submitted patches to StatCVS to *add* Subversion support rather > than forking. My impression was that Justin wants to start from scratch and not fork the StatCvs codebase. Of course I would be totally delighted If he contributes Subversion support to StatCvs. But to be fair, I should mention that there are some good reasons for starting from scratch: First, Subversion logs are better suited to our purposes than CVS logs. They are XML and there are explicit changesets. So, much less to code before your program can generate the first interesting report. Second, you can't generate *all* StatCvs reports from Subversion logs (for example, the lines of codes chart are not possible because there are no explicit lines +/- information in the logs, if I'm not mistaken), which means that StatSvn reports would be only a subset of the StatCvs records, and you can't take advantage of *all* existing work in StatCvs. Third, Justin could choose some scripting language instead of Java. That could probably reduce development time. So, Brian and Tom have given good reasons for going with StatCvs, and there are good reasons for starting from scratch. Either way, I'm very interested in seeing what Justin comes up with. (And yes, I know that it's just an idea for now.) Richard |