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

I understand the logic. I am not too happy about it, but there is no
perfect solution, as you pointed out.

I like the Shapado site. I am not sure we can vote up answers, which I
think is a killer feature. If that is there, it would have my blessing for
an official Q&A. I guess we can worry about migrating a little bit later,
once the thing proves to be viable.

How does that sound to everyone?

"Perseverance must finish its work so that you may be mature and complete,
not lacking anything." -James 1:4

On Tue, Nov 1, 2011 at 12:45 AM, Marc Paré <> wrote:

Le 2011-10-31 15:49, Florian Effenberger a écrit :


thanks everyone for your feedback and your kind offers to help, that's
really much appreciated!

As for which type to use, I must say that a "normal" forum is the only
way, IMHO. We've been experimenting with Nabble, and the result has been
rather mixed. People prefer a forum they know, nothing else. At least
based on my experience.

There are several forums running. What I would like to have is one
"official" LibO forum, either done by us or someone else, that is open
for all languages, and run by a group that does not have members who
openly show hostility towards TDF. I am not saying that everyone does
so, but at least I have heard from some forums, where definitely FUD was
spread, and this leaves me with bad feelings.

What I took from this thread is, that there are two options: One, and the other one the LibreOffice forum.

Anyone already got in touch with those folks? IIRC, there had been
discussions, with some groups, and that didn't work out - but I must
confess I don't know which ones.

Honestly, my preference would be to have our own forum and see if it
works. If not, we tried it, and we don't lose that much.


I really don't think this is a case where anyone can win with any of these
decisions. If is "awarded" the care of the LibreOffice
maintenance of the forums, there will be those who will complain about it
as not being a real native LibreOffice forums. If the TDF raises its own
forums, then there will those who will complain that communities have been
broken and all of the past discussions have been lost. The LibreOffice fork
of OpenOffice has created a shift in community use/support and that is just
the reality of the situation. The code base differences between LibreOffice
and AOO will only get wider over time and LibreOffice may find itself at
this same situation later on.

Therefore, as there would be no clear way to win, it would seem to make
the most sense for the TDF/LibreOffice to create its own forums
infrastructure, offer and invite participation of "already established"
interested forums related to LibreOffice. The TDF/LibreOffice forums could
also offer to help facilitate the migration of any historical data to its
own servers of any group wishing to join the new LibreOffice forums project.

It is still early in the game for LibreOffice and it is the right time to
move on to its own forums services. This will in effect offer our users a
complete office suite service under the same banner that is TDF/LibreOffice.


Unsubscribe instructions: E-mail to 
Posting guidelines + more: http://wiki.****
Netiquette <>
List archive: 
All messages sent to this list will be publicly archived and cannot be

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.