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


On Thu, Jan 20, 2011 at 12:29 PM, Ivan M. <ivanm@patentpending.co.nz> wrote:

Hi Michael, David, all,

On Wed, Jan 19, 2011 at 10:42 PM, Michael Wheatland
<michael@wheatland.com.au> wrote:
David Nelson and myself are organising the inaugural LibreOffice website
team conference call.

To vote on the time please visit: http://doodle.com/wzy78i52av4h6din

Is this the same meeting as the one we already created a Doodle poll
for at [1], or is it something different altogether (in which case, is
the other meeting off?)

In the call we expect to discuss website team leadership, nomination of
team
leaders, coordination of tasks and the way forward for the website team
and
the developments we are responsible for.

Hasn't the nomination of team leaders already been done by the SC? I
was hoping we could finally move forward, but another round of
nominations and discussions is going to delay things further (that
said, I think confcalls are good opportunities to make progress as
long as suitable provisions are made for those who can't attend).

If the SC is OK with this, no problem. However, the last thing I want
is for us to first delay by revisiting previous decisions only to have
them invalidated by the SC which will cause further delays. I'm not
against short term delays for long term gains if this is an
opportunity to move forward (which I hope it is) now that the new
website theme and initial content are up and running, but I also want
to make sure that we won't be wasting time.


We will not be wasting time. The website team as a whole has
been segregated by the communication faults that have occurred.
David and myself agree that the best way forward is for the website team to
stand up together as a grass roots united community team. Demonstrate that
we have the skills required to build the website into a community tool and
build trust with the whole community that we listen to everyone.

One aspect that this entails is definition of scope and setting up teams to
manage these resources. There has been unhappiness at the designation of
leaders by the SC without any consultation with the team involved. David and
I have discussed this at length and we see, as I hope others see, that we
need more scope and definition about our responsibilities. This is not to
disregard the SC statement about the leaders, but the first action of these
SC assigned leaders was to unify the team, get consensus amongst the team
regarding sub-projects and better define the people coordinating these
groups.

The SC is precisely that, a steering body, it is the community which finally
decides where this project ends up by way of positive contribution,
collaboration and communication.

We will not be wasting time, we will be (hopefully) uniting the great
talents that we have at our disposal, generating trust and defining the
roadmap for the website team instead of the chaos theory coordination that
has occurred thus far. I can't see any circumstances where this does not
strongly benefit our team and the community as a whole.

Thanks for your concern, and it is this exact reason that we need this
conference call, to clarify all of these issues and to take responsibility
for the website team's resources.

Michael Wheatland

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