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