On Wed, Jan 19, 2011 at 7:16 AM, Michael Wheatland
On Tue, Jan 18, 2011 at 11:38 PM, David Nelson <firstname.lastname@example.org> wrote:
I totally agree. The only reason people are (were) working on Drupal
was that Christian stated that people were already organised to
implement Silverstripe very quickly, which turned out to be not
You still don't get it. And you're completely turning the facts.
Silverstripe /was/ ready from the very beginning.
Once we realised that Christian's team was non-existant we offered to
help but were turned down:
There was no need to work on silverstripe, as silverstripe was working
from the very beginning. What was lacking were people willing to work
on the content and on the theme.
Yeah, and when you react two months after people were asking for help,
then it's too late. in this concrete situation, help was not turned
down either, but it was:
This is a very different message than you were sending the website
team last week. I respect the work you have put into the Silverstripe
site after Christian dropped the ball,
Stop this FUD!
There was no work put into silverstripe. David did a great job with
providing content and later with Ivan and Nikash on the theme as well,
but this has nothing to do with silverstripe maintainance.
Unsubscribe instructions: E-mail to email@example.com
List archive: http://listarchives.libreoffice.org/www/website/
*** All posts to this list are publicly archived for eternity ***
- RE: [tdf-discuss] [libreoffice-website] [Forum] How will the forum be organized? (continued)
Impressum (Legal Info)
: 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