On Tue, Dec 7, 2010 at 4:18 AM, David Nelson <firstname.lastname@example.org> wrote:
One thing I do on my own sites is to put a link in the page bottom
"Powered by Open Source software". That link goes to a page containing
a list of some of the software used on the server: the Linux distrib
used, Apache, PHP, MySQL, the CMS I'm using, and various other stuff
that people use continually and practically never mention. IMHO, the
very least courtesy is to put a link to the SilverStripe project, for
I'd rather not do that, since it is already decided that silverstripe
is only used until drupal is deployed.
I would of course love to stick with silverstripe, but that's the plan...
So when now the LO site shows off silverstripe in big letters, and
only a few month later silverstripe is replaced by drupal, people
might jump to conclusions like "Silverstripe couldn't cope with the
load, wasn't powerful enough, thus it was replaced by drupal".
This surely is not the case, but this is what I fear will happen.
Not sure, see above.
Silverstripe is "credited" in the source of every page:
<meta name="generator" content="SilverStripe - http://silverstripe.org" />
Giving that the move to drupal is already decided, I fear that
crediting silverstripe might actually have a bad effect, not a
But if you can suggest a suitable wording that makes this perfectly
clear: Why not.
Unsubscribe instructions: E-mail to email@example.com
List archive: http://www.libreoffice.org/lists/website/
*** All posts to this list are publicly archived for eternity ***
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