Hi Olivier, -------- Original-Nachricht -------- > Von: Olivier Hallot <[email protected]>
> > LO went into a new and frenetic development pace which concerns me if no > strong leadership and planning is not well conducted. I slightly disagree here on the term "leadership". I'd rather see "collaboration" here (kathedral vs. bazaar). But after all, some early brainstorming / decision making / specification would be very appreciated, as well as documentation. > > On top of the need for specs (often seen as a unimportant and cumbersome > task by casual developers) I am struggling with the radical changes of > the configuration of the software since release 3.2 that has almost no > document on how to make it work for you, much less on examples and > snippets. Well - good example, that "strong leadership" itself does not really help to prevent such things. The new configuration was implemented under OOo's (Sun's) "strong leadership" model (with all the requests for specification, qa, documentation etc. in place). I don'T want to say, that missing documentation is a good thing - just, that you don't create the docs by enforcing leadership. > > For me, no new feature should be released without proper > /help/user/admin documentation, even if this is is slowing the pace of > the release schedule. "Proper" is a very subjective term. I'd like to see a basic documentation from the developer - a a certain place (something like OOo's spec project, but not such bloated spec document formalism). This should be reviewed and enhacend by other community members (in collaboration with the developer). regards, André -- Unsubscribe instructions: E-mail to [email protected] Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
