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

Le 2010-10-20 16:17, Andreas Mantke a écrit :
Hi all,

sorry because i jump in the thread here, but i hadvenot the time to read every of the
- felt - two thausend posts about this topic on the list. I think, we are lost in a
nice discussion about features and posibilities of CMS. That should in my opinion not
the focus of our discussion. We had to find out, which CMS supports the basical
needs, is user (editor) friendly and could be configured and run at the end of the
week (I would suggest Friday.).

But that's not all. We need one or better two or more voluteers, who commit
themselves to work as admins on that CMS and do the "dirty work" in the background.

If we are going with silverstripe, i hope we have at least one volunteer ;-)

I don't know yet, if there is someone, who does the same for Drupal. I'm interested
to see, who of the writer in this thread is willing to do the dirty work for which


Hi Andreas:

Yes, we are trying to work through this methodically. People who are ready to commit their time has been discussed but will come up again sometime today or tomorrow. There is another sub-thread keeping tabs of our progress. I will be updating the information soon.


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.