From owner-freebsd-current@FreeBSD.ORG Tue Jan 13 09:20:38 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 63AFD16A4CE; Tue, 13 Jan 2004 09:20:38 -0800 (PST) Received: from theatre.msu.edu (theatre.msu.edu [35.8.69.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 639A743D4C; Tue, 13 Jan 2004 09:20:35 -0800 (PST) (envelope-from sagejona@theatre.msu.edu) Received: from theatre.msu.edu (c-67-167-140-34.client.comcast.net [67.167.140.34]) (authenticated bits=0) by theatre.msu.edu (8.12.10/8.12.10) with ESMTP id i0DHKVJa035086 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 13 Jan 2004 12:20:31 -0500 (EST) (envelope-from sagejona@theatre.msu.edu) Message-ID: <400428DC.2060108@theatre.msu.edu> Date: Tue, 13 Jan 2004 12:20:28 -0500 From: "Jonathan T. Sage" Organization: MSU Dept of Theatre User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031205 Thunderbird/0.4 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Scott Long References: <20040113093903.GA84055@mimoza.pantel.net> <400409F4.3090205@freebsd.org> In-Reply-To: <400409F4.3090205@freebsd.org> X-Enigmail-Version: 0.82.4.0 X-Enigmail-Supports: pgp-inline, pgp-mime X-Phone: +1-517-974-1428 X-WWW-Home-Page: http://theatre.msu.edu X-PGP-Key-Figerprint: 182C CF3F 93A9 1DAA 2EBE D4D5 A159 96D9 452E A7F1 X-IM: AIM(jonathantsage,spartyman), ICQ(9587621), YIM(wisesage98) Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig1933B109FAEAC757A27CAB15" cc: freebsd-current@freebsd.org Subject: Re: Status reports - why not regularly? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2004 17:20:38 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig1933B109FAEAC757A27CAB15 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Hello - I have to say, I really like the idea of having a status message, more frequnetly than the bi-monthly. While that is a very useful document, I find myself very out-of-the-loop on some things that I would like to know about. I have a spare machine with a very stable net connection right now. What i am going to do, is subsribe it to the commit list, and start attempting to process the list of commits, with messages, and send that report to me on say, a weekly basis. From there, I am going to look at the information i get purly from the messages provided there. My initial thoughts are : 1. a lot of the commits are going to be ports related, and therefore dropped immediatally. this sort of report is handled wonderfully by dan @ freshports, i see no reason to duplicate what he has done 2. a lot of it will be ambigous at best, from there, i think i will start politely e-mailing commiters about what it does. I think that given a long enough time, these e-mails will be less nessasary as the maintainers of this little project get to know "what's going on" so, what do you think? is this a good / bad start, what problems do you see, and who would like to help? most importantly, i do think we need to take the journalist approach to this, and decide who the audience is. developers? experienced admins following -stable or -current? newbies? i'm a big fan of perl, mysql is the database of choice (already installed). thoughts appreciated, i'm ready to start by this weekend. ~j *incedibly hungry snipping machine* -- "Yesterday upon the stair I saw a man who wasn't there, he wasn't there again today, oh how i wish he'd go away" Jonathan T. Sage Lighting / Set Designer Professional Web Design [HTTP://theatre.msu.edu] [sagejona@theatre.msu.edu] [See Headers for Contact Info] --------------enig1933B109FAEAC757A27CAB15 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFABCjfoVmW2UUup/ERAm6aAJ0R0t5jNdHNiEayoWdsxUTGaV1dnwCeI3JC p8m6W6dN4gnXTuho0GGS9x0= =ri7R -----END PGP SIGNATURE----- --------------enig1933B109FAEAC757A27CAB15--