Status reports - why not regularly?

Tig tigger at onemoremonkey.com
Tue Jan 13 05:33:12 PST 2004


On Tue, 13 Jan 2004 14:25:33 +0100
Matteo Riondato <rionda at gufi.org> wrote:

<snip>
> 
> I'm sorry but I cannot understand your point (this can be my poor
> english fault..). I'm talking about writing a Report, not about Vinum
> or in general software development. If neither of us two can
> understand what each commit means, we cannot write a report about the
> status of the project and we have to ask a developer to explain what
> he did. After that we could write our report.
> Regards
> -- 
> Rionda aka Matteo Riondato
> G.U.F.I Staff Member (http://www.gufi.org)
> BSD-FAQ-it Main Developer (http://www.gufi.org/~rionda)
> GPG key at: http://www.riondabsd.net/riondagpg.asc
> Sent from: kaiser.sig11.org running FreeBSD-5.2-CURRENT
> 

My point was you do not need to understand 'everything' to write a
report. You just need to record what is going on, with enough
information for people to see who is doing what and where.



More information about the freebsd-current mailing list