Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 13 Jan 2004 14:25:33 +0100
From:      Matteo Riondato <rionda@gufi.org>
To:        freebsd-current@freebsd.org
Subject:   Re: Status reports - why not regularly?
Message-ID:  <1074000332.18384.43.camel@kaiser.sig11.org>
In-Reply-To: <20040114001137.5ce8983b@piglet.goo>
References:  <20040113093903.GA84055@mimoza.pantel.net> <1073998390.18384.19.camel@kaiser.sig11.org> <20040114001137.5ce8983b@piglet.goo>

next in thread | previous in thread | raw e-mail | index | archive | help

--=-++BnDxriMDzAywbZArsB
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Il Mar, 2004-01-13 alle 14:11, Tig ha scritto:
> On Tue, 13 Jan 2004 13:53:10 +0100
> Matteo Riondato <rionda@gufi.org> wrote:
>=20
> <snip>
> >=20
> > Just to give my own opinion:
> > For normal -CURRENT user who haven't a real in-depth knowledge of the
> > system, is not easy to understand what every single commit message
> > means, especially those in regard to difficul topics such as VM
> > development or network device drivers development. That's probably why
> > nobody has volunteered to write a Status Report. It (the Status
> > Report) should be a work both of users _and_ developers.=20
> > These are my 0.2 euro
>=20
> I do not agree with this statement or approch. Something like;
>   "grog continues working on Vinum with a few patches commited from=20
>    the public"
>=20
> Is much better than nothing at all and in most cases is all that is
> required. The developers will be keen to see that work is continuing,
> the people most interested in Vinum will (more than likely) will already
> be aware of what was changed/commit and the general public (like me)
> will be happy to see that Vinum is not rotting away.
>=20
> All that is required is someone (or some people) with the time to put it
> together.

I'm sorry but I cannot understand your point (this can be my poor english f=
ault..).
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 w=
hat he did.
After that we could write our report.
Regards
--=20
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

--=-++BnDxriMDzAywbZArsB
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: Questa parte del messaggio =?ISO-8859-1?Q?=E8?= firmata

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)

iD8DBQBAA/HM2Mp4pR7Fa+wRAiDPAKCtO0qBGWO5KIKFvlbGxAwQJE4y4QCgsM1+
97df5hvhE893p9Pb+oqw8U8=
=6mXl
-----END PGP SIGNATURE-----

--=-++BnDxriMDzAywbZArsB--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1074000332.18384.43.camel>