Slashdot Mirror

← Back to Stories (view on slashdot.org)

Getting a Grip on Google Code

Posted by Zonk on from the improving-on-the-old dept.

netbuzz writes "Niall Kennedy reports on his blog that Guido van Rossum, author of the Python programming language, has begun showing off his first project since joining Google last year. 'Mondrian is a Web-based code-review system built on top of a Perforce and BigTable backend with a Python-powered front-end,' Kennedy writes. 'Mondrian is a pretty impressive system and is currently in use across Google.' Kennedy's description of Google's current code-review system sure makes it sound like it was in need of an upgrade. 'The Mondrian tool creates a much better workflow by creating task-specific dashboards, in-line commenting, well-tracked statistics, and more,' he writes. 'The application is built on top of Python open source libraries such as the Django framework, smtpd.py mail service, and the wsgiref Web server software.'"

3 of 91 comments (clear)

  1. Perforce? by Doctor+Memory · · Score: 4, Interesting

    Good idea, building on a closed-source SCMS that's (barely!) a mid-level player in the market. I can understand not wanting ClearCase, but what's wrong with CVS or Subversion? Hell, even Monotone or GNU Arch...

    Oh well, could be worse: they could have gone with StarTeam, PVCS or MKS Source Integrity...

    --
    Just junk food for thought...
  2. Re:Perforce? by panaceaa · · Score: 5, Interesting

    I'm not sure how you decided Perforce is a "barely mid-level player" in the SCM market. Adobe, Google, and Microsoft all use Perforce as their primary source code management solution. (Though Microsoft has highly modified it and calls it something else internally... but my contacts there tell me it's still Perforce underneath.) Perforce does have its problems with scalability, but in terms of merging, collaborating, viewing history, keeping branches, etc, etc, etc, it's pretty awesome.

    --
    my blog
  3. Re:Perforce? by slamb · · Score: 4, Interesting
    It means that (for example) while the hour-long checkpointing pre-backup process happens every night, you can't do any write operations.

    Let me be a little more specific: while the hour-long checkpointing process is happening, you can't even open files for edit. In addition to having really course locking, Perforce has more write operations than most version control systems. Subversion's CVS-style working copy means the only write operations are commits and revpropsets.