From owner-freebsd-hubs@FreeBSD.ORG Tue Jun 10 16:16:02 2003 Return-Path: Delivered-To: freebsd-hubs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E376937B401 for ; Tue, 10 Jun 2003 16:16:02 -0700 (PDT) Received: from carrick.bishnet.net (carrick.bishnet.net [217.204.9.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D18E43F75 for ; Tue, 10 Jun 2003 16:16:02 -0700 (PDT) (envelope-from tdb@carrick.bishnet.net) Received: from tdb by carrick.bishnet.net with local (Exim 4.20) id 19PsLO-0004We-32; Wed, 11 Jun 2003 00:15:58 +0100 Date: Wed, 11 Jun 2003 00:15:58 +0100 From: Tim Bishop To: Ken Smith Message-ID: <20030610231558.GA11147@carrick.bishnet.net> References: <20030610164328.GD2099@electra.cse.Buffalo.EDU> <200306101848.h5AImAVt006033@lurza.secnetix.de> <20030610212022.GB14325@ns1.xcllnt.net> <20030610213812.GB10251@electra.cse.Buffalo.EDU> <20030610223657.GA15071@ns1.xcllnt.net> <20030610225819.GA11960@electra.cse.Buffalo.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030610225819.GA11960@electra.cse.Buffalo.EDU> User-Agent: Mutt/1.4.1i X-PGP-Key: 0x5AE7D984 X-PGP-Fingerprint: 1453 086E 9376 1A50 ECF6 AE05 7DCE D659 5AE7 D984 Sender: "T.D.Bishop" X-Bishnet-MailScanner-Information: Contact postmaster@bishnet.net X-Bishnet-MailScanner-VirusCheck: Found to be clean cc: freebsd-hubs@freebsd.org Subject: Re: [FreeBSD-Announce] FreeBSD 5.1 Released! X-BeenThere: freebsd-hubs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD Distributions Hubs: mail sup ftp List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jun 2003 23:16:03 -0000 On Tue, Jun 10, 2003 at 06:58:19PM -0400, Ken Smith wrote: > ... I don't mind taking control but doing that right > requires access to more than can just be taken - some of it needs to > be given ... > ... I'm capable of that (been a sys-admin for quite a > while :-) but I don't have the access required. And giving that > kind of access is nothing to be taken lightly ... > ... I'm not sure what to do about that, most of the > activities I could engage myself in to help gain that kind of trust > have nothing to do with the mirror system ... Why not start by being a "mirror coordinator", or similar. You could be the person people go to for (using your example) things like DNS changes - even if you have to pass the request on to a third party to action. In time, more responsibility and power would come? Assuming you're not actually Bill Gates in disguise ;) It'd be good to have a single point-of-contact for mirror issues, and someone who'd be responsible for decision making. In the long run it could make release time a breeze ;) Tim. -- Tim Bishop http://www.bishnet.net/tim PGP Key: 0x5AE7D984