Status reports - why not regularly?
Josef El-Rayes
josef at daemon.li
Tue Jan 13 06:32:11 PST 2004
Dag-Erling Smørgrav <des at des.no> wrote:
> Eric Anderson <anderson at centtech.com> 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. [...]
> You must have missed the part of this thread where I said "we tried
> that before, and it didn't work".
i think i can cope with scanning through the MAINTAINERS list or
and sending emails asking about the progress and future of
the software, are working on. i do also
follow hackers@ and current@, so i think i notice most
of interesting topics. If i get some input i think it
wont be a problem to create a status report.
-josef
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 479 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20040113/545f57f6/attachment.bin
More information about the freebsd-current
mailing list