Sophie

Sophie

distrib > Mageia > 4 > x86_64 > by-pkgid > f9d20baf2d42bbb9f9c5746dba0abad5 > files > 243

python-translate-doc-1.10.0-3.mga4.noarch.rpm


<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">


<html xmlns="http://www.w3.org/1999/xhtml">
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
    
    <title>Contributing &mdash; Translate Toolkit 1.9.0 documentation</title>
    
    <link rel="stylesheet" href="../_static/basic.css" type="text/css" />
    <link rel="stylesheet" href="../_static/pygments.css" type="text/css" />
    <link rel="stylesheet" href="../_static/bootstrap.css" type="text/css" />
    <link rel="stylesheet" href="../_static/bootstrap-sphinx.css" type="text/css" />
    
    <script type="text/javascript">
      var DOCUMENTATION_OPTIONS = {
        URL_ROOT:    '../',
        VERSION:     '1.9.0',
        COLLAPSE_INDEX: false,
        FILE_SUFFIX: '.html',
        HAS_SOURCE:  true
      };
    </script>
    <script type="text/javascript" src="../_static/jquery.js"></script>
    <script type="text/javascript" src="../_static/underscore.js"></script>
    <script type="text/javascript" src="../_static/doctools.js"></script>
    <script type="text/javascript" src="../_static/bootstrap.js"></script>
    <script type="text/javascript" src="../_static/bootstrap-sphinx.js"></script>
    <link rel="top" title="Translate Toolkit 1.9.0 documentation" href="../index.html" />
    <link rel="next" title="Translate Toolkit Developers Guide" href="developers.html" />
    <link rel="prev" title="Building" href="building.html" /> 
  </head>
  <body>
  <div id="navbar" class="navbar navbar-fixed-top">
    <div class="navbar-inner">
      <div class="container-fluid">
        <a class="brand" href="../index.html">Translate Toolkit</a>
        <span class="navbar-text pull-left"><b>1.9.0</b></span>
          <ul class="nav">
            <li class="divider-vertical"></li>
            
              <li class="dropdown">
  <a href="#" class="dropdown-toggle" data-toggle="dropdown">Site <b class="caret"></b></a>
  <ul class="dropdown-menu globaltoc"><ul class="simple">
</ul>
<ul>
<li class="toctree-l1"><a class="reference internal" href="../features.html">Features</a></li>
<li class="toctree-l1"><a class="reference internal" href="../installation.html">Installation</a></li>
<li class="toctree-l1"><a class="reference internal" href="../commands/index.html">Converters</a></li>
<li class="toctree-l1"><a class="reference internal" href="../commands/index.html#tools">Tools</a></li>
<li class="toctree-l1"><a class="reference internal" href="../commands/index.html#scripts">Scripts</a></li>
<li class="toctree-l1"><a class="reference internal" href="../guides/index.html">Use Cases</a></li>
<li class="toctree-l1"><a class="reference internal" href="../formats/index.html">Supported formats</a></li>
</ul>
<ul class="current">
<li class="toctree-l1"><a class="reference internal" href="../styleguide.html">Translate Styleguide</a></li>
<li class="toctree-l1"><a class="reference internal" href="../styleguide.html#documentation">Documentation</a></li>
<li class="toctree-l1"><a class="reference internal" href="building.html">Building</a></li>
<li class="toctree-l1 current"><a class="current reference internal" href="">Contributing</a></li>
<li class="toctree-l1"><a class="reference internal" href="developers.html">Translate Toolkit Developers Guide</a></li>
</ul>
<ul>
<li class="toctree-l1"><a class="reference internal" href="../api/index.html">API</a></li>
</ul>
<ul>
<li class="toctree-l1"><a class="reference internal" href="../changelog.html">Important Changes</a></li>
<li class="toctree-l1"><a class="reference internal" href="../history.html">History of the Translate Toolkit</a></li>
<li class="toctree-l1"><a class="reference internal" href="../license.html">License</a></li>
</ul>
</ul>
</li>
              
<li class="dropdown">
  <a href="#" class="dropdown-toggle" data-toggle="dropdown">Page <b class="caret"></b></a>
  <ul class="dropdown-menu localtoc"><ul>
<li><a class="reference internal" href="#">Contributing</a><ul>
<li><a class="reference internal" href="#testing">Testing</a></li>
<li><a class="reference internal" href="#debugging">Debugging</a></li>
<li><a class="reference internal" href="#developing">Developing</a></li>
<li><a class="reference internal" href="#documenting">Documenting</a></li>
</ul>
</li>
</ul>
</ul>
</li>
            
            
              
  <li><a href="building.html"
         title="previous chapter">&laquo; Building</a></li>
  <li><a href="developers.html"
         title="next chapter">Translate Toolkit Developers Guide &raquo;</a></li>
            
            
              
            
          </ul>
          
            
<form class="navbar-search pull-right" action="../search.html" method="get">
  <input type="text" name="q" placeholder="Search" />
  <input type="hidden" name="check_keywords" value="yes" />
  <input type="hidden" name="area" value="default" />
</form>
          
          </ul>
        </div>
      </div>
    </div>
  </div>

<div class="container content">
   
  <div class="section" id="contributing">
<span id="id1"></span><h1>Contributing<a class="headerlink" href="#contributing" title="Permalink to this headline">¶</a></h1>
<p>We could use your help.  If you are interesting in contributing then please
join us on IRC on <a class="reference external" href="irc://irc.freenode.net/#pootle">#pootle</a> and on the
<a class="reference external" href="mailto:translate-devel&#37;&#52;&#48;lists&#46;sourceforge&#46;net">translate-devel</a> mailing list.</p>
<p>Here are some idea of how you can contribute</p>
<ul class="simple">
<li><a class="reference internal" href="#contributing-testing"><em>Test</em></a> &#8211; help us test new candidate releases
before they are released</li>
<li><a class="reference internal" href="#contributing-debugging"><em>Debug</em></a> &#8211; check bug reports, create tests to
highlight problems</li>
<li><a class="reference internal" href="#contributing-developing"><em>Develop</em></a> &#8211; add your Python developer skills
to the mix</li>
<li><a class="reference internal" href="#contributing-documenting"><em>Document</em></a> &#8211; help make our docs readable,
useful and complete</li>
</ul>
<p>Below we give you more detail on these:</p>
<div class="section" id="testing">
<span id="contributing-testing"></span><h2>Testing<a class="headerlink" href="#testing" title="Permalink to this headline">¶</a></h2>
<p>Before we release new versions of the Toolkit we need people to check that they
still work correctly.  If you are a frequent user you might want to start using
the release candidate on your current work and report any errors before we
release them.</p>
<p>Compile and install the software to see if we have any platform issues:</p>
<div class="highlight-python"><pre>./setup.py install</pre>
</div>
<p>Check for any files that are missing, tools that were not installed, etc.</p>
<p><em class="xref std std-ref">Run unit tests</em> to see if
there are any issues.  Please report any failures.</p>
<p>Finally, simply work with the software.  Checking all your current usage
patterns and report problems.</p>
</div>
<div class="section" id="debugging">
<span id="contributing-debugging"></span><h2>Debugging<a class="headerlink" href="#debugging" title="Permalink to this headline">¶</a></h2>
<ul class="simple">
<li>Make sure your familiar with the <tt class="xref doc docutils literal"><span class="pre">bug</span> <span class="pre">reporting</span> <span class="pre">guidelines</span></tt>.</li>
<li>Create a login for yourself at <a class="reference external" href="http://bugs.locamotion.org">http://bugs.locamotion.org</a></li>
<li>Then choose a bug</li>
</ul>
<p>Now you need to try and validate the bug.  Your aim is to confirm that the bug
is either fixed, is invalid or still exists.</p>
<p>If its fixed please close the bug and give details of how when it was fixed or
what version you used to validate it as corrected.</p>
<p>If you find that the bug reporter has made the incorrect assumptions or their
suggestion cannot work.  Then mark the bug as invalid and give reasons why.</p>
<p>The last case, an existing bug is the most interesting.  Check through the bug
and do the following:</p>
<ul class="simple">
<li>Fix up the summary to make it clear what the bug is</li>
<li>Create new bugs for separate issues</li>
<li>Set severity level and classifications correctly</li>
<li>Add examples to reproduce the bug, or make the supplied files simpler</li>
<li>If you can identify the bug but not fix it then explain what needs fixing</li>
<li>Move on to the next bug</li>
</ul>
</div>
<div class="section" id="developing">
<span id="contributing-developing"></span><h2>Developing<a class="headerlink" href="#developing" title="Permalink to this headline">¶</a></h2>
<p>Don&#8217;t ignore this area if you feel like you are not a hotshot coder!</p>
<p>You will need some Python skills, this is a great way to learn.</p>
<p>Here are some ideas to get you going:</p>
<ul class="simple">
<li>Write a test to expose some bug</li>
<li>Try to fix the actual code to fix your bug</li>
<li>Add a small piece of functionality that helps you</li>
<li>Document the methods in especially the base class and derived classes</li>
<li>Add a <a class="reference internal" href="../formats/index.html"><em>format</em></a> type and converters</li>
<li>Add more features to help our formats <a class="reference internal" href="../formats/conformance.html"><em>conform to the standards</em></a></li>
</ul>
<p>You will definitely need to be on the <a class="reference external" href="http://lists.sourceforge.net/lists/listinfo/translate-devel">Development</a> and probably on
the <a class="reference external" href="http://lists.sourceforge.net/lists/listinfo/translate-cvs">Subversion checkin</a> lists.</p>
<p>Now is the time to familiarise yourself with the <a class="reference internal" href="developers.html"><em>developers guide</em></a>.</p>
</div>
<div class="section" id="documenting">
<span id="contributing-documenting"></span><h2>Documenting<a class="headerlink" href="#documenting" title="Permalink to this headline">¶</a></h2>
<p>This is the easy one.  Login to the wiki and start!</p>
<p>The key areas that need to be looked at are:</p>
<ul class="simple">
<li>Do the guides to each tool cover all command line options</li>
<li>Are the examples clear for the general cases</li>
<li>Is the tools use clear</li>
<li>In the Use cases, can we add more, do they need updating. Has upstream
changed its approach</li>
</ul>
<p>After that and always:</p>
<ul class="simple">
<li>Grammar</li>
<li>Spelling</li>
<li>Layout</li>
</ul>
</div>
</div>


</div>
<hr>

<footer class="footer">
  <div class="container">
    <p class="pull-right"><a href="#">Back to top ↑</a></p>
    <ul class="unstyled muted">
      <li><small>
        &copy; 2012, Translate.org.za.<br/>
      </small></li>
      <li><small>
      Created using <a href="http://sphinx.pocoo.org/">Sphinx</a> 1.1.3.
      </small></li>
    </ul>
  </div>
</footer>
  </body>
</html>