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

Dear Charles,

Subject: RE : RE: [libreoffice-website] [Drupal] The road ahead and missed    opportunities

Dear Narayan,

I would advise you read the minutes of the latest steerinh committee.



I did read the minutes, thanks to the link provided by Michael. 

I am not clear how a "statement" from SC made a way in the minutes. That's not healthy.

Logically, I haven't seen any discussion at the mail list that can lead to this conclusion. 

It should be circulated well in advance in the agenda and discussed in the mail beforehand, right?

The "statement" from SC reads like a commandment; to be followed by the faithful.

Are we reduced (already) to a cult where the high priests decide everything?

Why can't we behave like an open community?

As I mentioned in other mail, irrespective of the CMS used, the central idea was to create a second 
website that meets the strategic needs of the LibO ecosystem (in particular, the 23 roles). That 
second site is named "Drupal" just for convenience. 

So when did the SC reverse its decision on this?
What's the new approach to achieve the same (or better) outcome?

The Drupal initiative does not hinder any of the current activities.
Neither does it divert any of the volunteers away.

So what's the problem?


Unsubscribe instructions: E-mail to
List archive:
*** All posts to this list are publicly archived for eternity ***


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.