Date: Tue, 13 Jan 2004 08:12:00 -0600 From: Eric Anderson <anderson@centtech.com> To: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= <des@des.no> Cc: freebsd-current@freebsd.org Subject: Re: Status reports - why not regularly? Message-ID: <4003FCB0.90403@centtech.com> In-Reply-To: <xzpeku4t0bt.fsf@dwp.des.no> 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> <xzpeku4t0bt.fsf@dwp.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
Dag-Erling Smørgrav wrote:
>Eric Anderson <anderson@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. [...]
>>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.
------------------------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4003FCB0.90403>