HI, Could I offer one observation. OJ does not have to carry the whole load on this. The QA group had this idea of getting an earlier cut of the package to a small group of testers. There is then an opportunity for the documentation group to leverage that.
If there where a way to let this small group know what is needed from the documentation side they might be able to help. Actually there is a way, ask? On 9/24/07, Uwe Fischer <[EMAIL PROTECTED]> wrote: > Hi, > > Frank Schönheit - Sun Microsystems Germany wrote: > > Well, I can understand other point of views here, too. In fact we have a > > number of different consumers of specifications (at least somebody who > > needs to write end-user documentation from it, and somebody who needs to > > implement it), and perhaps it really is not feasible to (try to) address > > all those with a single document. > > > > Which then would mean we have a gap between the specification writer and > > the end user, which needs to be filled by somebody. Normally this is the > > author of the online help. As much as I appreciate what those people are > > doing (Really, Uwe!), this is a pretty difficult task which perhaps > > cannot (always) be accomplished by somebody who itself does not have the > > "deepest technical knowledge in the matter", as I called it (no offense > > to anybody, in particular not to Uwe :). > > > > since you called me by name: in this case the problem seems to be that > the author of the Spec did not provide any user documentation (and that > is normally not necessary), while at the same time the application help > is still in the very early days of refinement. So the user has no > sufficient information to use the feature at this time. > If you look into the help file sources, you'll find dozens of comments > like "more info needed" or "must test this" etc., especially in the Base > help files. > Normally, these comments will be resolved by adding the missing > information within some time. But we all know that there is not always > enough time to do what should be done. Priorities must be set, and more > often than we want a file must be published without the desirable > refinement. > May be we should discuss whether a feature *can* be released without > appropriate user documentation? > > Uwe > -- > [EMAIL PROTECTED] - Technical Writer > StarOffice - Sun Microsystems, Inc. - Hamburg, Germany > http://www.sun.com/staroffice > http://documentation.openoffice.org/online_help/index.html > http://wiki.services.openoffice.org/wiki/Category:OnlineHelp > http://blogs.sun.com/oootnt > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
