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

Wheatbix wrote:

I think that a more appropriate location for these wiki pages would be
on the soon to be created rather than The
Document Foundation wiki.
Remember that the TDF wiki is not for LibreOffice information or
support, it is for community building and development.

I was thinking about this yesterday, and IMO create a whole new wiki is not
the best move: if you are worry by the fact TDF will in the future promote
more projects, this could be easily solved by "meta-tags". For example,
adding a [[Category:LibreOffice]] to the pages about LibO (and
[[Category:other-project]] to the others) should be enough to maintain
But what I see as a real mistake is this:

Stefan Weigel wrote:

The LibO wiki will have separate subdomains for each language, which
means a completely different concept and structure to what we have now.

I think the content on the different locales must be the same whenever
possible, and separate the wiki on different language subdomains defeat the
idea of "content coherence": IMO, the way in which TDF wiki is set up now is
the only possibility for a healthy multilingual project because it easy the
"interaction" between languages.
Just my 2¢
View this message in context:
Sent from the Website mailing list archive at

Unsubscribe instructions: E-mail to
List archive:
*** All posts to this list are publicly archived for eternity ***


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.