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


Hello Marc,

Le Wed, 05 Dec 2012 11:24:09 -0500,
Marc Paré <marc@marcpare.com> a écrit :

Le 2012-12-05 04:18, Jean-Baptiste Faure a écrit :
Hi,

Le 03/12/2012 18:49, Marc Paré a écrit :
[...]
Thanks for all of these suggestions. Here is an additional
suggestion that I would add:

5- Have an official TDF planet for official communication,

I understand what is an official TDF _blog_ for official
communication, but an "official planet", what is it ?

Best regards.
JBF


My suggestions is that http://planet.documentfoundation.org/ would
now be the official planet with the nl planets showing in the right
margin. Or as Cedric suggested on the FR list, a setup such as the
Opensouse site would also work[1], The links at the top would show
the different nl planets and NOT the blogs.

However, I do have some comments about the effectiveness of that site 
which I explained on the FR discuss list. In particular, if we were
to follow such a model, I would suggest:

* links at the top would be nl planets
* link names would all be localised
* there would be a link to the EN planet
* all articles showing on the landing page would be those of official 
TDF/LibreOffice news (no EN blogs other than an Official TDF blog
would show on this landing page)

Ultimately offer the following feature:

* offer registrations offering members the option of picking
favourites (nl planets), permitting them to see only the planets of
their choice once logged in (allow members to be logged in over an
extended 7 days to promote regular visits to the site)

* IMO, we should eventually work towards a "one TDF login does all"
for all of our sites. This will allow us another metric for marketing 
purposes -- even better as these members would be more engaged
members.

IMO, and this comment is what I find after having joined the
community 2 years ago, we should really move away from the EN
language being considered the ALL voice. I agree totally with the
idea of having EN as the "lingua franca" of communication with the
project (and for contributor groups), BUT, what has happened is the
decimation of the EN community. There is no real nl-EN work being
produced by nl-EN members. The overall impression from EN members is
that they do not have their own space and that everyone considers
anything EN tantamount to an official statement from the project.

We need to re-introduce the EN community wherever we can. In doing
so, this will send a clear message to the nl groups that there is no 
language of greater importance and that they can produce 
first-run/first-thought-of ideas in their own communities. If the EN 
community is interested in communicating this to ther members, then
they can easily translate these and post them through their own nl-EN
channels.


A big +1 to your comments!


Thanks,

-- 
Charles-H. Schulz 
Co-founder & Director, The Document Foundation,
Zimmerstr. 69, 10117 Berlin, Germany
Rechtsfähige Stiftung des bürgerlichen Rechts
Legal details: http://www.documentfoundation.org/imprint
Mobile Number: +33 (0)6 98 65 54 24.

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