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

On Wednesday 06 October 2010 00:55, Christoph Noack wrote:
Am Dienstag, den 05.10.2010, 10:08 +0200 schrieb Nino Novak:
On Monday 04 October 2010 23:54, Christoph Noack wrote:
Step forward, and share your thoughts,
too, please! But how to get started ... I mean ... without a wiki
to document the statements.

A wiki is a wiki is a wiki - so just set one up and let it
self-organize. Do not define too much contstraints in advance.

It's less about constraints, but to provide some basis to work on it.
Once we get the wiki, it will be (or maybe become) our primary
platform to share information. So my aim is to reduce the initial
hurdles ...

The problem I see (and have addressed in the other mail) are:
- who are *we* ??? Basically, tdf has announced its foundation. Some 
people are setting up an OOo fork & infrastructure. Other do not like 
to mention the word "fork" at all. 

Therefore, I strongly suggest to set up an empty wiki and NOT make the 
mistake to make any assumption about it structure in advance.

At least for me, TDF seems to aim to develop (in general terms) the best 
"ODF-user-interface" possible. But still nobody knows if forking OOo is 
the way to go or - just to bring in some differet ideas - integrating 
KOffice code with OOo code?, or setting up a product independend 
worldwide ODF QA community which just organizes testing? or doing 
mainly UX work? Or... we simply don't know.

And - what structure do all the people involved want? How do we 
organize? Who will be responsible for what? How do we want to organize 
decision processes? Representative elections? and so on...

Therefore my guess is: let the community decide!

Absolutely, that is the reason for my questions :-) Most of you are
already actively using wikis, so why not learn from your experience
right from the start?

Because our experiences are related to different communities / groups. 

My first question would be: Who is willing to take responsibility for 
the wiki? Who does supportive/admin work? Who will support this new 
community - whereever it decides to go?

The opener you are in the beginning, the better the commitment will be 
later as people will get the feeling "I have done it" or "I have 
influenced it, therefore it's my thing".

And concerning "users of the wiki", Liz (being part of the OOo UX
Team), did a survey last year to check whether people are happy with
the OOoWiki:

Do you really just want to copy OOowiki and apply some improvements? 

Well, it's one possibility, but my feeling about this new community 
which is just about starting to form - they should be given a solid 
infrastructure but not told where to go. 

Currently, I lack some more details, but hey, why are we here?

All that said, I'd prefere to have a wiki farm for different
languages and not one multilanguage wiki - just to enhance
usability (mainly the search function).

It seems that we get quite a pile of "related to language"

yes, the international collaboration should be supported as good as 
possible :)

To unsubscribe, send an empty e-mail to
All messages you send to this list will be publicly archived and cannot be deleted.
List archives are available at


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.