From worley@shell01.TheWorld.com Thu Nov 8 08:32:07 2012 Return-Path: X-Original-To: salud@ietfa.amsl.com Delivered-To: salud@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4070921F8AFB for ; Thu, 8 Nov 2012 08:32:07 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.723 X-Spam-Level: X-Spam-Status: No, score=-2.723 tagged_above=-999 required=5 tests=[AWL=0.257, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T2ORtJBpcaBr for ; Thu, 8 Nov 2012 08:32:06 -0800 (PST) Received: from TheWorld.com (pcls6.std.com [192.74.137.146]) by ietfa.amsl.com (Postfix) with ESMTP id AE14421F8ADC for ; Thu, 8 Nov 2012 08:32:06 -0800 (PST) Received: from shell.TheWorld.com (root@shell01.theworld.com [192.74.137.71]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id qA8GU40I018175 for ; Thu, 8 Nov 2012 11:30:06 -0500 Received: from shell01.TheWorld.com (localhost.theworld.com [127.0.0.1]) by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id qA8GU3uW607384 for ; Thu, 8 Nov 2012 11:30:04 -0500 (EST) Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id qA8GU35m607398; Thu, 8 Nov 2012 11:30:03 -0500 (EST) Date: Thu, 8 Nov 2012 11:30:03 -0500 (EST) Message-Id: <201211081630.qA8GU35m607398@shell01.TheWorld.com> From: worley@ariadne.com (Dale R. Worley) Sender: worley@ariadne.com (Dale R. Worley) To: salud@ietf.org Subject: [salud] Using the issue tracker X-BeenThere: salud@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Sip ALerting for User Devices working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Nov 2012 16:32:07 -0000 At this point, I think that the remaining work can be split into issues that don't interact very much. I think it would help us keep track of the discussion to put each issue into the "issue tracker" provided by the IETF. The issue tracker is accessible at http://trac.tools.ietf.org/wg/salud/trac/report/1 To log in, click on the link "Login" in the upper-right. You need an "IETF tools" login. You can get an IETF tools login by clicking on "Get Passwd" on the left-side navigation column. Do people think using the issue tracker would be useful? If so, I will copy our discussions into issues. Dale From pkyzivat@alum.mit.edu Thu Nov 8 10:21:04 2012 Return-Path: X-Original-To: salud@ietfa.amsl.com Delivered-To: salud@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56B8C21F86E4 for ; Thu, 8 Nov 2012 10:21:04 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.437 X-Spam-Level: X-Spam-Status: No, score=-0.437 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iJ4rlD3VMOjV for ; Thu, 8 Nov 2012 10:21:03 -0800 (PST) Received: from qmta01.emeryville.ca.mail.comcast.net (qmta01.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:43:76:96:30:16]) by ietfa.amsl.com (Postfix) with ESMTP id E708C21F86A3 for ; Thu, 8 Nov 2012 10:21:03 -0800 (PST) Received: from omta03.emeryville.ca.mail.comcast.net ([76.96.30.27]) by qmta01.emeryville.ca.mail.comcast.net with comcast id M0ct1k0060b6N64A16M3X1; Thu, 08 Nov 2012 18:21:03 +0000 Received: from dhcp-16c4.meeting.ietf.org ([IPv6:2001:df8:0:16:1e9:314a:2ceb:edfd]) by omta03.emeryville.ca.mail.comcast.net with comcast id M6M21k00P2S6iR48P6M34U; Thu, 08 Nov 2012 18:21:03 +0000 Message-ID: <509BF80D.7020203@alum.mit.edu> Date: Thu, 08 Nov 2012 13:21:01 -0500 From: Paul Kyzivat User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121010 Thunderbird/16.0.1 MIME-Version: 1.0 To: salud@ietf.org References: <201211081630.qA8GU35m607398@shell01.TheWorld.com> In-Reply-To: <201211081630.qA8GU35m607398@shell01.TheWorld.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [salud] Using the issue tracker X-BeenThere: salud@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Sip ALerting for User Devices working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Nov 2012 18:21:04 -0000 The trouble with issue tracker is that it is a tool that can be used and abused in many ways. Without careful guidelines for use it quickly becomes a mess. It particularly becomes a mess when it is used for one person to assign deliverables to another person without their consent. I also find that it gives me trouble tracking process. Typically I keep track of what is going on via email history. This more formal mechanism, while in some sense more formal, doesn't necessarily mesh well. IMO this tool is best used in limited ways, such as where the chairs are the only ones to add/edit issues based on discussion in meetings and email. I think it could also be used by an author or group of authors to keep track of things to be done to a draft. Thanks, Paul On 11/8/12 11:30 AM, Dale R. Worley wrote: > At this point, I think that the remaining work can be split into > issues that don't interact very much. I think it would help us keep > track of the discussion to put each issue into the "issue tracker" > provided by the IETF. > > The issue tracker is accessible at > http://trac.tools.ietf.org/wg/salud/trac/report/1 To log in, click on > the link "Login" in the upper-right. You need an "IETF tools" login. > You can get an IETF tools login by clicking on "Get Passwd" on the > left-side navigation column. > > Do people think using the issue tracker would be useful? If so, I > will copy our discussions into issues. > > Dale > _______________________________________________ > salud mailing list > salud@ietf.org > https://www.ietf.org/mailman/listinfo/salud > From laura.liess.dt@googlemail.com Thu Nov 8 11:05:22 2012 Return-Path: X-Original-To: salud@ietfa.amsl.com Delivered-To: salud@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B376E21F8531 for ; Thu, 8 Nov 2012 11:05:22 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.976 X-Spam-Level: X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hedfg3f3rlob for ; Thu, 8 Nov 2012 11:05:22 -0800 (PST) Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id ECF3221F8507 for ; Thu, 8 Nov 2012 11:05:21 -0800 (PST) Received: by mail-ie0-f172.google.com with SMTP id 9so5272492iec.31 for ; Thu, 08 Nov 2012 11:05:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=RXfGczEyJRDRX6IMjvKGM0bVKlEV66uI4C2j/4BMC6k=; b=fg3uuL6WFMV5JfRLgniD+0jYT00rO29A0TmRyqFNftMVgsptnxQdQuiiZfAXSd5h2m O+D1KD/1gbpzfyxTZNUV/T6H/Nl73uj8Xl5JPBGRjVeeik93fUhpE9rUYXeYhIDLExKN XVhnmoyHivEH025exmVOWasio4s5wSqTEm21WCO7XojvR5ncMpbMlMw/yDbMdtlfhyIM KxhW+LDRvExZB19HazIcJo+SlarnBmm4SWrmfjqwTOOoh5VesWVBVfUIDV6hUUaw0ACy IIUwWdEorcHsugpdD60vYkN2BcARgjAm5dws+Hga4BvjieFUIF5VoYWN+EaN/EjiY5Dn rqNw== MIME-Version: 1.0 Received: by 10.42.50.6 with SMTP id y6mr8138931icf.35.1352401521569; Thu, 08 Nov 2012 11:05:21 -0800 (PST) Received: by 10.231.58.80 with HTTP; Thu, 8 Nov 2012 11:05:21 -0800 (PST) In-Reply-To: <201211081630.qA8GU35m607398@shell01.TheWorld.com> References: <201211081630.qA8GU35m607398@shell01.TheWorld.com> Date: Thu, 8 Nov 2012 20:05:21 +0100 Message-ID: From: Laura Liess To: "Dale R. Worley" Content-Type: multipart/alternative; boundary=90e6ba10b07d49712b04ce008441 Cc: salud@ietf.org Subject: Re: [salud] Using the issue tracker X-BeenThere: salud@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Sip ALerting for User Devices working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Nov 2012 19:05:22 -0000 --90e6ba10b07d49712b04ce008441 Content-Type: text/plain; charset=ISO-8859-1 Hi Dale, I read Paul's comment and I don't think that an additional monitoring tool would be usefull. It would make things more complicated and it would take more time untill we finish the draft. Kind regards, Laura 2012/11/8 Dale R. Worley > At this point, I think that the remaining work can be split into > issues that don't interact very much. I think it would help us keep > track of the discussion to put each issue into the "issue tracker" > provided by the IETF. > > The issue tracker is accessible at > http://trac.tools.ietf.org/wg/salud/trac/report/1 To log in, click on > the link "Login" in the upper-right. You need an "IETF tools" login. > You can get an IETF tools login by clicking on "Get Passwd" on the > left-side navigation column. > > Do people think using the issue tracker would be useful? If so, I > will copy our discussions into issues. > > Dale > _______________________________________________ > salud mailing list > salud@ietf.org > https://www.ietf.org/mailman/listinfo/salud > --90e6ba10b07d49712b04ce008441 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Dale,

I read Paul's comment and I don't think that an add= itional monitoring tool would be usefull. It would make things more complic= ated and it would take more time untill we finish the draft.

Kind r= egards,
Laura

2012/11/8 Dale R. Worley <worley= @ariadne.com>
At this point, I think that the remaining work can be split into
issues that don't interact very much. =A0I think it would help us keep<= br> track of the discussion to put each issue into the "issue tracker"= ;
provided by the IETF.

The issue tracker is accessible at
http://trac.tools.ietf.org/wg/salud/trac/report/1 =A0To log in, cl= ick on
the link "Login" in the upper-right. =A0You need an "IETF to= ols" login.
You can get an IETF tools login by clicking on "Get Passwd" on th= e
left-side navigation column.

Do people think using the issue tracker would be useful? =A0If so, I
will copy our discussions into issues.

Dale
_______________________________________________
salud mailing list
salud@ietf.org
h= ttps://www.ietf.org/mailman/listinfo/salud

--90e6ba10b07d49712b04ce008441--