From owner-freebsd-current@FreeBSD.ORG Tue Jan 13 06:12:27 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 839D516A4CE for ; Tue, 13 Jan 2004 06:12:27 -0800 (PST) Received: from otter3.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB8BB43D46 for ; Tue, 13 Jan 2004 06:12:25 -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 i0DECN6T002123; Tue, 13 Jan 2004 08:12:23 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <4003FCB0.90403@centtech.com> Date: Tue, 13 Jan 2004 08:12:00 -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: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= 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> <4003F684.6090907@centtech.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit cc: Tig 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 14:12:27 -0000 Dag-Erling Smørgrav wrote: >Eric Anderson writes: > > >>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. [...] >>Josef already agreed to do the markup (the most tedious part of the >>work) - so now it's just information gathering.. >> >> > >You must have missed the part of this thread where I said "we tried >that before, and it didn't work". > > No, I didn't miss it - I must have misunderstood it. I thought you said you tried having all the developers reporting all the info to someone, and they compile it (which is what I am saying is the more efficient method). However, where you put the [...], I had written: "...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..." and "...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?").. " Which I thought clearly stated "start writing what you do know, and then ping the developers individually about things you don't".. I understand now that you are saying that method did not work either, in which case there isn't much left except writing what he can gather from non developers I suppose. Seems strange that the developers wouldn't want their hard work to be known.. Eric -- ------------------------------------------------------------------ Eric Anderson Systems Administrator Centaur Technology All generalizations are false, including this one. ------------------------------------------------------------------