Re: [pbd-se] Draft proposal for comment and issue handling

Gershon,

Terrific write up. Two additional suggestions you all may want to consider.

One of the fields available when create a new issue is the Environment field. Some TCs are using that field to collect the name of the reporter of the issue. Where this comes in particularly handy is for public reviews. You can capture the commenters name and the link to the email from pbd-se-comment@ for each issue you enter. Then, when it comes time for the next public review or other step where you'll need to have a comment resolution log, you can export issues from JIRA into a spread sheet to create the log.

The other field that helps with this is the Version field (there are two - I use Affects Version myself). You can use the Version field to identify the spec and the release for which the issue is being entered. (For example "Privacy by Design for Software Engineers Version 1.0 CSPRD01".) As you go through multiple public reviews, identifying them in the Version field lets you filter out what you received when. See how we do this for the TAB in https://issues.oasis-open.org/browse/TAB/?selectedTab=com.atlassian.jira.jira-projects-plugin:versions-panel

Best,

/chet

On Wed, Nov 12, 2014 at 8:05 AM, Gershon Janssen <gershon@qroot.com> wrote:

Hi all,

I took an action item at the last meeting to bring a draft proposal to the TC for comment and issue handling.

We already have lots of them and maybe more will follow. In order to handle this in an orderly fashion, the idea is to enter everything in JIRA so we can sort, categorize, comment and dispose of comments in such a fashion that it is transparent, traceable, keeps everybody honest and doesn't require me as TC secretary to take extensive meeting notes. We tried Excel and Word but that didn't work out due to the obvious issues: many versions, all different, unclear what happened with comments, you need issue coordinators who merge documents, etc...

Please find attached a short proposal. If the TC agrees to adopt it, we can take the next step and setup JIRA, distribute a short "how-to" (although JIRA is kind of easy), and enter our existing backlog of issues.

Many other TCs use the same system and found it to be quite practical.

Kind regards,

Gershon Janssen

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

/chet [§]
----------------
Chet Ensign
Director of Standards Development and TC Administration
OASIS: Advancing open standards for the information society
http://www.oasis-open.org

Primary: +1 973-996-2298
Mobile: +1 201-341-1393

Check your work using the Support Request Submission Checklist at http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html

TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin

Follow OASIS on:
LinkedIn: http://linkd.in/OASISopen
Twitter: http://twitter.com/OASISopen
Facebook: http://facebook.com/oasis.open

pbd-se message