From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-12-iad.dyndns.com (mxout-050-iad.mailhop.org [216.146.32.50]) by lists.bufferbloat.net (Postfix) with ESMTP id 2456A2E0271 for ; Tue, 15 Mar 2011 12:41:57 -0700 (PDT) Received: from scan-11-iad.mailhop.org (scan-11-iad.local [10.150.0.208]) by mail-12-iad.dyndns.com (Postfix) with ESMTP id 5AC5937090D for ; Tue, 15 Mar 2011 19:41:57 +0000 (UTC) X-Spam-Score: 0.1 () X-Mail-Handler: MailHop by DynDNS X-Originating-IP: 75.145.127.229 Received: from gw.co.teklibre.org (75-145-127-229-Colorado.hfc.comcastbusiness.net [75.145.127.229]) by mail-12-iad.dyndns.com (Postfix) with ESMTP id D824237085C for ; Tue, 15 Mar 2011 19:41:55 +0000 (UTC) Received: from cruithne.co.teklibre.org (unknown [IPv6:2002:4b91:7fe5:1::20]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "cruithne.co.teklibre.org", Issuer "CA Cert Signing Authority" (verified OK)) by gw.co.teklibre.org (Postfix) with ESMTPS id A57F95E9C7 for ; Tue, 15 Mar 2011 13:41:53 -0600 (MDT) Received: by cruithne.co.teklibre.org (Postfix, from userid 1000) id 0A09112085C; Tue, 15 Mar 2011 13:41:52 -0600 (MDT) From: d@taht.net (Dave =?utf-8?Q?T=C3=A4ht?=) To: bloat Organization: Teklibre - http://www.teklibre.com Date: Tue, 15 Mar 2011 13:41:52 -0600 Message-ID: <87hbb4f9xb.fsf@cruithne.co.teklibre.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: [Bloat] names for subprojects? X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Mar 2011 19:41:58 -0000 I am setting up (as I mentioned earlier today) a bunch of virtual servers (they will accessible directly via IPv6). I am planning on using boring names for the virtual servers, e.g: fedora.bufferbloat.net and the like. However, as we hope to be doing a lot with openwrt across the board, and doing bleeding edge stuff with it (and yes! Feeding back the patches we can into openwrt as best we can), I was thinking a good name for that subproject (and branch) would be something like "uberwrt". Does that work for people? Other suggestions are desire-able. -- Dave Taht http://nex-6.taht.net