Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index

Hi guys.

2011/4/1 Andre Schnabel <>

Hi Olivier,

-------- Original-Nachricht --------
Von: Olivier Hallot <>

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.

+1. Leadership occurs naturally. There's no need for naming a leader.

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

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.

Yeap! There's a lot of examples out there too. Not only about document
creation, but in any community made jobs.
But I don't want to get in Philosofic issues in this thread.

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).

+1. Collaboration is basics.




Paulo de Souza Lima
Técnico em Eletrônica e Administrador
Curitiba - PR
Linux User #432358
Ubuntu User #28729

Unsubscribe instructions: E-mail to
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.