Thomas Moschny wrote:
2008/6/2, Jeff Hammel <[EMAIL PROTECTED]>:For what its worth from a first time mailer to this list, I am glad trac does not import its wiki pages into an svn repo by default. For my mileage, this would be clunkier (but I'm sure I have different wiki needs than others).It is not clear to me how saving wiki pages in svn (or any other vc backend) could be clunkier, given the fact that wiki pages are simply versioned text pages. So, while using the real vcs for the projects 'first class' contents, Trac is implementing its own version control for the wiki pages (and other things, like attachments) and is thus duplicating efforts. Imho *that* is clunkier.
Clunkiness is not the issue, we do not wish to require Subversion in order to use Trac. It is better to reinvient a bit of the wheel in 100 lines of code, than force you to install a much much larger package (plus its deps, etc). There is also the issue that Trac supports other SCMs, and making a cross-SCM API for both reading and writing is very tricky. Everyone does things just a bit differently, even unifying the read-only APi is a stretch much of the time. I am not going to argue that versioning project data is bad idea, just that for most projects a full SCM is vast overkill for this. dSCMs are still very much an emerging technology, and distributed bug tracking even more so. Time will tell if it works in the general case.
--Noah
signature.asc
Description: OpenPGP digital signature
