Hi :)
I'm happy either way
Regards from
Tom :)
----- Original Message ----
From: Florian Effenberger <floeff@documentfoundation.org>
To: marketing@global.libreoffice.org
Sent: Mon, 13 June, 2011 13:09:47
Subject: Re: [libreoffice-marketing] inconsistent boilerplate
Hi,
Tom Davies wrote on 2011-06-13 00.33:
I think it's fine to have the slight differences there. In some contexts
we
need to show the continuity of the project and in other contexts we need to
show
that this is time for a fresh start.
well, I think the opposite. :-) I think we should have a consistent
boilerplate, pointing to the roots and past of TDF, but it should be consistent
amongst the pages.
Florian
-- Florian Effenberger <floeff@documentfoundation.org>
Steering Committee and Founding Member of The Document Foundation
Tel: +49 8341 99660880 | Mobile: +49 151 14424108
Skype: floeff | Twitter/Identi.ca: @floeff
-- Unsubscribe instructions: E-mail to marketing+help@global.libreoffice.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/marketing/
All messages sent to this list will be publicly archived and cannot be
deleted
--
Unsubscribe instructions: E-mail to marketing+help@global.libreoffice.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/marketing/
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.