From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1G8gvI-00030a-4L for garchives@archives.gentoo.org; Thu, 03 Aug 2006 17:23:52 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.7/8.13.6) with SMTP id k73HN4Xr031034; Thu, 3 Aug 2006 17:23:04 GMT Received: from egr.msu.edu (jeeves.egr.msu.edu [35.9.37.127]) by robin.gentoo.org (8.13.7/8.13.6) with ESMTP id k73HL8dK024359 for ; Thu, 3 Aug 2006 17:21:09 GMT Received: from [35.9.132.199] (feilongpc.dhcp.egr.msu.edu [35.9.132.199]) (authenticated bits=0) by egr.msu.edu (8.13.7/8.13.4) with ESMTP id k73HL9gw021198 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 3 Aug 2006 13:21:09 -0400 (EDT) Message-ID: <44D1F809.5010801@gentoo.org> Date: Thu, 03 Aug 2006 13:20:09 +0000 From: Alec Warner Organization: Gentoo User-Agent: Thunderbird 1.5.0.4 (X11/20060629) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Monthly Gentoo Council Reminder for August References: <20060801093001.C97C864465@smtp.gentoo.org> <44D1BFFD.4040303@gentoo.org> <1154607828.23292.5.camel@localhost> <44D1F4EF.3000209@gentoo.org> <1154612153.17538.26.camel@onyx> <44D20317.6030000@gentoo.org> <1154616531.28858.53.camel@onyx> <44D210C7.90902@gentoo.org> In-Reply-To: <44D210C7.90902@gentoo.org> Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: 7bit X-Archives-Salt: 65dd693f-11fa-4a5a-b3a9-a3850bdd0783 X-Archives-Hash: 8e8026bbafbd4cca89e88751136444e3 > No, not really. Just that I'd expect kinda more proactive approach than > the one demonstrated fex. in > http://bugs.gentoo.org/show_bug.cgi?id=128588#c29 (and a bit more > flexible approach to other alternatives, such as HW/hosting offers we've > received before) and that have been declined for various strange reasons. Linking to a bug where you make crazed comments about how bugs isn't fixed!!!!1111oneone and that dammit someone should do something now!!!1111 doesn't really help your case. I bet if I was infra I'd be wondering what my options were since: bugs is a pretty critical part of developing; AND you can't just host it anywhere; AND the hardware needed for it to perform is expensive; AND they did not know what the problem was at first As in, you don't just grab the first dual proc system that was offered out of some guys basement to host bugs on. You need a dedicated host who will stick around and provide good support should something go wrong. You need expensive hardware ( I believe we got a blade server with 3 blades in it, which is fscking expensive if you haven't priced one out before ). So once again, chill out. They are working on it. And yes bugs is slow and yes it sucks, but bitching about it doesn't accomplish anything :x -- gentoo-dev@gentoo.org mailing list