www/testimonials.html

   1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
   2 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
   3 <html xmlns="http://www.w3.org/1999/xhtml">
   4 <head>
   5 <style type="text/css"> /* <![CDATA[ */
   6   @import "branding/css/tigris.css";
   7   @import "branding/css/inst.css";
   8   /* ]]> */</style>
   9 <link rel="stylesheet" type="text/css" media="print"
  10   href="branding/css/print.css"/>
  11 <script type="text/javascript" src="branding/scripts/tigris.js"></script>
  12 <title>Subversion Testimonials</title>
  13 <meta http-equiv="Content-Type"
  14       content="text/html; charset=UTF-8"/>
  15 </head>
  16
  17 <body>
  18 <div class="app">
  19
  20 <h1 style="text-align: center;">Subversion Testimonials</h1>
  21
  22 <p>If you're trying to persuade your organization to try Subversion,
  23 the <a href="#testimonials">testimonials</a> and the <a
  24 href="#open-source-projects-using-svn">list of open source projects
  25 using Subversion</a> below might help.</p>
  26
  27 <p>See also our <a href="links.html">links page</a> and our <a
  28 href="svn-dav-securityspace-survey.html">graph of public Subversion
  29 DAV servers</a>.</p>
  30
  31 <div class="h2" id="testimonials" title="testimonials">
  32 <h2><a name="testimonials">Testimonials</a></h2>
  33
  34   <ul>
  35
  36     <li>
  37       <p><strong>Jason D. Lee of <a href="http://www.hobbylobby.com/">Hobby Lobby</a></strong>
  38       <tt><a href="http://subversion.tigris.org/servlets/ReadMsg?list=users&amp;msgNo=22868">(15&nbsp;Dec&nbsp;2004)</a></tt></p>
  39
  40       <p><em>I work for a large retailer in the US.  We are currently
  41       going through a certification process with VISA.  Part of the
  42       compliance demands are that we track all router and switch
  43       configuration changes, noting what changes were made and who
  44       made them.  We had a vendor come in and demo a very complicated
  45       system that did the job, but was priced at around $80,000.  Even
  46       in the middle of a $1M+ project, that's a lot of money.  When
  47       one of the network administrators told me what the price tag
  48       was, I immediately pointed him at Subversion.  A few days later
  49       of testing and developing methodology, we now have the router
  50       configs for our 300+ stores as well as our corporate routers
  51       safely stored and tracked in Subversion.  Our network
  52       administrators use TortoiseSVN for all of the commits, and those
  53       with access can view the history using WebSVN, and all this cost
  54       us one 1U server, which was reclaimed from a decommissioned
  55       server cluster.  It has been fast, stable and easy to use.
  56       Here's a big thank you to the entire Subversion team, especially
  57       the ones who tireless answer questions on IRC.  You have built
  58       an amazing system that I recommend every chance I get.</em></p>
  59
  60       <p><em>Jason Lee<br/>
  61       Programmer/Analyst<br/>
  62       Hobby Lobby Stores, Inc.</em></p>
  63     </li>
  64
  65     <li>
  66       <p><strong><a href="http://www.bieberlabs.com/">Ron Bieber</a></strong>
  67       <tt><a href="http://subversion.tigris.org/servlets/ReadMsg?list=dev&amp;msgNo=72516">(23&nbsp;July&nbsp;2004)</a></tt></p>
  68
  69       <p><em>I currently manage a group of about 20 developers for a
  70       Fortune 500 company.  We used CVS from January of 2001 until May
  71       of 2004 when we converted all of our repositories over to
  72       Subversion.</em></p>
  73
  74       <p><em>The advantages we received from Subversion are immense.
  75       Before our conversion to CVS from VSS, we had two full time
  76       employees managing our production builds.  Upon conversion to
  77       CVS we cut that resource count down to one.  This resource
  78       handled all branching and merging activities, reporting
  79       activities, and manipulation of the CVS repository to move files
  80       while retaining history.  The CVS branching and merging was just
  81       too cryptic (and took too long) for anyone to want to learn it.
  82       We had two CVS "experts" in house which included me and one of
  83       my direct reports.  We were constantly called in to resolve
  84       issues.  I myself spent a ton of time managing the support of
  85       the CVS repositories.</em></p>
  86
  87       <p><em>After running across Subversion by chance in May of 2003,
  88       I started piloting it at home.  As I used it more, I became
  89       convinced that this was a tool that my team needed in order to
  90       increase our productivity.  After using it for a while, I was
  91       able to come up with some specific areas that justified our
  92       conversion to Subversion in order to maximize our productivity
  93       and code quality:</em></p>
  94
  95       <ol>
  96
  97         <li><em>Atomic commits - The lack of atomicity in commits was a
  98         huge problem for us with CVS.  Subversion gives us the
  99         confidence that when we commit, everything went into the
 100         repository.</em></li>
 101
 102         <li><em>The ability to back out changes before going to
 103         production--using an activity branching model, we can allow
 104         developers to branch per activity and only merge to the main
 105         source base after code reviews have been performed.  If there
 106         are problems, we have one revision we can back out that
 107         includes the full changeset for that change. While the
 108         repository level revisioning was a shift for my developers to
 109         make that didn't happen immediately, it begins to make sense
 110         when an activity had to be removed from the build.  In CVS we
 111         had to go through each file looking for revisions that were
 112         effected by a change.  Subversion now manages this for
 113         us.</em></li>
 114
 115         <li><em>Decreased build time.  We run CruiseControl, and the
 116         checkout times we were experiencing with CVS, along with our
 117         requirement to tag of our source base after each build caused
 118         our automated build cycle to take an inordinate amount of
 119         time.  With the restriction that all production changes MUST
 120         go through the build, this made emergency situations very
 121         stressful.  The cheap copy functionality of Subversion
 122         decreased the time it took to get a change into source
 123         control, through the build system, and into deployment
 124         packages by 80%, greatly increasing our response time.</em></li>
 125
 126         <li><em>Directory Versioning - this was a big deal that caused us
 127         to actually evaluate Clearcase at one point.  The CVS Attic
 128         was killing us in checkout time and build time with the
 129         velocity of change we were making to the source base.  When
 130         checkout times got too slow, we would have to wipe out the
 131         attic, effectively wiping out the history of our source base.
 132         With Subversion, we can remove something from the repository
 133         and not suffer performance penalties later (and still be able
 134         to get the deleted contents back).</em></li>
 135
 136         <li><em>Simpler (and faster) branching - we no longer have a full
 137         time FTE managing branches.  We are now cycling this activity
 138         through the group.  Each developer can perform this activity,
 139         because it is now part of his daily work.</em></li>
 140       </ol>
 141
 142       <p><em>As a manager, converting to Subversion was one of the best
 143       decisions I have made thus far that had a such a direct and
 144       highly visible impact on the productivity of my team.</em></p>
 145
 146       <p><em>I hope this helps you make your case for Subversion.  My
 147       personal opinion is that no one should even consider CVS at this
 148       point in time.  Subversion is a great product and the support
 149       you get just on the mailing lists alone (from the development
 150       team no less!) is second to none.</em></p>
 151     </li>
 152
 153     <li>
 154       <p><strong>Ross Mark of Controlling Edge Inc</strong>
 155       <tt><a href="http://subversion.tigris.org/servlets/ReadMsg?list=dev&amp;msgNo=72348">(22&nbsp;July&nbsp;2004)</a></tt></p>
 156
 157       <p><em>For my own company Controlling Edge and at one of my
 158       customers S4 Technology (www.s4-technology.com) I have been
 159       running Subversion since 0.17 and have never looked back. While
 160       there were a few issues initially we have never lost anything
 161       and currently have around 20 repositories containing everything
 162       from source code, documentation to complete product
 163       installations. We use Subversion to install and upgrade the
 164       software on our servers. Once we copy the svn client onto the
 165       box the entire installation is a simple svn co plus the asvn to
 166       restore symlinks, devices and file permissions. Upgrading
 167       between releases with svn is great as it automatically merges
 168       any changes to local configuration files with new entries for
 169       the latest version. We even use svn to store file system images
 170       for our embedded devices (linux file system). Currently we have
 171       to check out the svn image on a server and then downloaded to
 172       our embedded device via rsync. We don't have the memory for a
 173       full svn client nor the disk space for the working copy but one
 174       day we will write our own svn client that can just do the
 175       checkout without the need for the wc support files or the memory
 176       overhead.</em></p>
 177
 178       <p><em>For the past 9 years I had been installing CVS at
 179       customer sites that required version control and wouldn't
 180       hesitate now to recommend SVN instead.</em></p>
 181     </li>
 182
 183     <li>
 184       <p><strong>John Szakmeister</strong>
 185       <tt><a href="http://subversion.tigris.org/servlets/ReadMsg?list=dev&amp;msgNo=72339">(21&nbsp;July&nbsp;2004)</a></tt></p>
 186
 187       <p><em>I work for a government contracting facility.  We develop
 188       everything from hardware, to full-fledged software applications,
 189       all of which supports mission-critical activities.  We're
 190       currently using it on one of our most productive teams, and
 191       houses about 3 years worth of work (for about 14 developers).
 192       We started off with CVS, and found that the customer was
 193       constantly coming back with request for features and upgrades.
 194       Our small test projects would turn into fully-funded
 195       applications, and as such, we had to restructure them.  It was
 196       just too painful with CVS, and we decided to look for something
 197       better.</em></p>
 198
 199       <p><em>We found Subversion when it was at version 0.17.  We
 200       started with just a few developers using it, and then migrated
 201       our other developers over time.  I can say without question that
 202       it has been one of the best decisions that we've made.
 203       Subversion works better than CVS ever did.  We can detect
 204       corruption before it gets to be a problem, we get atomic
 205       commits, and directory versioning.  All of which has made our
 206       development process and our ability to adapt to the customers'
 207       ever-changing requirements that much easier.  Plus, it natively
 208       supports both the Windows and Linux platforms (versus the mixing
 209       of CVS and CVSNT that we had before), which is our primary
 210       development platforms.  We've never lost any data, and our
 211       developers have found it to be a very intuitive tool.
 212       Subversion has been rock-solid in our environment, and very much
 213       complements our software engineering practices.  I can't speak
 214       highly enough of it.</em></p>
 215     </li>
 216
 217     <li>
 218       <p><strong>Stuart Robertson of Absolute Systems, Inc</strong>
 219       <tt><a href="http://subversion.tigris.org/servlets/ReadMsg?list=users&amp;msgNo=10651">(5&nbsp;May&nbsp;2004)</a></tt></p>
 220
 221       <p><em>I introduced SVN to Absolute Systems Inc.
 222       (www.absolutesys.com) where I work about a year ago, and for
 223       about 8 months we ran internal SVN pilots, played around to gain
 224       experience and trust, etc.</em></p>
 225
 226       <p><em>In the last 4 months we have migrated all of our internal
 227       product source repositories from Visual Source-Safe to SVN using
 228       an internally-written VSS-to-SVN migration tool.</em></p>
 229
 230       <p><em>Our largest SVN repository is now 3.7GB and currently has
 231       68806 revisions. We are running SVN 1.0.1 + Apache 2.0.48 on
 232       Linux. ...</em></p>
 233
 234       <p><em>SVN is a superb piece of work, and it is a *huge* step
 235       forward from VSS.  To put things in perspective... previously we
 236       had 26 VSS databases for one product, primarily because of
 237       problems with VSS when the repositories grow large.  As you can
 238       imagine, trying to manage product releases across so many
 239       repositories was really painful.</em></p>
 240
 241       <p><em>Now, with SVN, *all* of the artifacts for that same product are
 242       in a single repository, meaning that with a few cheap copy
 243       operations all of the sources that make up a given release can
 244       be grouped together. ...</em></p>
 245     </li>
 246
 247     <li>
 248       <p><strong>Gustavo Niemeyer of Conectiva Linux</strong>
 249       <tt><a href="http://subversion.tigris.org/servlets/ReadMsg?list=users&amp;msgNo=6523">(25&nbsp;February&nbsp;2004)</a></tt></p>
 250
 251       <p><em>I'm sure you are aware about the fantastic product you
 252       people have built, but I'd like to tell you a little story which
 253       should give new users some comfort about it.</em></p>
 254
 255       <p><em>Here in Conectiva we used to maintain our packages in a file
 256       based system, storing the latest SRPM packages, and also some
 257       old versions in case something bad happened. For a long time we
 258       wanted to build some system which would make our life easier in
 259       the daily work, and at the same time would give us some
 260       flexibility accessing historic information.</em></p>
 261
 262       <p><em>Shortening the history a lot, 1 year and 6 months ago, the
 263       first revision was committed into our repository:</em></p>
 264
 265       <pre>
 266       % svn log https://svn.distro.conectiva/repos/cnc -r 1
 267       ------------------------------------------------------------------------
 268       r1 | niemeyer | 2002-08-27 17:12:04 -0300 (Tue, 27 Aug 2002) | 1 line
 269
 270       Created basic structure.
 271       ------------------------------------------------------------------------
 272 </pre>
 273
 274       <p><em>Since then, 5 complete Conectiva Linux distributions were
 275       committed into the repository, and every single update in the
 276       distribution is done using Subversion. We've already surpassed
 277       50000 revisions, in a 30GB repository. Even though we have had
 278       space, memory, and other kinds of problems around the
 279       repository, I'm proud to say we have never lost a single bit of
 280       information since then.</em></p>
 281
 282       <p><em>Based on this, the least I could do is sending a big THANK
 283       YOU for everyone involved in the project.</em></p>
 284     </li>
 285
 286     <li>
 287       <p><strong>Mark Bohlman of Teledata Communications</strong>
 288       <tt><a href="http://subversion.tigris.org/servlets/ReadMsg?list=users&amp;msgNo=14575">(21&nbsp;July&nbsp;2004)</a></tt></p>
 289
 290       <p><em>Teledata Communications has been using Subversion for
 291       storing all of the source code on all our software products for
 292       the past year (since version 0.24).  I have been very happy with
 293       the overall results and they way that developer impacts are
 294       minimal.  We have not lost a single byte of code nor had any
 295       significant issues with using Subversion since the beginning.  I
 296       attribute part of the productivity gains we have see in the past
 297       year to the move away from our prior system with locking (and
 298       the corresponding messages back and for to have something
 299       'unlocked').  We continued to expand the use of the product to
 300       all groups in the company.</em></p>
 301
 302       <p><em>Mark Bohlman<br/>
 303       Software Development Manager</em></p>
 304     </li>
 305
 306     <li>
 307       <p><strong>Mark Grosberg, regarding <a
 308       href="http://www.asttool.com/">Assenmacher Specialty Tools</a>
 309       and <a href="http://www.gladesoft.com/">GladeSoft</a></strong>
 310       <tt><a href="http://subversion.tigris.org/servlets/ReadMsg?list=users&amp;msgNo=14573">(21&nbsp;July&nbsp;2004)</a></tt></p>
 311
 312       <p><em>AST makes automotive scan tools.  We keep our source code
 313       for both the embedded side and the Windows interface side under
 314       Subversion.  In addition we keep our (large) databases under
 315       Subversion as well.</em></p>
 316
 317       <p><em>GladeSoft sells an embedded webserver toolkit and
 318       application framework. Subversion stores all of our code and
 319       documentation.  In addition we store all of our business records
 320       in Subversion; so I guess we can't pull an Enron as easily
 321       :-)</em></p>
 322
 323       <p><em>Neither company has lost a single change with
 324       Subversion. Both companies also have satellite workers who use
 325       SSL to access the source repositories.  Subversion
 326       administration is relatively straightforward provided you use
 327       Apache so there are no permission problems. At AST most of the
 328       server administration is done by one of the mechanics who has
 329       other work to do.</em></p>
 330
 331     </li>
 332
 333     <li>
 334       <p><strong>Fog Creek Software on the
 335          <a href="http://www.fogcreek.com/FogBugz/docs/40/Articles/SourceControl/TortoiseSVN.html"
 336          >FogBugz and TortoiseSVN</a> integration</strong></p>
 337
 338       <p><em>Fog Creek Software has been using Subversion as our
 339       source control system for a few years now.  We switched awhile
 340       back from using CVS and have nothing but praise for Subversion.
 341       Anyone currently using CVS should bite the bullet and make the
 342       switch.  It just works.  The price is right, and best of all it
 343       integrates tightly with FogBugz.  We support a whole host of
 344       <a href="http://www.fogcreek.com/FogBugz/docs/40/Articles/SourceControl/SourceControlIntegrationS.html"
 345       >Source Control Systems</a>, and adding new ones is very simple,
 346       but if you are starting out -- our recommendation is to start
 347       with Subversion.</em></p>
 348
 349       <p><em>Once you get Subversion set up and running, if you are on
 350       Windows, you will be amazed at how useful a good Subversion
 351       client can be.  Steve King has created a fantastic piece of
 352       software, the <a href="http://tortoisesvn.tigris.org/"
 353       >TortoiseSVN</a> client, and he has spent some time making sure
 354       that it works perfectly with FogBugz.  [...]</em></p>
 355
 356     </li>
 357
 358     <li>
 359       <p><strong>Robert Zeh of Error Free Software</strong>
 360       <tt><a href="http://subversion.tigris.org/servlets/ReadMsg?list=users&amp;msgNo=14696">(23&nbsp;July&nbsp;2004)</a></tt></p>
 361
 362       <p><em>I manage a 13 member application development group for a
 363       trading firm.  There are about 9 other developers outside the
 364       group, and some others, so we have about 20 people using our
 365       Subversion repository.</em></p>
 366
 367       <p><em>For the past 10 years we used SCCS.  It was very
 368       frustrating --- files could not be renamed or moved, developers
 369       would forget about locks they had acquired, and remote
 370       development was next to impossible.  SCCS also made our limited
 371       Windows development painful (we are a Unix shop).</em></p>
 372
 373       <p><em>Since we switched to Subversion things have been much
 374       better.  Our entire history was transported into our Subversion
 375       repository, so none of our history was lost.  I wrote a Python
 376       script to transform it directly from SCCS to Subversion, and it
 377       was painless.</em></p>
 378
 379       <p><em>Conflicts have been very rare.  The ability to easily
 380       branch has been very useful; developers can make commits to
 381       branches without breaking other people's code.  It's easier to
 382       see what people are working on as the commits hit our internal
 383       commit mailing list.  Since we tag each release, we're able to
 384       determine which source code contributed to a release.
 385       TortiseSVN makes Windows development easy (no more ftping files
 386       over, or trying to build on a remotely mounted samba
 387       drive).</em></p>
 388
 389       <p><em>Robert Zeh<br/>
 390       Manager, Application Development<br/>
 391       Error Free Software</em></p>
 392
 393     </li>
 394
 395     <li>
 396       <p><strong>Chris Wein of Mobilygen</strong>
 397       <tt><a href="http://subversion.tigris.org/servlets/ReadMsg?list=users&amp;msgNo=14695">(23&nbsp;July&nbsp;2004)</a></tt></p>
 398
 399       <p><em>I also have had a very positive experience moving from
 400       CVS to Subversion in a commercial setting.  We are a small-ish
 401       silicon valley startup that used to have everything in CVS.
 402       Shortly after I joined as s/w manager I switched the s/w team to
 403       SVN (0.37) with excellent results.  We have had zero loss of
 404       data, zero down time, with effective branching, easy repository
 405       restructuring and constant time tags as our big positives.  The
 406       entire company will be moving in the near-ish future based on
 407       our pilot.  And of course the support from this list is
 408       fantastic.</em></p>
 409
 410       <p><em><span style="color: red">[Fair play dictates that we also
 411       include the wish-list portion of Chris's
 412       testimonial...]</span></em></p>
 413
 414       <p><em>As for my wishlist, it is short - completely seamless and
 415       foolproof tracking of merge history at the same level as the
 416       commercial tools.  I don't want to remember revision numbers, I
 417       just want to branch and merge with the tool remembering common
 418       base versions etc.  This is really the only thing I miss about
 419       ClearCase.</em></p>
 420
 421       <p><em><span style="color: red">[We agree :-).  Better merge tracking
 422       is on Subversion's long-term <a
 423       href="roadmap.html">roadmap</a>.]</span></em></p>
 424
 425     </li>
 426
 427     <li>
 428       <p><strong>Martin Pittenauer of <a href="http://www.codingmonkeys.de/subethaedit/">SubEthaEdit</a></strong>
 429       <tt>(2&nbsp;June&nbsp;2004)</tt></p>
 430
 431       <p><em>We are using Subversion since version 0.17 and it never
 432       let us down.  On contrary it provided a much better experience
 433       than any versioning system we have used before, including CVS
 434       and perforce. With Apple adding support for .svn files within
 435       NIBs with Xcode 1.2 we are certain that Subversion is the ideal
 436       versioning platform for modern software development on Mac OS
 437       X.</em></p>
 438     </li>
 439
 440   </ul>
 441
 442 </div>
 443
 444 <div class="h2" id="open-source-projects-using-svn"
 445                 title="open-source-projects-using-svn">
 446 <h2>Open Source Projects Using Subversion</h2>
 447
 448 <p style="font-style: italic;">This is not a complete list of all open
 449 source projects using Subversion, just some of the most recognizeable
 450 ones:</p>
 451
 452   <ul>
 453
 454     <li><p><strong>ASF</strong>: The Apache Software Foundation.<br/>
 455         Project site:  <a href="http://www.apache.org/"
 456                      >http://www.apache.org/</a><br/>
 457         Repository:  <a href="http://svn.apache.org/repos/asf/">
 458                      http://svn.apache.org/repos/asf/</a><br/>
 459       <em>The Apache Software Foundation is a community of many
 460       open-source software projects, including the popular Apache HTTP
 461       Server.</em></p>
 462     </li>
 463
 464     <li><p><strong>KDE</strong>: The K Desktop Environment.<br/>
 465         Project site:  <a href="http://www.kde.org/"
 466                      >http://www.kde.org/</a><br/>
 467         Repository:  <a href="svn://anonsvn.kde.org/home/kde/">
 468                      svn://anonsvn.kde.org/home/kde/</a><br/>
 469       <em>KDE is a powerful Free Software graphical desktop
 470       environment for Linux and Unix workstations.</em></p>
 471     </li>
 472
 473     <li><p><strong>GNOME</strong>: The GNOME Project.<br/>
 474         Project site:  <a href="http://www.gnome.org/"
 475                      >http://www.gnome.org/</a><br/>
 476         Repository:  <a href="http://svn.gnome.org/">
 477                      http://svn.gnome.org/</a><br/>
 478       <em>The GNOME project provides the GNOME desktop environment and
 479       the GNOME development platform, an extensive framework for
 480       building applications that integrate into the rest of the
 481       desktop.</em></p>
 482     </li>
 483
 484     <li><p><strong>GCC</strong>: The GNU Compiler Collection.<br/>
 485         Project site:  <a href="http://gcc.gnu.org/"
 486                      >http://gcc.gnu.org/</a><br/>
 487         Repository:  <a href="svn://gcc.gnu.org/svn/gcc/">
 488                      svn://gcc.gnu.org/svn/gcc</a><br/>
 489       <em>GCC, the GNU Compiler Collection, includes front ends for C,
 490       C++, Objective-C, Fortran, Java, and Ada, as well as libraries
 491       for these languages.</em></p>
 492     </li>
 493
 494     <li><p><strong>Python</strong>: The Python programming language<br/>
 495         Project site:  <a href="http://www.python.org/"
 496                      >http://www.python.org/</a><br/>
 497         Repository:  <a href="http://svn.python.org/projects/python/">
 498                      http://svn.python.org/projects/python/</a><br/>
 499       <em>Python is an interpreted, interactive, object-oriented
 500       programming language.</em></p>
 501     </li>
 502
 503     <li><p><strong>Samba</strong>:  SMB services for *nix systems.<br/>
 504         Project site:  <a href="http://www.samba.org/"
 505                      >http://www.samba.org/</a><br/>
 506         Repository:  <a href="svn://svnanon.samba.org/samba"
 507                      >svn://svnanon.samba.org/samba</a><br/>
 508       <em>Samba is an Open Source/Free Software suite that provides
 509       seamless file and print services to SMB/CIFS clients.</em></p>
 510     </li>
 511
 512     <li><p><strong>Mono</strong>: an open-source implementation of
 513         C#/.NET.<br/>
 514         Project site:  <a href="http://www.mono-project.com/"
 515                      >http://www.mono-project.com/</a><br/>
 516         Repository:  <a href="svn://mono.myrealbox.com/source/"
 517                      >svn://mono.myrealbox.com/source/</a><br/>
 518       <em>Mono is a comprehensive open source development platform based
 519       on the .NET framework.</em></p>
 520     </li>
 521
 522     <li><p><strong>PuTTY</strong>: Win32 SSH/Telnet implementation<br/>
 523         Project site:  <a
 524            href="http://www.chiark.greenend.org.uk/~sgtatham/putty/"
 525                 >http://www.chiark.greenend.org.uk/~sgtatham/putty/</a><br/>
 526         Repository: <a href="svn://ixion.tartarus.org/main/putty/"
 527                     >svn://ixion.tartarus.org/main/putty/</a><br/>
 528       <em>PuTTY is a free implementation of Telnet and SSH for Win32 and
 529       Unix platforms, along with an xterm terminal emulator.</em></p>
 530     </li>
 531
 532     <li><p><strong>Zope</strong>:  web application
 533         server/framework.<br/>
 534         Project site:  <a href="http://www.zope.org/"
 535                      >http://www.zope.org/</a><br/>
 536         Repository:  <a href="svn://svn.zope.org/repos/main/Zope"
 537                      >svn://svn.zope.org/repos/main/Zope</a><br/>
 538       <em>Zope is an open source application server for building content
 539       managements, intranets, portals, and custom applications.</em></p>
 540     </li>
 541
 542     <li><p><strong>Plone</strong>:  content management system.<br/>
 543         Project site:  <a href="http://plone.org/"
 544                                >http://plone.org/</a><br/>
 545         Repository:    <a href="http://svn.plone.org/"
 546                                >http://svn.plone.org/</a><br/>
 547
 548       <em>Plone is an out-of-the-box ready content management system
 549       built on the powerful and free Zope Application server.</em></p>
 550     </li>
 551
 552     <li><p><strong>Xiph</strong>:  open-source multimedia
 553         protocols.<br/>
 554         Project site:  <a href="http://www.xiph.org/"
 555                      >http://www.xiph.org/</a><br/>
 556         Repository:  <a href="http://svn.xiph.org/"
 557                      >http://svn.xiph.org/</a><br/>
 558       <em>The Xiph.Org Foundation is a non-profit corporation best known
 559       for the development of the Ogg Vorbis sound compression format and
 560       the Ogg Theora video codec.</em></p>
 561     </li>
 562
 563     <li><p><strong>GnuPG</strong>: a free encryption program.<br/>
 564         Project site:  <a href="http://www.gnupg.org/"
 565                                >http://www.gnupg.org/</a><br/>
 566         Repository:  <a href="svn://cvs.gnupg.org/gnupg/"
 567                              >svn://cvs.gnupg.org/gnupg/</a><br/>
 568
 569       <em>GnuPG is a GPL-licensed replacement for <cite>Pretty Good
 570       Privacy</cite> (PGP) and provides strong encryption and digital
 571       signatures.</em></p>
 572     </li>
 573
 574     <li><p><strong>CUPS (Common UNIX Printing System)</strong>: printing
 575         services for Unix-based OS's.<br/>
 576         Project site:  <a href="http://www.cups.org/"
 577                                >http://www.cups.org/</a><br/>
 578         Repository:  <a href="http://svn.easysw.com/public/cups/trunk/"
 579                              >http://svn.easysw.com/public/cups/trunk/</a><br/>
 580
 581       <em>CUPS provides a portable printing layer for Unix-based
 582       operating systems.</em></p>
 583     </li>
 584
 585     <li><p><strong>Irssi</strong>:  a GPL-licensed IRC client.<br/>
 586         Project site:  <a href="http://www.irssi.org/"
 587                                >http://www.irssi.org/</a><br/>
 588         Repository:  <a href="http://svn.irssi.org/"
 589                              >http://svn.irssi.org/</a><br/>
 590
 591       <em>Irssi is a popular and powerful text mode IRC client for
 592       Unix-like operating systems.</em></p>
 593     </li>
 594
 595     <li><p><strong>Linux From Scratch</strong>:  a Linux distribution
 596         built from source.<br/>
 597         Project site:  <a href="http://www.linuxfromscratch.org/"
 598                      >http://www.linuxfromscratch.org/</a><br/>
 599         Repository:  <a href="svn://linuxfromscratch.org/LFS/"
 600                      >svn://linuxfromscratch.org/LFS/</a><br/>
 601
 602       <em>A Linux distribution which gives you the power to build your
 603       own, customized system and teaches you how a Linux system works
 604       internally.</em></p>
 605     </li>
 606
 607     <li><p><strong>Conectiva</strong>:  a South American Linux
 608         distribution.<br/>
 609         Project site:  <a href="http://www.conectiva.com.br/"
 610                      >http://www.conectiva.com.br/</a><br/>
 611         Repository:  <a href="https://moin.conectiva.com.br/RepositorySystem"
 612                      >https://moin.conectiva.com.br/RepositorySystem</a><br/>
 613
 614       <em>Conectiva develops and distributes the Conectiva Linux
 615       distribution, which is aimed at use in Latin America.</em></p>
 616     </li>
 617
 618     <li><p><strong>Trac</strong>: a project management system.<br/>
 619         Project site:  <a href="http://projects.edgewall.com/trac/">
 620                      http://projects.edgewall.com/trac/</a><br/>
 621         Repository:  <a href="http://svn.edgewall.com/repos/trac/"
 622                         >http://svn.edgewall.com/repos/trac/</a><br/>
 623         <em>Trac is an enhanced wiki and issue tracking system for
 624         software development projects. It provides an interface to
 625         Subversion, an integrated wiki and convenient report
 626         facilities.</em></p>
 627     </li>
 628
 629     <li><p><strong>GNU Enterprise</strong>: enterprise application
 630                                             development.<br/>
 631         Project site:  <a href="http://www.gnuenterprise.org/">
 632                      http://www.gnuenterprise.org/</a><br/>
 633         Repository:  <a href="http://www.gnuenterprise.org/developers/svn.php"
 634                         >http://www.gnuenterprise.org/developers/svn.php</a>
 635                        <br/>
 636         <em>GNU Enterprise (GNUe) is a meta-project which is part of the
 637         overall GNU Project. GNUe's goal is to develop enterprise-class
 638         data-aware applications as Free software.</em></p>
 639     </li>
 640
 641     <li><p><strong>Ethereal</strong>: a free network protocol
 642         analyzer<br/>
 643         Project site:  <a href="http://www.ethereal.com/"
 644                        >http://www.ethereal.com/</a><br/>
 645         Repository:  <a href="http://anonsvn.ethereal.com/ethereal/"
 646                      >http://anonsvn.ethereal.com/ethereal/</a><br/>
 647         <em>Ethereal is a free network protocol analyzer with all the
 648         standard features you would expect in a protocol analyzer, and
 649         several features not seen in any other product.</em></p>
 650     </li>
 651
 652     <li><p><strong>Netfilter</strong>: the Linux packet manipulation
 653         framework<br/>
 654         Project site:  <a href="http://www.netfilter.org/"
 655                        >http://www.netfilter.org/</a><br/>
 656         Repository:  <a href="https://svn.netfilter.org/netfilter/"
 657                      >https://svn.netfilter.org/netfilter/</a><br/>
 658         <em>netfilter is a set of hooks inside the Linux kernel that
 659         allows kernel modules to register callback functions with the
 660         network stack. iptables is a generic table structure for the
 661         definition of rulesets.</em></p>
 662     </li>
 663
 664     <li><p><strong>TWiki</strong>: a web based collaboration
 665         platform<br/>
 666         Project site:  <a href="http://twiki.org/"
 667                        >http://twiki.org/</a><br/>
 668         Repository:  <a href="http://ntwiki.ethermage.net/svn/twiki/"
 669                      >http://ntwiki.ethermage.net/svn/twiki/</a><br/>
 670         <em>TWiki is a structured wiki, typically used to run a project
 671         development space, a document management system, a knowledge
 672         base, or any other groupware tool on the network.</em></p>
 673     </li>
 674
 675   </ul>
 676
 677 </div>
 678
 679 </div>
 680 </body>
 681 </html>
 682