On 16/12/11 23:34, Christian Lohmaier wrote:
Hi Olav,
On Fri, Dec 16, 2011 at 7:07 PM, Olav Dahlum <odahlum@gmail.com> wrote:
On 16/12/11 17:01, webmaster for Kracked Press Productions wrote:
On 12/16/2011 10:34 AM, Christian Lohmaier wrote:
[...]
SilverStripe is still a horrible and slow CMS, with next to no support for
anything, unless you hack it to death and have direct access to the
server it runs on.
Sorry for not having the slightest sympathy for you when you don't
bring proiblems you're experiencing to the list.
And people would have listened and made everything better?
Why it was chosen when so much spoke against it,
are just a mystery.
Because not much spoke or speaks against it. If you complain to
yourself only, and don't participate in the public discussion then it
is *YOUR OWN* fault, not the fault of others.
There have been *lengthy* discussions about choosing the CMS, there
have been *plenty* of opportunities to complain loud and clear.
Not much spoke against it… Everything spoke against it, it's even a
dedicated page on the wiki comparing it to the competition. I can't
be all over the place, I actually rely on other people to take sane
decisions in matters as these. The research was there, and it was
just ignored in favour of personal preferences/interest or whatever
happened.
I would certainly go for something like Drupal or
Joomla, which have a broad community, lot of international users,
an excellent selection of modules, available professional support,
and actually web managable.
This is a stupd message that has no fundamental value. Those
"arguments" have been provided en masse, without the people favoring
drupal being able to create a site that was only halfway usable during
more than three months.
Incompetence, they already knew the decision was taken, and thus no
point in doing it… It could be several reasons, but that didn't mean
it was impossible to achieve.
I might have to migrate the Norwegian LibreOffice site to a working
solution if this situation doesn't improve soon.
This is b*s. State what doesn't work, and it will be fixed.
Complaining to yourself won't help. Concrete problem descriptions and
you will be helped.
Ok, I want to display RSS feeds and Tweets on the frontpage… I don't
want to wait for ages to get my work saved or published, and I
certainly don't want my work to be destroyed during this process.
Either all other NL-projects are also complaining to themselves, or
they can work with the system.
No matter what it is: When you don't state your problems, your wishes,
then nothing will change, as simply as that.
ciao
Christian
This is the same half assed approach to usability a lot of FLOSS projects
struggle with. A lot of time is spent on talking about the things that have
to be done, how evil and bad certain companies are, hacking in places people
never will see or actually benefit from, and completely ignoring the fact
that most solutions are used by people, not hackers. And most users won't
speak up or have the technical skills to write bug reports etc.
I like the stories about the notorious IBM "Black Team", maybe we should
adopt the approach they had?
– Olav
--
Unsubscribe instructions: E-mail to website+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/website/
All messages sent to this list will be publicly archived and cannot be deleted
Context
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.