Status reports - why not regularly?
wkb at freebie.xs4all.nl
Tue Jan 13 02:02:07 PST 2004
On Tue, Jan 13, 2004 at 10:39:03AM +0100, Antal Rutz wrote:
Do you volunteer to write it? Basically it boils down to people experiencing
writing reports as 'real work', so it is not overly popular.
Given that I'm writing the core monthly reports I know why..
> 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).
> My intention is far from hurting anybody. Just want to get the information
> what other OS-users (linux/dragonfly) got.
> freebsd-current at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
---end of quoted text---
| / o / /_ _
|/|/ / / /( (_) Bulte wilko at FreeBSD.org
More information about the freebsd-current