Proposed TC Issues Process Martin Chapman. Purpose An issues driven process helps to 1.Untangle un-conflate problems 2.Narrow focus to solving particular.

Slides:



Advertisements
Similar presentations
Doc.: IEEE /0006r0 Submission March 2005 Steve Shellhammer, Intel CorporationSlide 1 What is a CA document? Notice: This document has been prepared.
Advertisements

SERVICE MANAGER 9.2 PROBLEM MANAGEMENT TRAINING JUNE 2011.
Page 1 of 5 UWA Service Desk The Service Desk self service portal allows you (staff or student) to not only monitor the progress of any Incident or request.
PbD-SE Technical Committee First Meeting December 05, 2012.
OASIS OSLC CCM TC Inaugural Meeting 04 February /04/14OASIS Presentation to OSLC CCM TC.
IEEE P1850 IEEE-SA Sponsor Ballot Primer 5 April 2005 Presented by Andy Ickowicz & Noelle Humenick IEEE Standards Activities.
Copyright © AEA — Association of Enterprise Architects 2013 AEA Workgroup Procedures Version of 31 October 2013.
How to Run an Effective Executive Committee Meeting  Diana Stegall, CSP, CFPS, ARM, ALCM, CPCU  RVP Region 5 - Northwest Chapter – President
OData Technical Committee Kick-off July 26, 2012.
IEEE MEDIA INDEPENDENT HANDOVER DCN: REVP m-session-64-closing-report Title: m Session #64 Closing Report Date Submitted:
Why Proposed TC Procedures? Define how TC reaches “completion” of what OASIS calls “Committee Specifications” TC procedures lead up to the OASIS process:
CMIS4DAM TC Inaugural Meeting 03 December /03/14OASIS Presentation to CMIS4DAM TC.
Chris Albrecht Legal Counsel JGC Leadership Training
TOSCA Technical Committee Kick-off December 12, 2011.
SCA TCs Proposed Issues Process Martin Chapman, Assembly Co-chair Anish Karmarkar, BPEL Co-chair Ashok Malhotra, Policy Co-chair Mike Edwards, Assembly.
DICOM to ISO-DICOM Report to joint ISO TC215/WG2 – DICOM WG10 meeting January 24, 2004, San Diego.
Consideration Of Updates And Additional Revisions To Procedures For Conducting Board and Committee Activities Board Item # 2.
Doc.: IEEE /0698r0 Submission May 2015 Xiaoming Peng (I2R)Slide 1 Date: Authors: IEEE aj Task Group March 2015 Report.
Doc.: IEEE / 0404r0 Submission March 2015 Slide 1 TGax PHY Ad Hoc March 2015 Meeting Agenda Date: Authors:
Due Process – ISSAIs and INTOSAI GOVs Roberto José Domínguez Moro Superior Audit Office of Mexico INTOSAI Working Group on Public Debt June 14, 2010.
Doc.: IEEE /0507r0 Submission TGaj CC12 on 10 April 2014 Report Author: Date: NameCompanyAddressPhone Haiming WANGSEU/CWPAN 2.
OData Technical Committee Convener Call June 5, 2012.
Doc.: IEEE /1623r0 Submission November 2006 Jim Petranovich, Conexant Systems, Inc.Slide 1 PHY Ad Hoc Nov 1 Agenda and Minutes Notice: This document.
Agenda & OASIS Procedures
Note At the 2008/03/12 TC meeting the BPEL4People TC formally adopted the SCA TC issue process for issue resolution. The following slides document v3 of.
Contents Major issue states and transitions Tools.
Legal Citation Markup TC Inaugural Meeting 12 February /12/14OASIS Presentation to LegalCiteM TC.
OASIS VIRTIO TC Inaugural Meeting 30 July /04/13 OASIS Presentation to PKCS 11 TC TC Process Overview TC Process is created by OASIS Board, carried.
BU Power Tools & Accessories – PT&A Task management – Definitions
OASIS Overview TC Process & Administration
OASIS OSLC CCM TC Inaugural Meeting 04 February 2014
OASIS TC Process Overview
CTI STIX SC Monthly Meeting
Chris Albrecht Legal Counsel
Agenda 5.11 General Regulations
TGac Ad-hoc lifecycle model
Meeting Procedure.
OCPP TC Inaugural Meeting 07 September 2016
Proposed TC Issues Process
OASIS eTMF TC Inaugural Meeting 16 December 2013
OASIS Overview TC Process
OASIS Overview TC Process
CSAF TC Inaugural Meeting 16 November 2016
SARIF TC Timeline Proposed, approximate.
TGac Ad-hoc lifecycle model
OASIS OSLC Core TC Inaugural Meeting 12 November 2013
OASIS Overview TC Process & Administration
TC Process Specification Flow
OSLC Domains TC Inaugural Meeting 30 September 2016
ARIP TC Inaugural Meeting 22 May 2015
OASIS Overview TC Process
CTI TC Inaugural Meeting 18 June 2015
Legal Citation Markup TC Inaugural Meeting 12 February 2014
OSLC PROMCODE TC Inaugural Meeting 26 March 2014
TGac Ad-hoc lifecycle model
WS-RX TC Process for Specification Development
WS-RX TC Process for Specification Development
IBOPS TC Inaugural Meeting 23 September 2014
OSLC Automation TC Inaugural Meeting 25 March 2014
COEL TC Inaugural Meeting 15 July 2015
Chris Albrecht Legal Counsel
BIOSERV TC Inaugural Meeting 08 July 2015
What is a CA document? Date: Authors: March 2005 March 2005
OASIS VIRTIO TC Inaugural Meeting 30 July 2013
802.11F Meeting Report March 2002 Month 1998 doc.: IEEE /xxx
Avoiding unnecessary delays in the WG Letter Ballot process
Proposal on TSC policy for ONAP release Maintenance
SAE Standards Works Training Module - Useful Tabs
TGn-LB97-General-adhoc-report
Presentation transcript:

Proposed TC Issues Process Martin Chapman

Purpose An issues driven process helps to 1.Untangle un-conflate problems 2.Narrow focus to solving particular bugs, improvements, new features etc 3. Set agendas and run meetings 4.Measure progress (ship when no more issues) 5.Dovetails with Public Reviews

Lifecycle New Issue Closed Open Resolved AppliedDeferred Change Agreed Rejected Reopen WD Updated Edits Approved Edits Rejected Accepted Duplicate/No longer relevant Address in future version

New Issue Raised by TC Members at and in between meetings Must be recorded by ING to the TC mailing list –Subject should be “NEW ISSUE: [title]” – must describe the problem in as much detail as possible – MAY propose a solution Recorded in TC’s JIRA Issue number allocated at this stage even though may not be accepted as an issue

New Issue Template Title: What is the topic Raised By: Name Target: What spec/section is affected, incl version Description: Explanation of problem Proposal: Optional but encouraged

Open State No issue in a TC may be worked upon unless it is opened –Only discussion on new issue is to clarify and decide whether to open or not An opened issue is –a new issue that has been voted to be opened Does not imply acceptance of any proposed resolution – a closed issue that has been voted to be reopened (super majority vote here) Discussion of an issue can take place in meetings and on the mailing list –All s MUST contain a subject line that includes “ISSUE: [issue number]”

Resolved State A solution to an issue has been agreed by vote of the TC The solution requires changes to a document A resolved state means changes are agreed, but have not yet been incorporated into an agreed working draft –Precise wording changes as far as possible –Some resolutions may delegate to editors

Applied State Editors have incorporated agreed resolution into a working draft. Editors only change a working draft by applying resolved issues. A rejected edit places the issue back into resolved state. Edits are approved by a TC adopting a new Committee Draft that contains the edits.

Closed State An issue that will not be worked on anymore by the TC –A new issue deemed out of scope, inappropriate, malformed etc –A duplicate of another issue –An open issue that is now no longer relevant. –A resolved issue whose applied changes have been incorporated into a committee draft Sub-state to record whether rejected, duplicate, fixed, no action

Deferred State An issue that is valid but agreed to be addressed in a future version of the spec. It is not closed.

Re-opening an Issue A Closed or Deferred Issue can be re-opened. Requires a Special Majority vote via web ballot run by the TC chair(s) –Hence a very strong justification needed –Standing rule required Re-opening does not undo a previously resolved issue (i.e. “un-edits”), but new resolution must take old resolution into account.

Raising the Bar With the exception of re-opening an issue all transitions require a majority vote As we get closer to finishing it is typical to raise the bar to open new issues. –Future standing rule and time to be decided by the TC

Tools to raise new issue using template Use TC Specific JIRA (OASIS hosted) to record all issues –Allocate issue numbers –Record state changes –Record resolutions and major decisions on an issue. –Always include public links to Minutes where decisions made. Issue discussions SHOULD NOT take place on JIRA –Discussions on TC list and TC meetings –Use JIRA to record transitions and agreed resolutions. –Editors can work off the “resolved” issues queue