From owner-freebsd-current@FreeBSD.ORG Tue Jan 13 05:46:15 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 A26B616A4CE for ; Tue, 13 Jan 2004 05:46:15 -0800 (PST) Received: from otter3.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0300243D3F for ; Tue, 13 Jan 2004 05:46:04 -0800 (PST) (envelope-from anderson@centtech.com) Received: from centtech.com (neutrino.centtech.com [10.177.171.220]) by otter3.centtech.com (8.12.3/8.12.3) with ESMTP id i0DDk36T099263; Tue, 13 Jan 2004 07:46:03 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <4003F684.6090907@centtech.com> Date: Tue, 13 Jan 2004 07:45:40 -0600 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tig References: <20040113093903.GA84055@mimoza.pantel.net> <1073998390.18384.19.camel@kaiser.sig11.org> <20040114001137.5ce8983b@piglet.goo> <1074000332.18384.43.camel@kaiser.sig11.org> <20040114003443.260c6738@piglet.goo> In-Reply-To: <20040114003443.260c6738@piglet.goo> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 13:46:15 -0000 Tig wrote: >On Tue, 13 Jan 2004 14:25:33 +0100 >Matteo Riondato wrote: > > > > >>I'm sorry but I cannot understand your point (this can be my poor >>english fault..). I'm talking about writing a Report, not about Vinum >>or in general software development. If neither of us two can >>understand what each commit means, we cannot write a report about the >>status of the project and we have to ask a developer to explain what >>he did. After that we could write our report. >>Regards >>-- >>Rionda aka Matteo Riondato >>G.U.F.I Staff Member (http://www.gufi.org) >>BSD-FAQ-it Main Developer (http://www.gufi.org/~rionda) >>GPG key at: http://www.riondabsd.net/riondagpg.asc >>Sent from: kaiser.sig11.org running FreeBSD-5.2-CURRENT >> >> >> > >My point was you do not need to understand 'everything' to write a >report. You just need to record what is going on, with enough >information for people to see who is doing what and where. > > It would be much more efficient if even *some* of the developers that are working on "new-and-cool" features would at least mention it on the -CURRENT list, or even send an email to the person (people?) working on the report. I know it's too much to ask o have every committer doing this - I would never expect that, but possibly there are a few core people that could occasionaly shoot an email out with some highlights.. The NDIS thing is a great example.. I broke my kernel build when it was first going in, and I didn't even have a clue it was being worked on.. Had it not broken a few builds around the -current waterhole, I think it may have gone somewhat unnoticed (which would be too bad since it is a nice addition). Anyhow, it's a great idea, and I think the "just do it" term applies here - start with what can be figured out, and then hunt committers and start questioning them ("hey, what's this new thing you've been committing a lot of lately?").. Josef already agreed to do the markup (the most tedious part of the work) - so now it's just information gathering.. Eric -- ------------------------------------------------------------------ Eric Anderson Systems Administrator Centaur Technology All generalizations are false, including this one. ------------------------------------------------------------------