From owner-freebsd-current@FreeBSD.ORG Tue Jan 13 06:48:00 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 B194716A4CE for ; Tue, 13 Jan 2004 06:48:00 -0800 (PST) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC84D43D58 for ; Tue, 13 Jan 2004 06:47:58 -0800 (PST) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.10/8.12.10) with ESMTP id i0DElpdN003785; Tue, 13 Jan 2004 15:47:56 +0100 (CET) (envelope-from phk@phk.freebsd.dk) To: rionda@gufi.org From: "Poul-Henning Kamp" In-Reply-To: Your message of "Tue, 13 Jan 2004 15:14:53 +0100." <1074003293.18384.62.camel@kaiser.sig11.org> Date: Tue, 13 Jan 2004 15:47:51 +0100 Message-ID: <3784.1074005271@critter.freebsd.dk> 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:48:00 -0000 In message <1074003293.18384.62.camel@kaiser.sig11.org>, Matteo Riondato writes : >That's quite a problem, because how can we inform normal users about new >features that will be included, if developers don't tell "anyobody" they >are working on those features? I think you can approach this from a better angle. Think: journalist. That is really what we are looking for here, a journalistic treatment of what's going on in the project. It's very well that people post various emails on the forums and whats not, but what we need here is for somebody to _summarize_, rather than _repost_. And journalists don't know very much about what they write about, they just try to make sense out of it. And journalists soon learn to spot when things happen, and they get better at it with some experience. (One of my uncles were a volounteer fireman, and he knew how to find out if journalists were present: park your car prominently, wear some fireman token visibly, suddenly leave the room with barely an excuse. The bloke who rush out after you is a journalist for the local paper :-) And there certainly isn't anything preventing you from sending an email to a committer going "I saw your commit to src/sys/kern/subr_cowsay.c, could you say a few words about it ?" And similarly, anyone who's been around for some time will soon know to read the subtle signs of people doing a few white-space corrections here, and few details there as something brewing under the cover in that general area. It doesn't quite have to be the level of www.theinquirer.net or washington post, for our little project a lot less will do. You would have more than fullfilled my dreams, if after vacation I could just read the FreeBSD-times, and confidently kill my entire mailbox. Poul-Henning -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.