views:

148

answers:

2

Hi.

We have a large SVN repo of LaTeX documents. Each document ultimately is rendered into PDF.

Documents need to be reviewed. Review has two major goals: ensure the quality of text itself and ensure the qualify of typesetting.

Right now reviewer could be separated into two major groups:

  1. Those who use SVN to checkout sources and build PDFs for themselves, and submit results of review as SVN commits

  2. Those who get pre-built PDFs from ftp server and submit results as a free-form list of comments via email.

Document authors process the review results by processing \todo{} blocks in LaTeX code, by rolling back unneeded changes in SVN or incorporating free-form comments from e-mail into LaTeX sources.

Problem is, as the number of documents grow, it is very hard to keep track of the reviewers from the second group, and incorporate their suggestions in the timely and thorough manner.

Therefore, some nonsophisticated post-commit review solution is needed.

Requirements:

  1. Post-commit review

  2. All repository should be by default considered a review target without a need to specify files/line ranges for review.

  3. Support for anonymous comments/review results

  4. Reviews/comments should have status to facilitate processing

  5. Web-based

  6. Integration with SVN, so that new commits could automatically be incorporated in the review

  7. Open source/cusomizable

ReviewBoard, CodeStiker, plugins for trac, Rietveld, JCR - they all fail to satisfy some of those requirements. Besides, most of them are too complex for the need at hand.

Crucible is nice. It is complex, but could be made easy via customization. However price tag is a bit heavy.

What did I miss?

A: 
Charles Stewart
No, it's non-goverment non-profit. About 10 large docs per month, 40-50 pages, with extensive review.
ADEpt
And, subversion is not a bottlneck in the process right now, not at all.It was chosen as a "lowest common divisor" which everyone has, as opposed to git/hg/...
ADEpt
A: 

It seems like your requirements might be a little more complicated than you think if you've already looked at all those open source projects, and they all don't meet your requirements.

I agree with using a DVCS if you can. I use git to manage all my latex code, and it's awesome.

have you thought of using just a plain text file to store your reviews? You could use something like org-mode in emacs, set up relative links to your documents, time stamp your reviews, use the TODO status cycling to keep track of what's reviewed and whats not, and keep the reviews right along side the latex code, something like: document.tex and document_review.org,.txt or whatever. org-mode will publish to latex, html, and a few other formats.

Anyway, just a suggestion-- KISS principle at work!

Mica
As a matter of fact, I'm using org-mode to keep track of all reviews statuses right now :)However, reviewers come in different flavors, and not all of them would be happy (or able) to use emacs and/or git. I need something more user-friendly
ADEpt
lol. alright-- fair enough. I have a similar type problem at work-- so if you find a really good solution to this, please let me know!
Mica