Keeping track of an ever-evolving list of issues such as new features, enhancements, or errors, or tasks yet to be completed in the process of specification or other TC work product development, can be a daunting task; yet it must be done to ensure that highest possible quality of the work product produced.
There are several methods of tracking issues currently in use by OASIS Technical Committees. These include the use of:
OASIS has now installed a JIRA issues tracking system that will be made available to Technical Committees upon request. While any of the existing methods are still viable, Technical Committees may want to consider migrating their existing method to a new JIRA Project.
In accordance with the OASIS Technical Committee Process Policy, Technical Committee Members have read/write access. Access control is at the Project level. All Projects are publicly-viewable.
Each Technical Committee will be a unique Project and identified by Technical Committee name.
Components are used to group a set of related issues. Components may identify Subcommittees or unique work products (that is, specifications or other document types) within a Technical Committee.
There are four (4) roles defined:
There is currently only one workflow available: Technical Committee Issues. Additional workflows can be created based on Technical Committee requirements.
All discussion on issues should happen on the Technical Committee's e-mail list and in TC meetings. As much detail as possible should be included when a new issue is opened. Additionally, the issue should note:
To request a Project, the Chair should send an email message to the OASIS TC Administrator and identify the name(s) of any Issues Editor(s).
NOTE: The issues tracking system is not tied into the OASIS groupware (KAVI) authentication. Permissions must be managed manually.
Copyright © 2008 OASIS Open