Il Mar, 2004-01-13 alle 14:34, Tig ha scritto: > On Tue, 13 Jan 2004 14:25:33 +0100 > Matteo Riondato <rionda_at_gufi.org> wrote: > > > > I'm sorry but I cannot understand your point > > 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. Yes, that can be true, but what if i cannot understand _anything_ about VM or IPsec development ? I have to ask the developer. And what about projects that are not in the tree such as KGI? I have to ask the developer about the status of his project. So writing a status report becomes a work of both users and developers. Writing a status report doesn't mean only "write about the state of the project as it is now" but also "write about what's going to change in the project in the next 2-3 months" and this is something that developers know but normal current users ignore, although they can give suggestions about what they would like to see in the system and they can send patches to see what-they-would-like-to-see-in-the-system been included in the system. (I hope I made myself understandable). I'll be glad to help writing the Status Report, if someone else help me :) 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
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:37 UTC