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


Hello Michael,

Le Sat, 8 Jan 2011 00:10:35 +0930,
Michael Wheatland <michael@wheatland.com.au> a écrit :

On Fri, Jan 7, 2011 at 8:30 PM, Charles-H. Schulz <
charles.schulz@documentfoundation.org> wrote:

Hello there,



Can you tell me where does this come from? Where this decision
has been discussed and taken and by whom? The fact that we
don't use the OOo site is to satisfy a request that has
nothing to do with quality.

We are an open source project, why should we prevent somebody
to contribute for whatever reason? what are the criteria for
the quality you're talking about, where are they written, who
is the person giving the approval? That would be funny that
people could contribute to OOo but not to LibO...


It is a work in progress. We will be consulting with all of the
stakeholders once things settle down and LibO3.3 has been
released. Rest assured we will be able to change things once a
community consensus has been reached.

We did not want to move focus away from the important areas of
community development at the moment. Hence the comment
previously.

Stay tuned


I must say that I'm left perplexed by all this. Michael, would you
mind telling us:
- who is "We" as "we did not want to move focus away"
- why this secrecy? Do you remember it's an open source project?
- "we will be consulting with all of the stakeholders... " so let me
 rephrase: you're doing something apparently in secret then will
 battle hard to defend it in front of the community? That's about
the most unproductive thing I can think of here, and it reminds me
of the Drupal misunderstanding. Nobody has ever talked about an
extension store/website, although it's definitely something we need
to address. But working this way around just does not help.


I don't want to seem rude, but there seems to be a disproportionate
amount of 'push back' within the website mailing list, while groups
and individuals are working hard to build a better future for our
community. Regardless of the development style, or whether it is
received well from the community during consultation and even if
ideas are not implemented, could I suggest everybody attempts to take
an encouraging attitude towards new ideas and people willing to put
hard work in to any idea or project. It is the responsibility of the
people doing the work to consult and present their idea and
development to the community at which point feedback and (hopefully)
constructive criticism will always occur. (This is not a direct
reference to Charles, but a feeling that I have from participating in
and watching the mailing lists).


Certainly so Michael, what is wanted is a contributions-based culture. 

There is no secrecy involved with this or any other
ideas/developments I am involved in. It was an idea floated inside
the website mailing list, wiki pages and instant chat discussions
between the website team (Not IRC unfortunately).
The idea was roughed out and as we have made clear through the website
mailing list a number of times it is very easy to create a rapid
prototype to 'show' the idea rather than tell it.


Okay, so indeed it's not exactly secrecy :-) Would you mind pointing
out some of the wiki pages ?

Best,
Charles.

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