<commit_before><!DOCTYPE html PUBLIC "-//Tigris//DTD XHTML 1.0 Transitional//EN"
"http://style.tigris.org/tigris_transitional.dtd">
<html>
<head>
<title>Project Development</title>
<link rel="stylesheet" type="text/css"
      href="http://subversion.tigris.org/branding/css/tigris.css"/>
<link rel="stylesheet" type="text/css"
      href="http://subversion.tigris.org/branding/css/inst.css"/>
<link rel="stylesheet" type="text/css" media="print"
      href="http://subversion.tigris.org/branding/css/print.css"/>
<script type="text/javascript"
        src="http://subversion.tigris.org/branding/scripts/tigris.js"></script>
</head>

<body>
<div class="app">

<h2>Subversion Development</h2>

<h3>Coding</h3>

<p>Subversion development discussion takes place on the mailing list
<a href="mailto:<EMAIL>"><EMAIL></a>.
You don't need to subscribe to the list just to submit a patch or two,
but if you want to be involved with Subversion development on a
regular basis, you should probably subscribe.  It's high-traffic, but
threading tends to be fairly disciplined, so you can ignore
conversations you aren't interested in.  For real-time chat,
developers use the same IRC channel as everyone else: <a
href="irc://irc.freenode.net/svn">irc.freenode.net/svn</a>.</p>

<p>The <b>HACKING</b> file contains developer guidelines, see:</p>

<blockquote>
   <a href="http://svn.collab.net/repos/svn/trunk/HACKING"
           >http://svn.collab.net/repos/svn/trunk/HACKING</a>
</blockquote>

<p>There you can find information about submitting patches, learning
your way around the code, interacting with other developers, project
governance, etc.  If you don't see the answers you need there, please
ask on the mailing list or in IRC, we're happy to help.</p>


<h3>Translating Subversion output</h3>

<p>With the release of version 1.1 Subversion program output can be
translated.  Discussion takes place both on the Subversion development
mailing list as well as dedicated native language mailing lists
(<em><EMAIL></em>).</p>

<p>Next to any information it <b>HACKING</b> pertinent to translating
Subversion output, additional information can be found in</p>

<blockquote>
   <a href="http://svn.collab.net/repos/svn/trunk/TRANSLATING"
           >http://svn.collab.net/repos/svn/trunk/TRANSLATING</a>
</blockquote>

<p>Currently available translations can be found in
<a href="http://svn.collab.net/repos/svn/trunk/subversion/po/"
>the po section of the repository</a>.  Please contact the development
mailing list when you want to start a translation not available yet.</p>


<h3>Translating the book &quot;Version control with Subversion&quot;</h3>

<p>Translations of the book &quot;Version control with Subversion&quot;
are also actively maintained.  Available languages are available at
<a href="http://svn.collab.net/repos/svn/trunk/doc/translations/"
>http://svn.collab.net/repos/svn/trunk/doc/translations/</a>.
Contributions can be sent to the main developers mailing list or to
one of the dedicated translations lists.  If you want to start a
translation which is not yet available, please contact the developers
mailing list to find out about the right course of action.</p>

</div>
</body>
</html><commit_msg>* www/project_development.html   (Translating the book): Buh-bye.<commit_after><!DOCTYPE html PUBLIC "-//Tigris//DTD XHTML 1.0 Transitional//EN"
"http://style.tigris.org/tigris_transitional.dtd">
<html>
<head>
<title>Project Development</title>
<link rel="stylesheet" type="text/css"
      href="http://subversion.tigris.org/branding/css/tigris.css"/>
<link rel="stylesheet" type="text/css"
      href="http://subversion.tigris.org/branding/css/inst.css"/>
<link rel="stylesheet" type="text/css" media="print"
      href="http://subversion.tigris.org/branding/css/print.css"/>
<script type="text/javascript"
        src="http://subversion.tigris.org/branding/scripts/tigris.js"></script>
</head>

<body>
<div class="app">

<h2>Subversion Development</h2>

<h3>Coding</h3>

<p>Subversion development discussion takes place on the mailing list
<a href="mailto:<EMAIL>"><EMAIL></a>.
You don't need to subscribe to the list just to submit a patch or two,
but if you want to be involved with Subversion development on a
regular basis, you should probably subscribe.  It's high-traffic, but
threading tends to be fairly disciplined, so you can ignore
conversations you aren't interested in.  For real-time chat,
developers use the same IRC channel as everyone else: <a
href="irc://irc.freenode.net/svn">irc.freenode.net/svn</a>.</p>

<p>The <b>HACKING</b> file contains developer guidelines, see:</p>

<blockquote>
   <a href="http://svn.collab.net/repos/svn/trunk/HACKING"
           >http://svn.collab.net/repos/svn/trunk/HACKING</a>
</blockquote>

<p>There you can find information about submitting patches, learning
your way around the code, interacting with other developers, project
governance, etc.  If you don't see the answers you need there, please
ask on the mailing list or in IRC, we're happy to help.</p>


<h3>Translating Subversion output</h3>

<p>With the release of version 1.1 Subversion program output can be
translated.  Discussion takes place both on the Subversion development
mailing list as well as dedicated native language mailing lists
(<em><EMAIL></em>).</p>

<p>Next to any information it <b>HACKING</b> pertinent to translating
Subversion output, additional information can be found in</p>

<blockquote>
   <a href="http://svn.collab.net/repos/svn/trunk/TRANSLATING"
           >http://svn.collab.net/repos/svn/trunk/TRANSLATING</a>
</blockquote>

<p>Currently available translations can be found in
<a href="http://svn.collab.net/repos/svn/trunk/subversion/po/"
>the po section of the repository</a>.  Please contact the development
mailing list when you want to start a translation not available yet.</p>

</div>
</body>
</html>
{'fraction_non_alphanumeric': 0.13000511160333958, 'fraction_numerical': 0.0037485091156926223, 'mean_word_length': 4.569259962049336, 'pattern_counts': {'":': 0, '<': 123, '<?xml version=': 0, '>': 123, 'https://': 0, 'lorem ipsum': 0, 'www.': 1, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 4, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1854315', 'n_tokens_mistral': 1954, 'n_tokens_neox': 1846, 'n_words': 588}