From owner-freebsd-advocacy@FreeBSD.ORG Tue Jan 13 07:11:46 2004 Return-Path: Delivered-To: freebsd-advocacy@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B94F416A4DA for ; Tue, 13 Jan 2004 07:11:46 -0800 (PST) Received: from smtp.mho.com (smtp.mho.net [64.58.4.6]) by mx1.FreeBSD.org (Postfix) with SMTP id F197F43DA0 for ; Tue, 13 Jan 2004 07:10:25 -0800 (PST) (envelope-from scottl@freebsd.org) Received: (qmail 12132 invoked by uid 1002); 13 Jan 2004 15:10:22 -0000 Received: from unknown (HELO freebsd.org) (64.58.1.252) by smtp.mho.net with SMTP; 13 Jan 2004 15:10:22 -0000 Message-ID: <400409F4.3090205@freebsd.org> Date: Tue, 13 Jan 2004 08:08:36 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20031103 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Antal Rutz References: <20040113093903.GA84055@mimoza.pantel.net> In-Reply-To: <20040113093903.GA84055@mimoza.pantel.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-advocacy@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: Status reports - why not regularly? X-BeenThere: freebsd-advocacy@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD Evangelism List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2004 15:11:46 -0000 Hi, There seems to have been quite a bit of discussion about this while I was sleeping. Since I'm the one who has done these reports, I'll toss in some comments. The primary reason why the reports have gotten less frequent is because of lack of time on my part. It is _not_ (as some suggested) because developers are too lazy to send me reports when I ask for them. It just happens that whenever it's time to start soliciting reports for the bi-monthly thing, either a release cycle has just start or just ended. So I'm either swamped or highly burnt out. I enjoy putting the reports together, and I really do feel bad that I haven't kept up on them since they are so valuable. The bottleneck in this process is not that it takes too much time/effort to put them together. Taking all of the submissions and turning them into a report takes about 1-2 evenings. There is of course a but of overhead spent on sending the solicitation emails and reminders, but it's not all that bad. It really comes down to me being too busy to remember to start the process. There was a hint at suggesting that we should move to the Linux LKML model, where someone follows the mailing list and writes brief summaries on it. I think that that would be an excellent project, and I highly encourage someone to take that on. However, I don't think that that would totally replace the bi-monthly report, since those allow the developers to go into a bit more detail than what can be summarized on a list. So I think that both forms of reports could complement each other very well. As for having another bi-monthly status report, let me start up the process tonight for the Nov-Dec 2003 report. Stay tuned..... Scott Antal Rutz wrote: > Hi. > > I just read the status report of the year 2003 from DragonFlyBSD. > > I ask (not only) myself why don't we have something like this monthly or > bi-monthly. I regularly read the cvs-src and current lists, but surely there > are many developments that I can't understand from the commit messages. And > what about a regular user, who just reads some relnotes and can't see the > continuous work? > > There are weekly news about what code got into the latest Linux kernels. > But I'd like to know what's going on about FreeBSD! I don't think so that it > would take a whole day to just write down a few lines every (second) month > about the work is in progress and/or done. > > The last of these reports was written in September last year (by Scott Long > and Robert Watson). > pity. > > My intention is far from hurting anybody. Just want to get the information > what other OS-users (linux/dragonfly) got. > > -- > > > --arutz > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >