in the Python documentation. Authors may use this guide, in
conjunction with the template files provided with the
distribution, to create or maintain whole documents or sections.
+
+If you're interested in contributing to Python's documentation,
+there's no need to learn \LaTeX{} if you're not so inclined; plain
+text contributions are more than welcome as well.
\end{abstract}
\tableofcontents
discussing future directions for the Python documentation and where
to turn for more information.
+ If your interest is in contributing to the Python documentation, but
+ you don't have the time or inclination to learn \LaTeX{} and the
+ markup structures documented here, there's a welcoming place for you
+ among the Python contributors as well. Any time you feel that you
+ can clarify existing documentation or provide documentation that's
+ missing, the existing documentation team will gladly work with you
+ to integrate your text, dealing with the markup for you. Please
+ don't let the material in this document stand between the
+ documentation and your desire to help out!
+
\section{Directory Structure \label{directories}}
The source distribution for the standard Python documentation
this document, please report the bug at the <a
href="http://sourceforge.net/bugs/?group_id=5470">Python Bug
Tracker</a> at <a href="http://sourceforge.net/">SourceForge</a>.
+ If you are able to provide suggested text, either to replace
+ existing incorrect or unclear material, or additional text to
+ supplement what's already available, we'd appreciate the
+ contribution. There's no need to worry about text markup; our
+ documentation team will gladly take care of that.
</p>
<p> Questions regarding how to use the information in this
report the bug at the <a
href="http://sourceforge.net/bugs/?group_id=5470">Python Bug
Tracker</a> at <a href="http://sourceforge.net/">SourceForge</a>.
+ If you are able to provide suggested text, either to replace
+ existing incorrect or unclear material, or additional text to
+ supplement what's already available, we'd appreciate the
+ contribution. There's no need to worry about text markup; our
+ documentation team will gladly take care of that.
</p>
<p> Questions regarding how to use the information in this