On April 29, 2002, Andrew Savory wrote: >> 3. Author consults topic status list (a web page on cocoon web site) to >> make sure no other draft on this topic is in process. > > Make (3) a part of the How-To? (i.e. as part of preparing to write, they > need to check the topic draft list.)
Right, but shouldn't they at least alert Cocoon about their efforts? Why run the risk of duplicate effort when we have so many holes? <snip reason="agree" /> > >> 7. Editor forwards outline to the SME (subject matter expert). > > This could probably be skipped ... let peer-review catch it. I think > most > of the steps other than the ones highlighted here could be skipped, too. > If they prove to be needed, they can always be added back in. But what if the author is overlooking something? Wouldn't you rather catch this in an outline than in a draft? Why are you adding extra work for SMEs to fill in the missing content? Isn't it the authors job? I don't want to make any extra work for SMEs who are probably busy enough just contributing code! Diana --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
