Documentation Team
This pages assembles some information for those involved in the process of
creating and maintaining documentation for TurboGears and gives pointers to
those that want to contribute to this effort.
We believe that TurboGears is one of the best web development frameworks out
there and that the quality of its documentation should reflect that. The
sentiment stated in the TurboGears project philosophy, "If it isn't
documented, it doesn't exist", serves as the driving idea behind our efforts.
Currently, these efforts are directed towards bringing the documentation for
the TurboGears 1.0 release up to par with this goal by writing missing
pieces, updating old documents and structuring what we have. We are always
looking for volunteers who would like to help out by writing new documentation,
check/update contributions from others, or provide useful comments, criticism
and other suggestions!
Discussion about documentation efforts for TurboGears takes place on the
turbogears-doc Google Group. This is a low-volume, member-only-posting group.
The archive is open to the public. To post on the list, write email to:
turbogears-doc@googlegroups.com
If you have things you'd like to see done, please add them to the wishlist
below:
Here are a few resources for documentation authors. Feel free to add anything
that you deem useful.
| Name |
Wiki editor |
Website editor |
Trac wiki editor |
| Florent Aide |
yes |
yes |
yes |
| Chris Arndt |
yes |
yes |
yes |
| Andrew Brown |
|
|
|
| Kevin Dangoor |
yes |
yes |
yes |
| Iain Duncan |
yes |
|
|
| Elvelind Grandin |
yes |
yes |
yes |
| Karl Guertin |
yes |
|
|
| Ansel Haliburton |
|
|
|
| Paul Johnston |
yes |
|
|
| Adam Jones |
yes |
|
|
| Fred Lin |
yes |
|
|
| Lee McFadden |
yes |
yes |
yes |
| Chris Percious |
yes |
|
|
| Mark Ramm |
yes |
|
yes |
| Diez Roggisch |
yes |
|
yes |
| Peter Russel |
yes |
|
|
| Alberto Valverde |
yes |
yes |
yes |
| Jorge Vargas |
yes |
|
yes |
| Felix Schwarz |
yes |
|
|
| Chris Zwerschke |
yes |
|
yes |
Wiki admins can add new Wiki editors by listing them on the
EditorGroup page.