logo_kerberos.gif

Projects/Kerberos Documentation

From K5Wiki
< Projects(Difference between revisions)
Jump to: navigation, search
m (explanation of Part_1 and Part_2 purpose for function documentation)
m
 
(11 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{project-early}}
+
{{project-rel|1.11}}
   
 
== Purpose ==
 
== Purpose ==
   
 
The goal of the project is to create an infrastructure and process for the future development of the extensive Kerberos documentation.
 
The goal of the project is to create an infrastructure and process for the future development of the extensive Kerberos documentation.
  +
The documentation should be useful and correct; it must be detailed, but optimized -- do not be too verbose.
  +
  +
'''The documentation will be built incrementally. We will analyze what works and what doesn't and correct the course of action as needed.'''
  +
Part of the criteria for "what works" is that the documentation should be easy to maintain.
   
 
The actualized documentation will be useful for developers and administrators, both for experienced ones and newcomers. It will address the following topics:
 
The actualized documentation will be useful for developers and administrators, both for experienced ones and newcomers. It will address the following topics:
   
 
* Complete reference - API, internal functions, data types, macros
 
* 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
+
* Tutorial for application developers - description on various tasks such as working with credentials, topics on how to write plugins, etc
* Cookbook for administrators - Installation, configuration, troubleshooting
+
* 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.'''
+
== Documentation for application developers ==
  +
  +
Generally any topic in the Kerberos documentation can cross-reference with function documentation and each other.
   
   
Line 19: Line 23:
   
   
==== Documenting functions ====
+
=== Documenting functions ===
 
 
'''Part_1'''
 
 
   
 
The following fields ''must'' be included in the function documentation and should reside in the source code :
 
The following fields ''must'' be included in the function documentation and should reside in the source code :
Line 29: Line 33:
 
# Detailed description (optional)
 
# Detailed description (optional)
   
+
<pre>
One can see that Part_1 contains the information that is the most useful for those who update the code and fix the bugs. To avoid the code overcrowding and make any additions to the function documentation as simple as possible, we suggest to save additional documentation ( see below Part_2) in the separate location - one file per function..
+
/** Some brief description
+
*
+
* Optional detailed description
'''Part_2'''
+
*
+
* @param[in] arg1 Description of arg1
  +
*
  +
* @return Something useful
  +
*/
  +
char * KRB5_CALLCONV
  +
krb5_X(type arg1)
  +
</pre>
   
 
The ''optional'' fields may include:
 
The ''optional'' fields may include:
Line 46: Line 50:
   
   
This effectively means that we expect the Doxygen style comments in the headers in the following format:
+
==== Workflow ====
 
/**
 
* @brief Some brief description
 
*
 
* Optional detailed description
 
*
 
* @param[in] arg1 Description of arg1
 
*
 
* @return Something useful
 
*/
 
char * KRB5_CALLCONV
 
krb5_X ( type arg1)
 
 
Also, when available, we suggest to have Part_2 information associated with the particular function in ReST format. For example:
 
 
* Warnings and suggestions
 
Warn about any potential mistakes and misuse.
 
Point to other useful routines.
 
 
* 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.
 
# 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''.
+
# For each function and data type generate document in ReST format. 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
 
# File ''krb5_X.rst'' can be used as input for Sphinx
   
   
NOTE: Initially we provide Python script to automate steps 2-4. The whole process will be automated later.
+
=== Documenting data types and macros===
   
==== Documenting data types ====
+
Similar to documenting functions.
 
TODO
 
   
   
 
== How to contribute ==
 
== 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.
+
# 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. See [[Projects/Documentation Tasks]] for more detailed information.
 
# Community can suggest new tasks
 
# 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.
 
# 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 krbdoc@mit.edu for this purpose
+
# Community can provide the feedback on the documented tasks.
 
   
 
== Tools ==
 
== Tools ==
Line 70: Line 74:
 
* Sphinx 1.0.4 <http://sphinx.pocoo.org>
 
* Sphinx 1.0.4 <http://sphinx.pocoo.org>
 
* Python 2.5+ (with lxml extension)
 
* Python 2.5+ (with lxml extension)
  +
* Cheetah 2.4.4 <http://www.cheetahtemplate.org>
 
* Restructured Text markup <http://docutils.sourceforge.net/docs/user/rst/quickstart.html>
 
* Restructured Text markup <http://docutils.sourceforge.net/docs/user/rst/quickstart.html>

Latest revision as of 11:21, 29 October 2013

This project was completed in release 1.11.


Contents

[edit] Purpose

The goal of the project is to create an infrastructure and process for the future development of the extensive Kerberos documentation. The documentation should be useful and correct; it must be detailed, but optimized -- do not be too verbose.

The documentation will be built incrementally. We will analyze what works and what doesn't and correct the course of action as needed. Part of the criteria for "what works" is that the documentation should be easy to maintain.

The actualized documentation will be useful for developers and administrators, both for experienced ones and newcomers. It will address the following topics:

  • Complete reference - API, internal functions, data types, macros
  • Tutorial for application developers - description on various tasks such as working with credentials, topics on how to write plugins, etc
  • Cookbook for administrators - Installation, configuration, troubleshooting.


[edit] Documentation for application developers

Generally any topic in the Kerberos documentation can cross-reference with function documentation and each other.


[edit] Details of source documentation

[edit] Documenting functions

The following fields must be included in the function documentation and should reside in the source code  :

  1. Function signature
  2. Brief function description
  3. Arguments - [in/out] with description
  4. Return value description
  5. Detailed description (optional)
/** Some brief description
 * 
 * Optional  detailed description 
 * 
 * @param[in]  arg1  Description of arg1
 *
 * @return Something useful
 */
char * KRB5_CALLCONV 
krb5_X(type arg1) 

The optional fields may include:

  1. See also section to refer to the related functions,
  2. Note section to highlight the specifics of the behaivor
  3. Examples of the usage
  4. Snap-shot of the real code involving this function
  5. Links to KRB5 Wiki Project page, krbdev discussion, RFC document or its section etc
  6. Version of Kerberos when fuction was introduced or became obsolete


[edit] Workflow

  1. Configure Doxygen to generate output both in xml and html formats. Run Doxygen.
  2. For each function and data type generate document in ReST format. For the function krb5_X() lets call it krb5_X_p1.
  3. File krb5_X.rst can be used as input for Sphinx


[edit] Documenting data types and macros

Similar to documenting functions.


[edit] How to contribute

  1. 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. See Projects/Documentation Tasks for more detailed information.
  2. Community can suggest new tasks
  3. 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.
  4. Community can provide the feedback on the documented tasks.

[edit] Tools

Personal tools