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

Le 2010-10-20 00:13, Benjamin Horst a écrit :
Hi Graham,

On Oct 19, 2010, at 4:58 PM, Graham Lauder wrote:
On Wednesday 20 Oct 2010 02:16:38 Benjamin Horst wrote:
On Oct 19, 2010, at 8:56 AM, Graham Lauder wrote:
On Tuesday 19 Oct 2010 12:39:56 Keith Williams wrote:

Yes, I respect Christian, but I don't feel that he is giving this issue
sufficient balance. Having only installed Silverstripe once in a demo
instance is no substitute for real-world experience with a platform. You
may be disappointed in the half-complete Drupal Demo we've tried to set
up, but I and colleagues have implemented Drupal in dozens of real-world
sites for a vast array of clients, and it has stood up to the test.

And please, don't think I don't rate your contribution over the years as
highly. :) and I thank you for giving time to the debate.

Thank you. My only motivation here is to help build the best system I know how, while working 
within the community processes or best practices we have been developing.

The kicker for me though is that at some point in any OSS project roles
change or people get added to teams for this sort of admin.  The number
of admins will expand quickly for all the various projects and the
faster they are up to speed on any CMS, the better.  To me Silverstripe
wins this hands down.

I think quite differently here. There are far more people in the FLOSS
world familiar with Drupal, some of OOo's infrastructure has already been
in Drupal, and new people who have used CMSs in the past likely have
encountered Drupal. It's tested, it's robust, and it's widely known.

Fair comment and I would agree that the Drupal community is extensive and
passionate, however my experience has shown in the past that the passion can
get in the way of practicality, however having said that, my thanks for your
reasoned debate to this point.

Passion without thorough analysis is definitely not the way to make a technical decision. However, 
I don't think we are faced with that situation here. :)

My point was that people who are Drupal Geeks, while they may be out there,
are not always Office Suite Geeks like you and I, the people who will end up
administering this will invariably be the latter

However, my mind is always open and if evidence is shown to the contrary I'll
be happy to put my small weight behind it.

I should probably point out here that the IIRC Daniel Carrera set up the
ingots site on Drupal. Ian Lynch could confirm or
correct that.

Another example of existing Drupal sites in the wide cosmos of OOo, LibO and related sites. 
(Viewing the page source confirms it's using Drupal.)

Once the site is configured, it will be easy enough to administer by technically-savvy people who 
may not be Drupal experts. Any Drupal experts can certainly take a reduced advisory role after 
launch, with no detriment to the project.


Benjamin Horst
646-464-2314 (Eastern)

Thanks for the insightful comment from the both of you. We should have till Friday to make our decisions unless someone advises otherwise. Keep the critiques coming.

It sounds like both CMS fulfil the spec requirements as laid out by Christopher. Arguments for additional advantages will most likely help in determining the choice.


E-mail to for instructions on how to unsubscribe
List archives are available at
All messages you send to this list will be publicly archived and cannot be deleted


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.