Home > DrProject > Portals on Gears?

Portals on Gears?

January 3rd, 2008

Optimistic version control systems like CVS and Subversion allow people to decouple their work: instead of simultaneously editing the master copy of a file (and stomping on one another’s changes), each player changes a local copy, then merges it into the repository.  In contrast, most ticketing systems still use the “everything’s on the server” model: there’s no notion of a “local” copy of the ticket database.

But Google Gears has got me thinking: could we build portals like SourceForge and DrProject on a “write then merge” platform?  Would it improve performance?  Scaling?  Usability?  Or is it just a hammer looking for a walnut?  Any MSc students looking for a project out there?

DrProject

  1. Blaise Alleyne
    January 4th, 2008 at 04:38 | #1
    Reply | Quote

    Do you need something like Google Gears? Couldn’t the “write then merge” idea be implemented like it is with distributed version control systems like Linus’ git or Canonical’s Bazaar?

Comments are closed.