Documentation SIG Status
Emerging Products
The Doc SIG members have produced some tools:
- HTMLgen is now available from Robin Friedrich's starship website, as well as from the Python ftp site (that's a gzipped tar file; possibly an
older version).
- Doug Hellmann has created HappyDoc, a tool for
extracting documentation from Python source code. It differs
from other such applications by the fact that it uses the parse
tree for a module to derive the information and does not import
the module.
- Daniel Larsson's pythondoc package is on starship.
- Daniel's older gendoc package is also on starship.
Structured Text
Early discussions generated the "Structured Text" proposal; the
details of this format are described in Structured Text Formatting Rules. This proposal
does not hold any "official" status.
Continuing questions
The doc-sig discussion should focus on coming to an agreement on the
types of documents that are needed, the format that documentation
should be made available in, and the content or subject matter that
should be covered in those document. The project should also make an
effort to recruit authors. Examples of options available include:
- Types of documents:
- Tutorials and HowTo Papers
- User Guides
- Reference Manuals
- Installation Guides
- Text books
- Books of documented examples
- The format options:
- Write in one format, and generate multiple output formats.
- Linuxdoc
- Bill Janssen suggested something else
- What output formats are needed
- Postscript
- HTML
- info
- troff (-man option)
- native Grail .pyc files ??
- Subject matter:
- Python core
- Extension modules
- Applications
- Applets
THE PSA as a Catalyst
Authors of software would have an incentive to write documentation
according to a common standard if that were a prerequisite for
receiving the PSA stamp-of-approval. For this to work the PSA will need
guidelines to use for the evaluation process. The review guidelines may
include things such as:
- Form and content rules
- A style guide
- Suggested tools such as syntax and spelling checkers
- Document review process
- review goals
- completeness in regards to type and content of documents
- content evaluation for redundancy with existing documents
- content evaluation for inconsistency with existing documents
- Qualifications for proofreader
Having the PSA perform this function of course assume someone is
willing to volunteer or to pay for having documents reviewed. The PSA
stamp would be the carrot. The incentive for participation is quid
pro quo. It should work for a range of circumstances. For instance:
|