Le 2010-12-12 03:47, Stefan Weigel a écrit :
Hi Stefan:
Well:
<quote>
during our yesterday's call, the CMS decision was taken: it will be
Silverstripe as a starter, with plans to migrate to Drupal later on.
</quote>
To me, "plans to migrate to Drupal later on" does not necessarily
mean, that there actually will be a migration to Drupal.
Hmmm, I don't know how more implicit this would be.
And, the SCM minutes clearly read:
<quote>
suggestion is that the website team should do some more planning,
what we need regarding website, additional services, and see how
this can be achieved with drupal. We see the need of a more
sophisticated CMS in the future.
</quote>
Yes, this, when taken in context, was a comment on the Drupal team not being
as organised in the beginning. Most of the Drupal people were busy with
their employment commitments and had somehow been caught short in presenting
a sample CMS for the SC. However, the documentation was well presented. You
would have to read the whole thread to get a feel for it.
To me, this means, that there has to be further evaluation and an
that migrating to drupal depends on a future decision by the SC.
Pse, don´t get me wrong: I am *not* against Drupal. But we should
recognize, what has been decided yet and what not.
Stefan
Marc
--
Unsubscribe instructions: E-mail to website+help@libreoffice.org
List archive: http://www.libreoffice.org/lists/website/
*** 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.