Document:
DRAFT-12-06-11-Minutes-IF-Subcommittee.doc

Draft (A preliminary unapproved sketch, outline, or version.)

Details

Submitted By Jeff Waters on 2011-12-06 6:32 pm UTC

Publication Type

None at this time.

Group / Folder

EM Infrastructure Framework SC / Resources

Modified by

Not modified.

Copy

This document is not a copy.

Technical Contact

None at this time.

Download Count

115

Download Agreement

None at this time.

Description

At the December 6, 2011 meeting of the Infrastructure Framework Subcommittee, the members discussed the following topics:

1. TOPIC: Is the DE 2.0 draft close to public review? (Answer: Yes. Chet advised that the public review should go out by Thursday. This is very good news and thanks so much to Chet and the OASIS staff for this excellent support and progress.)

2. TOPIC: How best should we handle aggregating, discussing and making changes to the working draft? (Answer: The previous process was to note the issues, discuss them and resolve on the telecons, then have one master editor merge the changes and generate the new working draft. It is assumed that we can't make changes to the version accessible to the public as part of the public review. It would be ideal if we had a document management system that allowed multiple people to collaborate on one draft, but that isn't an option at the moment.)

3. TOPIC: How best should we use JIRA to track issues in support of the public review? (Answer: Chet attended today's meeting and began a walk-through of best practices for how to use JIRA to track issues. Chet will arrange a webex for a more detailed walk-through. For example, the OASIS Energy Interoperation TC was cited (http://tools.oasis-open.org/issues/browse/ENERGYINTEROP?report=com.atlassian.jira.plugin.system.project%3Aopenissues-panel) as an example of tying issues to specification components and enabling effective filtering by practices such as (a) creating JIRA components for each major part of a specification (e.g. schema, specification, note, etc.); (b) using the Environment field to specify the name of the person who originally made the comment; and (c) specifying the working draft version impacted.)

References:

(1) DE 2.0 CSD Request Tracker: http://tools.oasis-open.org/issues/browse/TCADMIN-759
(2) DE 2.0 Public Review Request Tracker: http://tools.oasis-open.org/issues/browse/TCADMIN-775
(3) Example use of JIRA, Best Practices: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP?report=com.atlassian.jira.plugin.system.project%3Aopenissues-panel