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


Hi Marc, all!

Am Freitag, den 07.01.2011, 02:58 -0500 schrieb Marc Paré:
Le 2011-01-07 02:43, Sophie Gautier a écrit :
On 07/01/2011 10:17, Marc Paré wrote:
[...]
[...]
argh, as I'm the one who has committed this, please let me explain that
this is not organization, it's only information. It's not because it's
on the wiki that it's done.
This page only means: Now that you know what needs to be done, you are
responsible to act or not. No need to be entitled of whatever name for
that. And you don't need to wait for somebody to tell you what to do.
It's here, do it or leave it to someone else.

Thanks. It does however give the group a starting point and direction. 
This is what was meant. It is more productive to get some help from the 
seasoned stakeholders and move on from there. Which is why this is so 
important to get the group moving in one direction.

Maybe a thought, because you already wrote about new members, fresh
ideas, ... within the LibreOffice community. We all value these ideas;
some of these are new to us (great!), some of these have been discussed
numerous times before. Despite the TDF changes, some things won't change
by nature ... so some ideas won't work in our community, or may require
a lot more time to evolve.

Sophie provided the wiki page - which is both excellent in content and
availability (I owe her respect for her time management *g*). As far as
I understand, you value this a starting point and a direction - which is
great to see.

Nevertheless, what I don't understand is, that many of the other
comments within mails - also by Sophie, or Bernhard, or other long-time
contributors - are missed or treated differently. And although we do
need "a breath of fresh air" (a.k.a. community), this support may be as
valuable as "wiki content". We are happy to share our experience.

[...]
We don't need formal leads, we need people able to act and be
responsible in front of the whole community or the whole project if you
prefer. If somebody claims to be member of the website team, whatever he
prefers to do, he should work on what *has to be done*. It's just a
matter of commitment to the group. You can lead a task one day and not
the other, and it reflects more how an open source project is working.

[...]

Personally, I would see leads more as in a mentorship role to the teams. 
If the teams get too way off track, the lead would step in and add words 
of wisdom as well as play an active role in role modelling. There is no 
need to vote on any lead, leaders just shine by themselves and promote 
community growth.

Absolutely! I also prefer the terms "guidance", "support" or
"mentoring". Although the current situation makes it a bit hard to
"shine by themselves" - you already stated that many of you are new to
LibreOffice, and you don't know the experience of other people. It gets
an "chicken and egg" problem as we can see on some mailing lists :-)

In our LibO/TDF situation, I am fine to (temporarily) highlight a few
people who are known specialists for certain topics (within our
community), and are also known to be heavily involved since quite some
time. Would that be helpful? What do you think?

Cheers,
Christoph


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