The goal of the project is to create an infrastructure and process for the future development of the extensive Kerberos documentation.
- Complete reference - API, internal functions, data types, macros
- Tutorial for application developers - description on various tasks such as working with credentials, read and verify message, etc
- Cookbook for administrators - Installation, configuration, troubleshooting
- Contributions to Kerberos code - topics on how to write plugins, kerberize cloud, etc
The documentation will be built incrementally. We will analyze what works and what doesn't and correct the course of action as needed.
Details of source documentation
The following fields must be included in the function documentation and should reside in the source code (as the most useful for those who update the code and fix the bugs) :
- Function signature
- Brief function description
- Arguments - [in/out] with description
- Return value description
- Detailed description (optional)
The optional fields may include:
- See also section to refer to the related functions,
- Note section to highlight the specifics of the behaivor
- Examples of the usage
- Snap-shot of the real code involving this function
- Links to KRB5 Wiki Project page, krbdev discussion, RFC document or its section etc
- Version of Kerberos when fuction was introduced or became obsolete
This effectively means that we expect the Doxygen style comments in the headers in the following format:
/** * @brief Some brief descr * * Optional long and very detailed description * * @param[in] context A krb5 library context (see krb5_Z()) * * @return Something useful */ char * KRB5_CALLCONV krb5_X ( krb5_context context)
Also, when available, we suggest to have Part_2 information associated with the particular function in ReST format. It will be kept in the separate file (one file per function). For example:
* Warnings and suggestions Warn about any potential mistakes. Point to other usefull places.
* Links to RFC, wiki Projects, krbdev discussions :rfc:4120 Or if you want to reffer to the specific section of the RFC use the following notation: :rfc:4120#section-5.2 Or link to Kerberos Project page, for example, Disable_DES project <http://k5wiki.kerberos.org/wiki/Projects/Disable_DES>
* Example The place for the function usage examples
Workflow: Putting Part_1 and Part_2 together
- Configure Doxygen to generate output both in xml and html formats. Run Doxygen.
- For each function and data type generate document in ReST format. It is expected that it contains information from Part_1. For the function krb5_X() lets call it krb5_X_p1.
- If the Part_2 documentation for krb5_X() has been already written, there is a file called krb5_X_p2.rst in the designated directory. If not - nothing happens.
- Concatenate krb5_X_p1 and krb5_X_p2.rst (if it exists), add the link to Doxygen generated documentation for this function in html format (generated automatically) and save as a file krb5_X.rst.
- File krb5_X.rst can be used as input for Sphinx
NOTE: We provide Python script to automate steps 2-4.
Documenting data types
How to contribute
- The core team - the administrator - posts the initial list of the tasks (such as API, admin tasks, "How to"-s etc) and further supports it.
- Community can suggest new tasks
- The core team provides templates that, if helpful, may be used by the documentation writers. The most desirable format for the contributed documents is ReST as the easiest to integrate with the mainstream documentation.
- Community can provide the feedback on the documented tasks. There will be a designated mail box firstname.lastname@example.org for this purpose
- Doxygen 1.7.2 <http://www.stack.nl/~dimitri/doxygen/index.html>
- Sphinx 1.0.4 <http://sphinx.pocoo.org>
- Python 2.5+
- Restructured Text markup <http://docutils.sourceforge.net/docs/user/rst/quickstart.html>