Hi Doug,
Thanks for your thoughtful comment. I did ask the OASIS TC admin about it (cc’d) and he said that functionality may not be enabled (if I am remembering correctly), although
it could be. That said; there is something to be said for separation of concerns; consistently using Kavi for ALL document management and JIRA for issue management by just referencing the documents by URL in the issue, which is common in OASIS, I believe.
I suppose it depends on whether you’re a “by reference” or “by value” kinda guy! :-)
Have a great holiday season and New Year!
Best,
Paul
Paul Lipton
CA Technologies
VP, Industry Standards and Open Source
Member, CA Council for Technical Excellence
Office Phone: +1 609 583-9718
Mobile: +1 267 987-6887
Email:
paul.lipton@ca.com
THIS MESSAGE MAY CONTAIN CONFIDENTIAL, PRIVILEGED OR OTHER LEGALLY PROTECTED INFORMATION. IT IS INTENDED FOR THE ADDRESSEE ONLY. IF YOU ARE NOT THE ADDRESSEE
(OR SOMEONE THE ADDRESSEE AUTHORIZED TO RECEIVE THIS MESSAGE), YOU ARE PROHIBITED FROM COPYING, DISTRIBUTING OR OTHERWISE USING IT. PLEASE NOTIFY THE SENDER AND RETURN IT AT OUR COST. THANK YOU.
From: tosca@lists.oasis-open.org [mailto:tosca@lists.oasis-open.org]
On Behalf Of Doug Davis
Sent: Thursday, December 22, 2011 5:42 PM
To: Lipton, Paul C
Cc: tosca@lists.oasis-open.org
Subject: Re: [tosca] Proposal for JIRA Utilization in the TC
Paul,
one change I would suggest is that people upload docs about issues (proposals, etc) into the Jira issue itself - assuming this is possible. Mixing details about an issue between Jira and Kavi
(even if there are URLs pointing to the issues) could be annoying. Keeping it all in one spot seems cleaner to me.
thanks
-Doug
______________________________________________________
STSM | Standards Architect | IBM Software Group
(919) 254-6905 | IBM 444-6905 | dug@us.ibm.com
The more I'm around some people, the more I like my dog.
|
"Lipton, Paul C" <Paul.Lipton@ca.com>
Sent by: <tosca@lists.oasis-open.org>
12/22/2011 05:31 PM
|
|
To
|
"tosca@lists.oasis-open.org" <tosca@lists.oasis-open.org>
|
|
cc
|
|
|
Subject
|
[tosca] Proposal for JIRA Utilization in the TC
|
|
Hi all,
Based on the TC Admin's recommendations, I would like to propose the following definitions and additional Committee Standing Rules in support of our using JIRA for ALL issues/enhancements/proposals/bugs as well as more technically-oriented actions items.
I have taken the liberty of placing this item on our agenda for January 12th. Please see below and have a great holiday and New Year.
Additional TC Standing Rules
=============================
1. Proposals, enhancements, bugs, and any other item that might require a change MUST be in JIRA, or it will not be recognized.
a. Associated presentations and documents may be uploaded to TC's Kavi Working Documents folder and links added to the JIRA issue, as needed.
2. A "New" issue may be created at any time by any member of the TC, or the TC may request that a member open an issue on its behalf.
3. Non-quarate TC meetings or quarate on issues that are less than 1 week old can ONLY take the following actions on JIRA issues:
a. Discuss the issue
b. Request further information (homework)
c. Add other comments
4. Quarate TC meetings can also change the status of an issue and direct the editors to make changes to documents. These constraints apply:
a. The issue MUST be at least one week old
b. Decision to change issue status is by either by achieving consensus of the attending parties or if a member chooses to "call the vote," the decision is by simple majority of those present.
Use Cases
=========
. Primary: Issues raised by the TC (in meetings and outside of meetings)
. Secondary: Other non-trivial action items, e.g., initiating liaison activities, etc.
. Tertiary: Public review comments
JIRA Status Definitions
=======================
. New - has not been discussed in the TC
. Open - has been discussed in the TC, but not yet resolved
. Resolved - A decision has been made, change(s) need to be applied to documents
. Applied - The necessary changes have been applied to documents, but need to be reviewed and approved by the TC
. Closed - No more consideration needed by the TC (any changes mandated have been done and approved) or the TC has chosen to ignore or just comment.
. Deferred - This item is tabled. The TC should try to recommend when this issue should be re-opened.
JIRA Components
===============
Normative Components
Spec
Schema
Non-Normative Components (non-standards track work products)
Primers (possibly)
Presentations (possibly)
Thanks,
Paul
Paul Lipton
CA Technologies
VP, Industry Standards and Open Source
Member, CA Council for Technical Excellence
Office Phone: +1 609 583-9718
Mobile: +1 267 987-6887
Email: paul.lipton@ca.com
THIS MESSAGE MAY CONTAIN CONFIDENTIAL, PRIVILEGED OR OTHER LEGALLY PROTECTED INFORMATION. IT IS INTENDED FOR THE ADDRESSEE ONLY. IF YOU ARE NOT THE ADDRESSEE (OR SOMEONE THE ADDRESSEE AUTHORIZED TO RECEIVE THIS MESSAGE), YOU ARE PROHIBITED FROM COPYING,
DISTRIBUTING OR OTHERWISE USING IT. PLEASE NOTIFY THE SENDER AND RETURN IT AT OUR COST. THANK YOU.
---------------------------------------------------------------------
To unsubscribe, e-mail: tosca-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: tosca-help@lists.oasis-open.org