Re: [hybi] Issue tracker openness

Maciej Stachowiak <mjs@apple.com> Thu, 07 October 2010 07:33 UTC

Return-Path: <mjs@apple.com>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9CBE93A6D4A for <hybi@core3.amsl.com>; Thu, 7 Oct 2010 00:33:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.918
X-Spam-Level:
X-Spam-Status: No, score=-105.918 tagged_above=-999 required=5 tests=[AWL=-0.716, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4, 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 r4f-XFovHB-n for <hybi@core3.amsl.com>; Thu, 7 Oct 2010 00:33:48 -0700 (PDT)
Received: from mail-out3.apple.com (mail-out3.apple.com [17.254.13.22]) by core3.amsl.com (Postfix) with ESMTP id 576B43A6CBA for <hybi@ietf.org>; Thu, 7 Oct 2010 00:33:48 -0700 (PDT)
Received: from relay14.apple.com (relay14.apple.com [17.128.113.52]) by mail-out3.apple.com (Postfix) with ESMTP id 354D6ADB5DF8 for <hybi@ietf.org>; Thu, 7 Oct 2010 00:34:50 -0700 (PDT)
X-AuditID: 11807134-b7cacae0000058e0-5a-4cad781ad9fb
Received: from elliott.apple.com (elliott.apple.com [17.151.62.13]) by relay14.apple.com (Apple SCV relay) with SMTP id 26.B8.22752.A187DAC4; Thu, 7 Oct 2010 00:34:50 -0700 (PDT)
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_6OwF90l+i87uhyftUN4aOw)"
Received: from [17.151.76.4] by elliott.apple.com (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPSA id <0L9W009CIT206220@elliott.apple.com> for hybi@ietf.org; Thu, 07 Oct 2010 00:34:49 -0700 (PDT)
From: Maciej Stachowiak <mjs@apple.com>
In-reply-to: <AANLkTi=ogVrCZMwtP1y_J32DJpQ1J6Zph4ki-M9=5Rf+@mail.gmail.com>
Date: Thu, 07 Oct 2010 00:34:48 -0700
Message-id: <4E2F98C5-00A3-4990-AC89-02AD589F42F2@apple.com>
References: <AANLkTinj2FU-kLCW_wvbEXku8cY3eQk-cxGJO2ioLjHi@mail.gmail.com> <20101006181957.GA25685@1wt.eu> <AANLkTi=ogVrCZMwtP1y_J32DJpQ1J6Zph4ki-M9=5Rf+@mail.gmail.com>
To: ifette@google.com
X-Mailer: Apple Mail (2.1081)
X-Brightmail-Tracker: AAAAAA==
Cc: hybi@ietf.org
Subject: Re: [hybi] Issue tracker openness
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hybi>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Oct 2010 07:33:49 -0000

On Oct 6, 2010, at 11:24 AM, Ian Fette (イアンフェッティ) wrote:

> On Wed, Oct 6, 2010 at 11:19 AM, Willy Tarreau <w@1wt.eu> wrote:
> On Wed, Oct 06, 2010 at 10:58:22AM -0700, Ian Fette (????????????????????????) wrote:
> > Currently, only a subset of people have access to open a new issue on the
> > issue tracker. I personally find the issue tracker a very nice tool to use
> > so that we don't lose track of things, especially when it comes to requests
> > like "Please merge X to Y" or "Please add the following text to the spec".
> > Would anyone be opposed to opening up the issue tracker such that anyone can
> > file new issues?
> 
> While it may be useful, it could also end up as we sometimes see on some
> issue trackers, where discussions only happen there instead of on the list.
> The advantage of the list is that people must defend their arguments.
> Sometimes it may become tempting to open a bug when you feel like nobody
> understands your concerns on the list.
> 
> So I'm not completely convinced by the of advantages vs drawbacks.
> 
> Regards,
> Willy
> 
> 
> I don't think that opening an issue obviates you of the requirement to defend your arguments. It's possible that some discussion may move from the list to the issue tracker, and whether that's desirable is an open question (that we could perhaps try to correct for), but I don't see why the fact that the discussion is happening on an issue would mean that there is a lower bar to meet in terms of justification. Frankly, in all the projects I've ever worked on, having an open bug tracker where discussion happens on that bug tracker makes the discussion much easier to follow.

I have had positive experiences with open access to issue/bug trackers for both software projects and standards projects. Allowing anyone to track an issues seems to significantly reduce the risk of comments getting overlooked. It does take some social norms and monitoring to avoid bad patterns, but then, so does a mailing list. It also works much better, in my opinion, for simple editorial comments or reports of trivial errors - it is highly desirable to have those tracked more formally than just email, but not worth the time of the Chairs to enter each one in the tracker, or of the WG to discuss each one in detail.

It seems not to be the norm in the IETF community to let anyone raise issues, but perhaps it would be worth an experiment in this WG.

Regards,
Maciej