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

Re: [steering-discuss] Fwd: Re: LibO Drupal site

On Thu, 2010-11-11 at 07:18 +1300, Graham Lauder wrote:
On Wednesday 10 Nov 2010 20:53:16 Sebastian Spaeth wrote:
Well - nothing against giving appropriate credit - but the question is
what does he think is appropriate?

This would be my first question and would have to be negotiated.  SUN/Oracle 
have a small banner at the bottom of each page on the OOo site and contribute 
over a hundred devs and all the infrastructure which is probably appropriate 
for them.

        Riight - and really, I personally don't want to go back to a
corporately branded world. Conference sponsorship is something different
of course.

        Fighting out how much of whose logo we put where, is just too silly & a
waste of time :-) if we get one, then we get many - since we want to
involve many companies. I would suggest that just a statement of support
on the documentfoundation web-site, mentioning their contribution would
be enough, at least for now.

        "We love LibreOffice" says JimBob, Director of Awesomeness at
Drupal-helpers Inc. "This is why we are investing so much in helping
make their website rock with our drupal skills"

        or whatever ;-)



--  <><, Pseudo Engineer, itinerant idiot

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.