W3C home > Mailing lists > Public > public-ws-policy@w3.org > August 2006

[UPDATED] Use of Bugzilla for WS-Policy Issues

From: Christopher B Ferris <chrisfer@us.ibm.com>
Date: Wed, 2 Aug 2006 11:50:49 -0400
To: public-ws-policy@w3.org
Message-ID: <OF498A071A.C59B9458-ON852571BE.0054C07F-852571BE.00570B57@us.ibm.com>
All,

Thanks, Felix, for putting together the Bugzilla FAQ. 

Paul and I agree that it is important that we conduct all issue discussion 
on the public list
rather than by entering in comments in Bugzilla. It is important that we 
do so to ensure
full transparency and visibility of issues discussion. Note also that 
Issue Owner responsibilities
have been added to the instructions. 

This is an updated summary of what you need to do to handle WS-Policy 
issues with
Bugzilla.

0) First, get an account at:
        http://www.w3.org/Bugs/Public/createaccount.cgi . 

Your mail address will be your user name. Most of the following steps will 
only work after you
have created an account and have logged in (or you will be prompted to log 
in).
        NOTE: every working group member SHOULD get an Bugzilla account 
ASAP.
        Otherwise, certain functions related to issue tracking will not 
work effectively. Failure
        to have a Bugzilla account will not be taken as an excuse for 
owning an issue.

1) How to enter a new issue:
* go to http://www.w3.org/Bugs/Public/enter_bug.cgi?product=WS-Policy
* choose a component, e.g. "Attachment".
        Note: if your issue concerns several documents, choose a compound
        component, e.g. "Framework+Attachment".
* choose a version, e.g. "FPWD" (First Public Working Draft).
* Enter a summary (the "title" or "topic" of the issue).
* Enter a description.
* Assign the issue to YOUR ACCOUNT (unless you are entering on behalf
of someone else), using YOUR email address. 

        NOTE: The default for this field is Felix's email address. Please 
be sure to change this before
        submitting the new issue.

* Normally, leave the "QA Contact" field as it is.
        NOTE: The "QA Contact" gets a notification mails for each new 
issue. The
        default QA contact is public-ws-policy@w3.org. I would propose to 
leave
        this field as "public-ws-policy@w3.org" for each new issue, so 
that the
        whole WG sees the issue on the public ML.
* Press "Commit".

*** NOTE: Steps 2 and 3 below apply only to NON-WG MEMBERS who cannot
post to the public list. ***

2) How to add a comment on an existing issue (NON-WG MEMBERS ONLY):
* go to the issue, e.g. http://www.w3.org/Bugs/Public/show_bug.cgi?id=3543
* Type your additional comment into the field "Additional Comments:  ".
* Press "Commit".

3) How to reply to a specific comment  (NON-WG MEMBERS ONLY):
* go to the issue, e.g. http://www.w3.org/Bugs/Public/show_bug.cgi?id=3543
* Press "reply", e.g.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=3543#add_comment
* Add your comment and press "Commit".

4) Issue Discussion:
All issue discussion SHOULD be conducted on the public mailing list. 
Please include
in new threads a link to the issue in the body and identification of the 
issue number in the Subject: field
of the email.

e.g.

        To: public-ws-policy@w3.org
        From: myemail@example.com
        Subject: Issue 12345: I have heartburn over the proposed 
resolution
        Body:
        All, 
        Regarding issue 12345 [1], the proposed resolution in so-and-so's 
email [2] is
        completely unreasonable. I think we should close the issue with no 
action.

        John Doe

        [1] http://www.w3.org/Bugs/Public/show_bug.cgi?id=12345
        [2] 
http://lists.w3.org/Archives/Public/public-ws-policy/2006Aug/0000.html

5) Issue Owners SHOULD review their respective issues for discussion that 
is not conducted
on-list and send an email to the public mailing list summarizing the 
off-list discussion in the
issue history.  This SHOULD be done prior to any distributed or 
face-to-face meeting
espcially if the issue is up for discussion during the meeting. This will 
ensure that all
WG members have the proper context for the discussion and will also serve 
to ensure 
visibility of the issue discussion.

Additionally, Issue Owners SHOULD update their respective issues with a 
link to
the head of an email thread on the public list, to ensure that the issue 
provides
a complete history of its discussion.

Finally, Issue Owners SHOULD update their respective issues with a link to 
the
approved minutes (NOT the member-only draft minutes, please) for any 
meetings
in which their issue(s) were a topic of discussion.

6) How to find all WS Policy related issues:
        Go to http://www.w3.org/Bugs/Public/buglist.cgi?product=WS-Policy
NOTE: You can set more query options via
http://www.w3.org/Bugs/Public/query.cgi?field-1-0-0=product&product=WS-Policy&query_format=advanced&remaction=&type-1-0-0=anyexact&value-1-0-0=WS-Policy
.
Cheers,

Christopher Ferris
STSM, Software Group Standards Strategy
email: chrisfer@us.ibm.com
blog: http://www.ibm.com/developerworks/blogs/dw_blog.jspa?blog=440
phone: +1 508 377 9295
Received on Wednesday, 2 August 2006 15:51:13 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:33:13 UTC