Re: [sipcore] Tracker Etiquette
"Elwell, John" <john.elwell@siemens-enterprise.com> Wed, 01 September 2010 06:37 UTC
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6671F3A6908 for <sipcore@core3.amsl.com>; Tue, 31 Aug 2010 23:37:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.721
X-Spam-Level:
X-Spam-Status: No, score=-102.721 tagged_above=-999 required=5 tests=[AWL=-0.122, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QgsTAEU1Eiq7 for <sipcore@core3.amsl.com>; Tue, 31 Aug 2010 23:37:06 -0700 (PDT)
Received: from ms01.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 94C8E3A68CE for <sipcore@ietf.org>; Tue, 31 Aug 2010 23:37:06 -0700 (PDT)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms01.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-1352386; Wed, 1 Sep 2010 08:37:36 +0200
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx11-mx (Server) with ESMTP id 52FB41EB82AB; Wed, 1 Sep 2010 08:37:36 +0200 (CEST)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Wed, 1 Sep 2010 08:37:36 +0200
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "James M. Polk" <jmpolk@cisco.com>, Paul Kyzivat <pkyzivat@cisco.com>
Date: Wed, 01 Sep 2010 08:37:35 +0200
Thread-Topic: [sipcore] Tracker Etiquette
Thread-Index: ActJbyOQLJWKiyq9Ry6Hej+wnFuTrAAMFV8g
Message-ID: <A444A0F8084434499206E78C106220CA01C48DAED0@MCHP058A.global-ad.net>
References: <4C7D5E9C.9090908@nostrum.com> <201008312037.o7VKb82b003320@sj-core-5.cisco.com> <4C7D786A.4020704@cisco.com> <201009010046.o810kVwd016967@sj-core-1.cisco.com>
In-Reply-To: <201009010046.o810kVwd016967@sj-core-1.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: SIPCORE <sipcore@ietf.org>
Subject: Re: [sipcore] Tracker Etiquette
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Sep 2010 06:37:09 -0000
> -----Original Message----- > From: sipcore-bounces@ietf.org > [mailto:sipcore-bounces@ietf.org] On Behalf Of James M. Polk > Sent: 01 September 2010 01:47 > To: Paul Kyzivat; James M. Polk > Cc: SIPCORE > Subject: Re: [sipcore] Tracker Etiquette > > ISTM that the first order of business wrt Tickets is to correlate > them to a particular document. Perhaps this is a pull down tab with > minimal ids for each WG item we have (e.g., 'hi' for history-info, > and 'loc' for Location Conveyance). The note to the list will already > say it's [sipcore], so this second level of identification allows doc > editors to quickly know whether a ticket (in the subject line of the > note to the list) is for 'their' doc or not. > > I think the chairs ought to assign what they think is best for a doc > identifier. > > BTW - Geopriv and ECRIT use tickets, but not the doc identifiers, and > as an author of more than one ID within each group, it's a real bitch > (sorry ladies) to track them in my mail app. > > Also, personally I don't like tickets being generated about one of my > docs without any discussion - mostly because I feel kinda blindsided > by having to account for another topic without having a chance to > explain whether or not I believe that ticket's topic is already > covered (or not). In other words, I personally don't have an issue > with bonafide open issues - whether technical or editorial - but I'd > like the opportunity to address the topic before it becomes a ticket. [JRE] MARTINI has used tickets, fairly successfully I think. We are starting to use them in SIPREC, but we have limited experience to date. In both groups, anyone can generate a ticket (or reopen a closed one), which does lead to a free-for-all Potentially it could be a problem, so if we constrain it I would like at least the chairs, not just the editor, to have the ability to open a ticket (assigned to the editor). John > > I believe all the rest of Paul's points fall under these above, and > can be worked out. > > Maybe that's just how I think... > > comments? > > James > > At 04:47 PM 8/31/2010, Paul Kyzivat wrote: > >[as chair] > > > >I've been ignoring the tracker till now, but it seems impossible to > >continue doing so. > > > >ISTM we do need some group norms on this. > >Especially given my lack of experience with the tool, I'm reluctant > >to impose them, at least *yet*. Instead, I'd like to see some > >discussion on how people think this should be used. > > > >Here are a few questions that come to mind: > > > >- can anybody create a new topic? Or should the topics be controlled > > in some way? (e.g. consensus) > > > >- can anybody create a new ticket? Or should ticket issuance be > > controlled in some way? (e.g. consensus) > > > >- is creating a ticket done after discussion, or in lieu of > discussion? > > > >- who is responsible for assigning ownership of a ticket? > > can the author pick anybody he wants? Or should people only be > > allowed to assign ownership to themself? Or should there be > > ownership of topics? > > > >- who can close a ticket? The reporter? The owner? Anybody? > > > >I'd like to hear what people in this WG think about this. (My own > >first reaction is that it would be helpful for wg doc editors to use > >tracker for those things that need to be addressed in a document, > >based on emails from others. I'm not so sure about use beyond that, > >but have an open mind.) > > > >Should I have created a tracker topic "Tracker Etiquette" and > >submitted tickets for each of these questions, rather than > sending this mail? > > > > Thanks, > > Paul > > > >James M. Polk wrote: > >>At 02:57 PM 8/31/2010, Adam Roach wrote: > >> > >>>[as chair] > >>> > >>>Finally, it would be helpful to document authors if you included > >>>something in the ticket name that indicated which document the > >>>tracker issue is on. It doesn't have to be a whole document name; > >>>something like "4244bis" for the history-info draft would > be sufficient. > >>Amen > >>tracking which issues pertain to which docs is a fundamental flaw > >>in this whole process regardless of the WG or doc involved. > >>James > >> > >>>Thank you. > >>> > >>>/a > >>>_______________________________________________ > >>>sipcore mailing list > >>>sipcore@ietf.org > >>>https://www.ietf.org/mailman/listinfo/sipcore > >>_______________________________________________ > >>sipcore mailing list > >>sipcore@ietf.org > >>https://www.ietf.org/mailman/listinfo/sipcore > > _______________________________________________ > sipcore mailing list > sipcore@ietf.org > https://www.ietf.org/mailman/listinfo/sipcore >
- [sipcore] Tracker Etiquette Adam Roach
- Re: [sipcore] Tracker Etiquette James M. Polk
- Re: [sipcore] Tracker Etiquette Paul Kyzivat
- Re: [sipcore] Tracker Etiquette Paul Kyzivat
- Re: [sipcore] Tracker Etiquette Hadriel Kaplan
- Re: [sipcore] Tracker Etiquette James M. Polk
- Re: [sipcore] Tracker Etiquette Worley, Dale R (Dale)
- Re: [sipcore] Tracker Etiquette James M. Polk
- Re: [sipcore] Tracker Etiquette Elwell, John
- Re: [sipcore] Tracker Etiquette Hadriel Kaplan
- Re: [sipcore] Tracker Etiquette Paul Kyzivat
- Re: [sipcore] Tracker Etiquette Paul Kyzivat
- Re: [sipcore] Tracker Etiquette Mary Barnes
- Re: [sipcore] Tracker Etiquette Elwell, John
- Re: [sipcore] Tracker Etiquette Worley, Dale R (Dale)
- Re: [sipcore] Tracker Etiquette Paul Kyzivat
- Re: [sipcore] Tracker Etiquette Worley, Dale R (Dale)