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


Hi Florian, Steering Commitee, world, :-)

Really great job, Florian. Blogging like [1] this brings home to
people the human side of the SC members (we used to think you were all
wizards sitting on a cloud in the sky, who could accomplish miracles
on first demand).

Blogging is also a great chance to set forth and explain the reasons
for many aspects of TDF policies and decisions, and for explaining
your thoughts and feelings in a place that is rather more sticky and
durable than a mailing list post.

It also makes the TDF blog a hot place to visit regularly for "inside"
news and views.

I would really encourage *other* members of the SC to also blog in the
same way: Charles, Michael, Thorsten, Italo, and all of you.

I really feel that it is one *important key* to good communications
and community cultivation.

I thoroughly enjoyed reading this post, and would love to see blog
posts coming at the rate of about 3 a week... That would only be one
blog post per SC member every once in a while... Could be very
beneficial to community life?

2 cents. ;-)

[1] http://blog.documentfoundation.org/2011/01/22/hassles-and-woes-and-how-to-solve-them/

David Nelson

-- 
Unsubscribe instructions: E-mail to website+help@libreoffice.org
List archive: http://listarchives.libreoffice.org/www/website/
*** All posts to this list are publicly archived for eternity ***

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.