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


On Wed, 2011-11-30 at 15:58 -0200, Olivier Hallot wrote:
Hi Christian

Em 30-11-2011 15:22, Christian Lohmaier escreveu:
Hi *,

as it was raised in the BOD call: Do we need separate forums for the
various NL-Projects like it was/is the case with OOo?

Each language has Writer, Calc, ..... forums, and a couple of general
ones. Around 10 to 15 forums per language.

This will make the Forum listing quite crowded - and it cannot be
avoided that some languages will appear at the bottom of the page,
while english appears on top...

And while I answered that dedicated categories would work just fine,
thinking about it I'm not so sure anymore. There are just too many
different forums....

What's your opinion/proposal for a solution?

I think that the NL forums could be separated from the main (English) 
forum, and acessed by its own URL like http://nl-forum.libreoffice.org...

Is it feasible? does it makes sense?

Possible yes - from a phpBB stand point, with our without separate
forums, you can do this against a single forum installation with
redirects.


The issue I have is that  an english forum will have near zero 
participation from the non english speaking people (at least from Brazil).

I do recomend we set a pt-BR (*) set of forums for Writer, Calc, ... + 2 
others for announcements/discussion as you indicated.

(*) I am talking to the pt-PT guys to see if we really need 2 separate 
set of forums for portuguese, at least wrt the modules (Calc, writer...)



Does phpBB support subcategories (JForum does not) - and would that be
a solution? I.e. having a list of languages as categories, and each
category having its own set of subcategories, or having a Writer,....
category, and the languages as subcategory.

Have language as category and modules as sub-category, if the above 
cannot be implemented

Both just don't sound right, and the only benefit would be to only
have a single database...

Can we have one DBMS with many (per NL) databases?

Absolutely - the real question is about shared user and security tables,
but that can be done and doing so from scratch, before there are
existing user accounts to merge, would make it much easier.



But it would make the "show recent/active posts" useless for a
majority of the users, as German users don't care about that a new
article was posted in the English or French forums...

Right.


So better to create separate forums? Even have a mix of forum
software? Let NL-project foo use phpBB, and have NL-project bar use
JForum?

I am not in a position to choose between the two. I am more concerned on 
the moderation workload. For me the lower workload, the best.

But that will be may approach: NL-project forums.


Argh - instead of answering questions, the call did bring a much bigger one ;-)

I call that "management". :-)


But at least askbot is settled :-)
right.

Regards

-- 
Olivier Hallot
Founder, Board of Directors Member - The Document Foundation
LibreOffice translation leader for Brazilian Portuguese
+55-21-8822-8812





-- 
Unsubscribe instructions: E-mail to website+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/website/
All messages sent to this list will be publicly archived and cannot be deleted

Context


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.