news/2008/0623-git.xhtml

   1 <?xml version="1.0" encoding="UTF-8"?>
   2 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
   3   "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
   4 <html
   5   xmlns="http://www.w3.org/1999/xhtml"
   6   xmlns:xi="http://www.w3.org/2001/XInclude"
   7   xmlns:xc="urn:xhtml-compiler"
   8   xml:lang="en">
   9 <head>
  10   <title>Switching to Git - News - HTML Purifier</title>
  11   <xi:include href="common-meta.xml" xpointer="xpointer(/*/node())" />
  12   <meta name="Date" content="Mon, 23 June 2008 22:42:00 EST" />
  13 </head>
  14 <body>
  15
  16 <xi:include href="common-header.xml" xpointer="xpointer(/*/node())" />
  17 <h1 id="title">Switching to Git</h1>
  18
  19 <div id="content">
  20   <p>
  21     After several weeks of testing, HTML Purifier is proud to announce that
  22     it will be switching to Git as its source control management system.
  23     Git offers a number of advantages over Subversion:
  24   </p>
  25   <ul>
  26     <li>
  27       <em>Superior support for branchy development.</em> Subversion 1.5 introduces
  28       merge-tracking which somewhat diminishes this benefit, but implementing
  29       that is entirely at the whimsy of Dreamhost, which I am not going to
  30       bother with.
  31     </li>
  32     <li>
  33       <em>Increased possibility for user participation.</em> Git makes it extremely
  34       easy to do local development and submit patches.
  35     </li>
  36     <li>
  37       <em>Data redundancy.</em> Every user has a complete copy of HTML Purifier's
  38       history, making it extremely difficult to lose data. This is opposed
  39       to our current setup, where htmlpurifier.org is a central point of failure,
  40       and backups are sent to only one other machine.
  41     </li>
  42     <li>
  43       <em>Performance.</em> Git is fast, both in terms of disk operations
  44       and network operations. Gone are the days of waiting several minutes
  45       for Subversion to finish committing.
  46     </li>
  47   </ul>
  48   <p>
  49     Currently, only <code>htmlpurifier</code> has been migrated to Git;
  50     <code>htmlpurifier-web</code> will be migrated after any kinks are
  51     worked out. There are number of features such as nightly snapshot
  52     generation and contributor documentation that needs to be written.
  53   </p>
  54   <p>
  55     We will be using <a href="http://repo.or.cz/w/htmlpurifier.git">repo.or.cz</a>
  56     as our primary remote repository; push access will be administered there,
  57     and changes will be mirrored (courtesy of a script by aeruder at #git)
  58     to a repository hosted at <a href="http://git.htmlpurifier.org">git.htmlpurifier.org</a>
  59     as well as <a href="http://github.com/ezyang/htmlpurifier/tree/master">GitHub</a>.
  60     If you want to grab a development copy, use this command:
  61   </p>
  62   <pre>git clone git://repo.or.cz/htmlpurifier.git</pre>
  63   <p>
  64     Feel free to play around, and register comments and complaints at
  65     <a href="phorum">the forum</a>.
  66   </p>
  67 </div>
  68 </body>
  69 </html>