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

Disclaimer: I am on the Drupal team and think that this is the better solution for the LibreOffice CMS solution.

As this conversation just seems to be going in circles, could we just leave it to the fact that the SC did voice its decision that the Drupal solution was to be reviewed at a later date (within 6 months) and that a move would be considered then?

It is therefore logical to consider that, being a volunteer and meritocratic organisation, that if a group decides to work on a Drupal solution, it is their prerogative and, that these contributing members will therefore be able to work on this solution as their time permits. If so many of these members decide to work on the Drupal solution to the detriment of the Silverstripe solution, then, again, the SC will perhaps have to reconsider its choice of CMS accordingly. If the Drupal site seems to have outpaced that of the Silverstripe, the credit should go to the Drupal team contributors who are more adept at creating a Drupal CMS site. It would make no sense to ask a Drupal experienced contributors to slow down because the Silverstripe team is not able to keep up to their development. You can easily see the listing of the Drupal members on the Drupal team membership wiki page.[1] And, the list or interested members still seems to grow.

The Drupal team is currently working hard to deliver this solution within the 6 months delay accorded by the SC. It may, in fact, be able to present to the membership a working site within an earlier time frame that was firstly accorded, thanks to the team's hard work. It will then be up to the membership to give constructive criticism to the newly worked Drupal site to see if this is what will work best for LibreOffice. After all, the same is happening in the documentation team with their different projects. Let's keep an open mind.

Please do visit the Drupal site to see its development[2], please do test out sections of the site when announcements go out for its testing phase, please do criticise in order to help out in order to improve the site. This is all in the spirit of creating a great CMS site of choice for the LibreOffice final home destination.

As to why I consider the Drupal CMS the right solution? Just visit the organisation on the Silverstripe and Drupal wiki pages and this speaks volumes.[3] Also consider that we (LibreOffice membership) have more Drupal-able members who could help out to level out the administration workload, not to mention the offer from a Drupal website development house's offer to help out. We would most likely be able to find more Drupal oriented organisations to help out than Silverstripe. The bottom line is that Drupal help with resources, modules, and most of all technical help are plentiful.

So, let's see, as per SC decision, what kind of site a Drupal LibreOffice would have to offer and let's all concentrate on getting a great CMS to work for LibreOffice.

In the meantime, many of the Drupal team have put aside their time to help out. I had offered help with the documentation and started, but stepped aside for David who has done a fabulous job -- well done David. Your work is awesome! However, with a looming 6-month delay, the Drupal team will get back to work on their proposal and present, again, to the membership and SC what they would consider a better solution for the LibreOffice CMS website.


Drupal Team Member

[1] [2] (you need a login/password to see the real extent of progress on the site) [3]

Unsubscribe instructions: E-mail to
*** 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.