SlideServe
Télécharger Obtenir Pro
Menu
Accueil Pro
Préférences
ApparenceLight Aide et commentaires
© SlideServe · v2026

Guidelines for Raising and Managing Issues within Technical Committees

said avatar
said
12 diapositives · 254 Views · Sep 18, 2014

This document outlines the procedures for raising and managing issues within Technical Committees (TCs). All new issues must be documented by emailing the TC mailing list with a detailed description and possible solutions. Issues will be recorded in OSOA's JIRA system, with allocated issue numbers, and discussions must take place solely on the TC mailing list. Resolved issues indicate that a solution has been agreed upon; however, any changes will not be reflected in working drafts until formally incorporated. The process also addresses the reopening of closed or resolved issues along with the necessary voting requirements.

Guidelines for Raising and Managing Issues within Technical Committees - slide 1
01 / 12Guidelines for Raising and Managing Issues within Technical Committees
1 / 17

Télécharger la présentation

Guidelines for Raising and Managing Issues within Technical Committees
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation

  1. SCA TCs Proposed Issues Process Martin Chapman, Assembly Co-chair Anish Karmarkar, BPEL Co-chair Ashok Malhotra, Policy Co-chair Mike Edwards, Assembly Co-chair Michael Rowley, Java Co-chair Henning Blohm, Java Co-chair Sanjay Patil, BPEL Co-chair Simon Holdsworth, Bindings Co-chair David Booz, Policy Co-chair Bryan Aupperle, C &C++ Co-chair

  2. Contents • Major issue states • Tools

  3. New Issues • Raised by TC Members at and in between meetings • Must be recorded by EMAILING to the TC mailing list • Subject should be “NEW ISSUE: [title]” • Email must describe the problem in as much detail as possible • Email MAY propose a solution • Recorded in OSOA’s JIRA • Issue number allocated at this stage even though may not be an issue yet (next page)

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

  5. Open Issue • 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 emails MUST contain a subject line that includes “ISSUE: [issue number]”

  6. “Resolved” Issues • 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 • Sub-State of “Applied” to denote editors have addressed

  7. “Deferred” Issues • An issue that is valid but agreed to be addressed in a future version of the spec. • Agreed by the TC • It is not closed.

  8. Closed Issue • 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 changes have been incorporated into a committee draft • Sub-state to record whether rejected, duplicate, fixed, no action

  9. Re-opening an Issue • A Closed or a Resolved Later Issue can be re-opened. • Requires a 2/3 majority vote via web ballot • 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 into account.

  10. Tools • Email to raise new issue • Use (OSAO hosted) JIRA to record all issues • Allocate issue numbers • Record state changes • Record resolutions and major decisions on an issue. • Always include links to Minutes where decisions made. • Issue discussions MUST NOT take place on JIRA • Only one place for discussions and that is the TC email list • Using OASIS tools is essential for tracking IPR contributions

  11. JIRA Issues • MUST ring-fence OSOA and OASIS issues • Separate JIRA Instances? • Should OASIS host an instance? • OASIS issues on JIRA must be publicly viewable • Write access by issue editors and chairs only.