1 / 6

Guideline to use Bugzilla in SC32WG2 (supersedes SC32/WG2 N0879)

Guideline to use Bugzilla in SC32WG2 (supersedes SC32/WG2 N0879). Bugzilla Drafting Committee SC32WG2 ISO/IEC JTC1 SC32 WG2 Toronto Meeting 2005/09/30. How to initiate a discussion on Bugzilla.

taurus
Download Presentation

Guideline to use Bugzilla in SC32WG2 (supersedes SC32/WG2 N0879)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Guideline to use Bugzilla in SC32WG2(supersedes SC32/WG2 N0879) Bugzilla Drafting Committee SC32WG2 ISO/IEC JTC1 SC32 WG2 Toronto Meeting 2005/09/30

  2. How to initiate a discussion on Bugzilla • Any P-members, participants, Convener and Project editors can post an issue on Bugzilla, discuss it on Bugzilla and resolve it on Bugzilla. • When a new issue is posted, Bugzila automatically send a notification to all the members of Bugzilla distribution list. • It is responsibility of each P-member national body to have at least one person assigned to Bugzilla distribution list. • Bugzilla automatically keep all the discussions on it and send their notifications to all the members of Bugzilla distribution list. • The issue to be posted has to be specific and appropriate to Bugzilla and its description has to be clear. Otherwise, it will not be ‘assigned’ and remain ‘new’ after it is posted. • see ‘Issues not appropriate to Bugzilla’ on slide 5 and 6.

  3. How to put a proposed resolution on Bugzilla • After an issued becomes ‘assigned’, any P-members, participants, Convener and Project editors can post a proposed resolution, otherwise specified. • Editor is responsible to initiate the resolution procedure for each issue. • It should be considered that WG-level work is done on consensus-base (i.e. the substantial support of the P-members is necessary.) • The days given for reviewing is basically 28 calendar days after it is posted, but may change depending on the issue. • Deadline should be stated by a calendar day in terms of GMT. • Any P-members, participants, Convener and Project editors who are not satisfied with the proposed resolution can post a counter proposed resolution. • Basically, another 28 calendar days should be given also to the counter one.

  4. Several Notes • For any issue that is not resolved yet, any P-members, participants, Convener and Project editors who think that the issue is inappropriate to be resolved on Bugzilla can raise an opposition, then the issue cannot be resolved on Bugzilla but the discussion on it can be continued on Bugzilla. • For any issue whose resolution procedure initiated by the editor but not yet resolved yet, any P-members, participants, Convener and Project editors who think that the resolution procedure is inappropriate can raise its change proposal to the editor, then the editor has to consider the proposal. • Any P-members, participants, Convener and Project editors who recognize that Bugzilla does not make proper notifications are responsible to notice the fact to all. Then, all the discussion on Bugzilla has to be halted until Bugzilla comes to make proper notifications.

  5. Issues not appropriate to Bugzilla (1 of 2) • Issues related to the following resolutions that are usually made at the WG2 meeting are not appropriate to Bugzilla. • Section 1 - Programme of Work Resolutions • Resolution WG 02 / 1: SC 32/WG 02 Programme of Work and Project Editor Assignments • SC 32/WG 02 approves the Programme of Work, Target Dates and Project Editor Assignments contained in… • Resolution WG 02 / 2: SC 32/WG 02 Project Subdivisions • SC 32/WG 02 approves the following subdivisions and minor enhancements to existing work: • SC 32/WG 2 instructs its Convener to forward these subdivisions to SC 32 for endorsement. • Resolution WG 02 / 3: SC 32/WG 02 Project Withdrawals • SC 32/WG 02 approves the following withdrawals from existing work: • SC 32/WG 02 instructs its Convener to forward these withdrawals to SC 32 for endorsement. • Resolution WG 02 / 4: Standards Due for Periodic Review • SC 32/WG 02 approves the following: • SC 32/WG 02 instructs its Convener to inform SC 32 of the above recommendations. • Resolution WG 02 / 5: New Projects • SC 32/WG 02 approves the following: • Upon receipt of texts, SC 32 WG 02 recommends that SC 32 submit to JTC 1 the referenced Proposals for New Work Items: • Resolution WG 02 / 6: Study Period • SC 32 WG 02 recommends that SC 32 submit to JTC 1 the following Proposals for Study Period:

  6. Issues not appropriate to Bugzilla (2 of 2) (Continued from the previous slide) • Section 2 - Project Document Resolutions • Resolution WG 02 / 7: Committee Draft (CD) Ballots (CD, PDAM, PDISP, PDTR) • Upon receipt of texts, SC 32/WG 02requests its SC 32 Secretariat to register as CDs, PDAMs, PDISPs, PDTRs and issue letter ballots on the following projects: • Resolution WG 02 / 8: Final Committee Draft (FCD) Ballots (FCD, FPDAM, FPDISP, FPDTR, DCOR) • Upon receipt of texts, SC 32/WG 02requests its SC 32 Secretariat to register as FCDs, FPDAMs, PDTRs, FPDISPs, DCORs and issue letter ballots on the following projects: • Resolution WG 02 / 9: Final Draft International Standard (FDIS) Ballots (FDIS, FDAM, DTR) • Upon receipt of texts, SC 32/WG 02requests its SC 32 Secretariat to register as FDISs, FDAMs, DTRs and submit to ITTF for the following projects:

More Related