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

On Wed, Oct 20, 2010 at 12:05 PM, Christian Lohmaier < <>>wrote:

Hi Andrea, *,

On Wed, Oct 20, 2010 at 1:26 PM, Andrea Pescetti
<> wrote:
Marc Paré wrote:

A proper discussion would not fit the deadlines and tools the Document
Foundation has now: if a decision has to be taken now, it will miss the
bigger scope. If the Document Foundation must choose a tool that will be
flexible enough to rebuild all the current infrastructure
on it

No. I strongly disagree. Not one tool that can do all.
No. Really seriously Drupal can do some very impressive things and in years
of using it, it does what is needed.  Its actually a revolutionary bit of
software, you just need to know it beyond a demo on CMSreport.

(e.g.: OOo site; Extensions; TCM; QATrack),

And even that: Duplicating the extensions site would be a waste of
time and efforts. There are already two repositories, the OOo one, the
FSF one. It would be bad if there would be another one, just for the
sake of having it.
LO should be compatible to OOo in that regard, Extensions should run
on OOo, LO, other derivates, thus a dedicated site is a nogo.

then Drupal is that
tool; I can't imagine how to rebuild the Extensions site and all
processing in Silverstripe, for one.

It would involve creating an appropriate module. But again, I'd not
see that as a good idea.
The extensions site has a different target user group, and a different
contributers group, so I don't see any reason to try to cover it with
the same tool that is used for the website.

Very Likely any functionality you want in Drupal will just use one of the
7,000 available modules.  It's actually very hard to find something you
can't already do with Drupal very well.

2) Moving to a database-based CMS can imply loss of traceability of
changes. The current CVS infrastructure, as bad as it can be, allows to
see a full log of changes very easily. Drupal has a killer feature here:
site settings can be exported to PHP code, shared among a distributed
development team through any revision control system (SVN, git,
whatever) and applied in a safe way to the running site. It is very
important that we are able to answer the question "Who enabled
this permission, when and why?"

Why is that a killer feature of drupal, why do you assume you can't
put silverstripe's configuration under version control?
What makes you think silverstripe wouldn't have a change history for the

Drupal works very well to display change histories.  Lets look at how
Drupal handles a module / code project:
This is the homepage:

Take a look at the patch queue:[]=8&status[]=13&status[]=14

Take a look at the issue queue:

Oh yes, there are actually people working on the project, so there are
issues in the queue.  But they get fixed because people can find them and
start working on them easily by browsing the system and looking at the
modules home page.  Having the discussion board integrated with supporting
the module helps get community feedback for testing and bug reports and
feature requests.  This interaction promotes collaboration and ensuring that
the project is guided by the needs of the community.

Lets look at another function the groups:

This group is managed online and helps members coordinate activities for
training and promotes the project.

Lets look at the documentation for the API:

This is well organized and automatically generated by doxygen talking to
Drupal.  NOtice the example modules, so teaching how to develop is
integrated with the communities development site.

LEts look at documenation wiki functionality:

This is created by the community using Drupal as a wiki.

This is a whole new product built using Drupal:

Drupal is amazingly flexible and is really a workhorse for web application
development, it just happens to be a rocking good, fast, reliable CMS.  No,
it isn't a slick out of the box as Silverstripe, but it has a lot more to

3) How do you plan to implement translations? (from a visitor's point
of view, not technically). I mean, the current
site is in English only; you need to go to to
see content in German, but that one is a totally different site. On the
other hand, the Silverstripe demo (and of course Drupal too) seems to
support translation of the single pages: but is that what you want?

Well, this is a reiteration of what has been discussed already. No, it
is not *all* that we want. That's why I did put the subsites
requirement on the list.
But it is /part/ of what is wanted.

what I could see (pumbaa has been down for me for the last two hours)

Yes, the machine (the host) was rebooted and the VM that hosts
silverstripe wasn't restarted.


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

*Thought Farm Productions <>*
*(201) 691-7057*

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.