Author: | David Goodger |
---|---|
Contact: | goodger@python.org |
Date: | 2005-03-23 02:01:57 +0100 (Wed, 23 Mar 2005) |
Revision: | 3092 |
Copyright: | This document has been placed in the public domain. |
The latest working documents may be accessed individually below, or from the docs directory of the development snapshots. They are also distributed with the latest project release package, but those may not be completely up to date.
Docutils stakeholders can be categorized in several groups:
There's a lot of overlap between these groups. Most (perhaps all) core-developers, component-developers, client-developers, and re-implementers are also end-users. Core-developers are also client-developers, and may also be component-developers in other projects. Component-developers are also client-developers.
These files are for all Docutils stakeholders. They are kept at the top level of the Docutils project directory.
README.txt: | Project overview: quick-start, requirements, installation, and usage. |
---|---|
COPYING.txt: | Conditions for Docutils redistribution, with links to licenses. |
FAQ.txt: | Docutils Frequently Asked Questions. If you have a question or issue, there's a good chance it's already answered here. |
BUGS.txt: | A list of known bugs, and how to report a bug. |
HISTORY.txt: | Change history log. |
THANKS.txt: | Acknowledgements. |
Docutils-general:
Many of these files began as developer specifications, but now that they're mature and used by end-users and client-developers, they have become reference material. Successful specs evolve into refs.
Docutils-general:
Although not in the "ref" directory, PEP 258 is a must-read reference for any Docutils developer.
Prehistoric:
Please note that PEPs in the master repository may not be current, whereas the local versions are.
PEP 258 is an overview of the architecture of Docutils.
Docutils-general: