Hi David, > For issue 12719 I attempted to have a faster and more accessible > specification process > This involved developing the spec collaboratively in the wiki > Unfortunately the spec team did not like this idea and have gone for an > OOo template for designing specifications with > This is perhaps better than the previous system, but I think there are > still significant cases where using a wiki is a much faster route for > people (particularly outside contributors) to use to collaboratively > produce a specification.
ACK. A spec is a living document, I don't think it's reasonable to expect it can be written from scratch in a perfect shape. A Wiki is much better suited to reflect this permanent change. This doesn't mean we can't "freeze" the spec once all stakeholders agree it's final, or call it "make a snapshot", by moving the Wiki content to a .odt at some time. > But I would like to propose that this approach to spec generation be > given more thought. +1 I don't think that's the best approach for all cases, but certainly a good one for some. Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Database http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
