GT Release Manuals
From Globus
The purpose of the Globus Toolkit (GT) Release Manuals project is to provide formalized documentation for the components in the official GT distribution.
This Globdev project web page contains information for project committers and contributors.
Contents |
Product Metadata
Overview
| Latest stable cvs module: alliance/toolkit/docs/4.2/4.2.0/ | Latest development cvs tag: not available yet | |
|---|---|---|
| Location | http://www.globus.org/toolkit/docs/4.2/4.2.0/ | not available yet |
| Documentation quality |
13 technologies with a quality rating of A |
not available yet |
| User support | bugzilla | limited |
Release Schedule
The GT Release Manuals release schedule is aligned with the Globus Toolkit release schedule.
Roadmap
Development roadmap for GT Release Manuals
Project Metadata
Committers
- Cristina Williams, chair
- Charles Bacon
- Lisa Childers
- Mats Rynge
- All committers for GT products
- Ben Clifford (added by committer vote in June 2006)
- Dan Fraser (added by committer vote in January 2007)
Development Tasks
Short term development tasks in the GT Release Manuals project are tracked in bugzilla using the process shown here.
Active
Proposed
- list bugzilla ids describing proposed tasks here
Wishlist
- list bugzilla ids describing ideas that developers/contributors might work on here
Mailing Lists
| Developer discussion (gtmanuals-dev) | archive/subscribe/unsubscribe |
| User discussion (gtmanuals-user) | archive/subscribe/unsubscribe |
| Announcements (gtmanuals-announce) | archive/subscribe/unsubscribe |
| Commit notifications (gtmanuals-commit) | archive/subscribe/unsubscribe |
How to subscribe
How to unsubscribe
Search the email archives
FAQ
Coming soon - feel free to add some: FAQ for GT Release Manuals
Policies
In addition to the Globus Alliance Project Guidelines, the GT Release Manuals project observes the guidelines outlined in the Docbook Primer.
The quality of individual GT release manuals is graded as described in the GT Release Manuals Quality Grading Guide.
Guidelines for committers
- For information on checking out docs from the CVS repository, see How to edit docs.
- For information about how the docs are structured as well as best practices for using the DocBook tags, see the DocBook Primer.
- Find the file with the content you are changing/updating. Make your updates and commit back to CVS repository. The website is automatically updated with your changes.
Guidelines for individual contributors
- If you wish to contribute to the documentation but are not a committer, file a bug (using the "documentation" module) for the appropriate version of documentation. See bugzilla.
