JIRA Issue Tracking System now live

[Robin Cover <robin@oasis-open.org>]

The S-RAMP TC Issue Tracking Project has been created and can be
accessed at:

http://tools.oasis-open.org/issues/browse/SRAMP

Each Member [1] of the TC who did not already have a JIRA account
should have received an email message with their login information.
JIRA accounts have been set up with a userID corresponding to your
OASIS (Kavi) login userID.  When you log in to JIRA for the first
time, please change your password to correspond to your OASIS
(Kavi) password.

Excerpted below is an overview of OASIS TC JIRA Projects.  For more
information about JIRA itself, the JIRA User's Guide is online here:

http://www.atlassian.com/software/jira/docs/v3.13.5/introduction.html

Please let me know if you have questions that are not more
appropriately answered by the S-RAMP TC Chair (Vincent Brunssen,
brunssen@us.ibm.com), Randall Hauch (initial JIRA Project Lead,
rhauch@redhat.com), or one of the specification Editors, e.g.,
Martin Smithson (msmiths@uk.ibm.com).

Best wishes!

Robin Cover
Interim OASIS TC Administrator
OASIS Director of Information Services
Editor, Cover Pages and XML Daily Newslink
Email: robin@oasis-open.org
Staff bio: http://www.oasis-open.org/who/staff.php#cover
Cover Pages: http://xml.coverpages.org/
Newsletter: http://xml.coverpages.org/newsletterArchive.html
Tel: +1 972-296-1783


======= OASIS-hosted Issues Tracking System =======

OASIS has installed a JIRA issues tracking system that will be
made available to any Technical Committees upon request. While
any of the existing methods for tracking TC and specification
issues are still allowable, Technical Committees may want to
consider migrating their existing method to a new JIRA Project.

Access

In accordance with the OASIS Technical Committee Process Policy,
Technical Committee Members have read/write access. Access control
is managed at the Project level. All Projects are publicly-viewable.

Projects

Each Technical Committee is configured as unique Project and is
identified by Technical Committee name.

Components

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.
The TC Chair(s), Editors, and other designated persons will be
responsible for defining Components and defining other usage
conventions appropriate to TC work that needs to be tracked.

[Note: http://www.oasis-open.org/committees/download.php/40622/S-RAMP-TC-Issues-Process.ppt ]

Project Roles

There are four (4) roles defined in an OASIS TC JIRA Project:

TC Chair
TC Editor
TC Member
Anyone

Workflows

There is currently only one workflow available: Technical Committee
Issues. Additional workflows can be created based on Technical
Committee requirements.

* New - When an issue is created it is automatically assigned a status
of New. A New issue has not yet been accepted by the Technical
Committee. A new issue may either be accepted (Open Issue) or rejected
(Close Issue) by the TC. Once an issue has been entered, the system
will automatically send an e-mail to the TC list with the URI.

* Open - An issue accepted by the Technical Committee. Actual discussion
of the issue takes place on the TC e-mail list and should include
the URI to the actual issue.

* Deferred - An issue accepted by the Technical Committee, but agreed
that its resolution will be not be included in the current version.

* Resolved - An issue with an agreed-upon resolution that requires a
change to the work product.

* Applied - An issue to which the agreed-upon resolution has been
incorporated into a draft work product.

* Closed - An issue that has either been rejected or resolved and
incorporated into a Committee-approved work product.

All discussion on issues should happen on the Technical Committee's
general mailing list and in TC meetings. As much detail as possible
should be included when a new issue is opened. Additionally, the
issue should note:

- resolution, if accepted
- reason for closing (completed, duplicate, rejected, etc.)

NOTE: The JIRA issues tracking system is not linked to the OASIS
groupware (KAVI) authentication. Therefore, JIRA user permissions
must be managed manually.


[1]  Note that TC "Observers" are not considered Members with respect
      to write permission for OASIS repositories, etc

http://www.oasis-open.org/committees/process-2010-07-28.php#dMember
http://www.oasis-open.org/committees/process-2010-07-28.php#dObserver