Date: Wed, 14 Jan 2004 00:34:43 +1100 From: Tig <tigger@onemoremonkey.com> To: freebsd-current@freebsd.org Subject: Re: Status reports - why not regularly? Message-ID: <20040114003443.260c6738@piglet.goo> In-Reply-To: <1074000332.18384.43.camel@kaiser.sig11.org> References: <20040113093903.GA84055@mimoza.pantel.net> <1073998390.18384.19.camel@kaiser.sig11.org> <20040114001137.5ce8983b@piglet.goo> <1074000332.18384.43.camel@kaiser.sig11.org>
index | next in thread | previous in thread | raw e-mail
On Tue, 13 Jan 2004 14:25:33 +0100 Matteo Riondato <rionda@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.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040114003443.260c6738>