On Tuesday 26 May 2009 17:43:24 Thomas R. Jones wrote:
> I have been following the openvas community for some time as a silent
> observer. I'd like to know if there is a formal constraint for CR
> processing. Seemingly a developer feels as though a particular CR
> needs implementation than a he/she initiates a "vote". A project of
> such importance and structure should be formally represented and
> maintained. This renders this project in a less than professional and
> exemplary light----which it deserves.
the change request procedure works well now for 32 items.
Though not 100% specified, the process helps and does not get
in the way.
I regard it quite professional to document major changes in the way
we do. Only few Free Software projects do this.
> I present my recommendation that CRs are processed formally. I would
> further present my belief that these transitions be in accordance with
> recognized software development life cycle analysis and design
> techniques.
Good proposals are welcome. Please keep in mind that they need to
be doable in practice when designing a new process.
Best
Jan
--
Dr. Jan-Oliver Wagner | ++49-541-335084-0 | http://www.greenbone.net/
Greenbone Networks GmbH, Neuer Graben 17, 49074 Osnabrück
AG Osnabrück, HR B 202460 | Geschäftsführer: Lukas Grunwald, Dr. Jan-Oliver
Wagner
_______________________________________________
Openvas-discuss mailing list
[email protected]
http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss
