OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

xdi message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Tracking specification draft issues


Fellow TC members,

Drummond asked that I circulate a note to TC members to briefly explain how we will be tracking document draft comments, requests, bugs, etc…

OASIS provides the TC with a hosted version of Atlassian’s Jira [1] software. The TCs jira project can be found at [2] (as well as via the “Issues” link on the TC Kavi home page [3]).

I have used Jira to track specification comments and bugs/nits on many projects, and it works very well. While there are many fancy features Jira includes (some of which we, the TC, are not allowed to suppress), I recommend simply focusing on the following when creating issues:

+ Issue Type: use your own discretion as to which value to select. it is largely subjective anyway
+ Summary: a brief description of the comment (FWIW, many issue list interfaces only include the summary, so be as clear as possible)
+ Assignee: unless you know in advance, best to leave this as automatic (which right now, means unassigned. I will pass through the list periodically to assign issues to the correct party). 
+ Description: The main description of the issue (leave any recommendations to the proposal field)
+ Proposal: If you have specific language in mind, or other concrete directions to an editor, use this field to describe actionable tasks. In most cases, I hope we can use this to track feature changes/corrections, briefly discuss any proposals, and take action on the issue during an "issue review" agenda item every friday
+ Label: these are really “tags”. presently, i cannot think of a use for this field, but open to suggestions.

In addition, any new issue or issue events and any comments on an issue results in an email sent to the XDI-TC mailing list. All OASIS members should have read access, create access and comment access to our jira project. If you do not have access, please let me know.

We will have a QA session, and basic tour of jira on this fridays TC call.

thanks
=peterd

[1] https://www.atlassian.com/software/jira
[2] https://tools.oasis-open.org/issues/browse/XDI
[3] https://www.oasis-open.org/apps/org/workgroup/xdi/

Peter Davis: Neustar, Inc.
Distinguished Engineer, Director, Neustar Foundry
45980 Center Oak Plaza Sterling, VA 20166

The information contained in this e-mail message is intended only for the use of the recipient(s) named above and may contain confidential and/or privileged information. If you are not the intended recipient you have received this e-mail message in error and any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately and delete the original message.




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]