From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-21-ewr.dyndns.com (mxout-111-ewr.mailhop.org [216.146.33.111]) by lists.bufferbloat.net (Postfix) with ESMTP id 1DB202E0419 for ; Sun, 17 Apr 2011 08:21:46 -0700 (PDT) Received: from scan-21-ewr.mailhop.org (scan-21-ewr.local [10.0.141.243]) by mail-21-ewr.dyndns.com (Postfix) with ESMTP id 10FB070AA for ; Sun, 17 Apr 2011 15:21:45 +0000 (UTC) X-Spam-Score: 0.0 () X-Mail-Handler: MailHop by DynDNS X-Originating-IP: 149.20.54.64 Received: from mainmail.teklibre.com (toutatis.isc.org [149.20.54.64]) by mail-21-ewr.dyndns.com (Postfix) with ESMTP id 190D51244 for ; Sun, 17 Apr 2011 15:21:41 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mainmail.teklibre.com (Postfix) with ESMTP id ED4B012B74A for ; Sun, 17 Apr 2011 08:56:10 -0700 (PDT) Received: from mainmail.teklibre.com ([127.0.0.1]) by localhost (toutatis.sql1.isc.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gl96NXTwCTak for ; Sun, 17 Apr 2011 08:56:10 -0700 (PDT) Received: from [192.168.1.4] (c-68-39-173-20.hsd1.nj.comcast.net [68.39.173.20]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: d) by mainmail.teklibre.com (Postfix) with ESMTPSA id 948A312B6AB for ; Sun, 17 Apr 2011 08:56:10 -0700 (PDT) Message-ID: <4DAB0582.1040903@taht.net> Date: Sun, 17 Apr 2011 09:21:38 -0600 From: Dave Taht User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.14) Gecko/20110223 Thunderbird/3.1.8 MIME-Version: 1.0 To: bismark-devel@lists.bufferbloat.net Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Bismark-devel] Verifying/classifying/prioritizing bugs on a regular basis X-BeenThere: bismark-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: BISMark related software development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Apr 2011 15:21:47 -0000 1) I have a few people that get notified of new bug and feature requests by default on the bismark issues page. I can add more, let me know. 2) It would be good if various people could walk down the existing bug and feature list and verify that a given bug exists, and comment on it as to how to perhaps fix the problem. And take ownership, provide an estimate as to how long it will take to fix, add a start date, add watchers to people that might be interested, etc. http://www.bufferbloat.net/projects/bismark/issues for everything outstanding. As a simple example, I'd like someone to replicate and verify that bug 88 exists... 3) Quite often this above task requires a joint, scheduled meeting, as doing this sort of triage is not a lot of fun - but it is not required to do it in person, over irc works well. 4) The default catagories of people on the list may not be correct. The people with manager perms can promote/demote people into the right catagories. For example, I'm closer to being a developer than a contributor on this project...