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

Re: [steering-discuss] Fwd: Google Alert - libreoffice

From: Italo Vignoli <>
Sent: Tue, 14 June, 2011 13:15:05
Subject: Re: [steering-discuss] Fwd: Google Alert - libreoffice

On 6/14/11 9:21 AM, Charles-H. Schulz wrote:

This is indeed really good. Now, if IBM really throws in the code from Lotus
Symphony, we'll have to be prepared, as some journalists might change their
stance... Although probably not :-)

It would be nice to know what it might mean in practical terms... Throwing in 
the code might imply a huge dump of files which have little or no meaning at all 
(see what happened with OOo files from Oracle). In any case, we should be 
prepared to react, but I don't think that IBM will throw anything before all OOo 
code is there.

Italo Vignoli
mobile +39.348.5653829
VoIP +39.02.320621813
skype italovignoli

Hi :)
1 thing it definitely would mean is a lot more articles about us, or at least 
discussing LibreOffice and TDF.  

Do people here add comments to the bottom of these articles to help get the 
articles "bumped up" within whichever place publishes the article?  It's an 
excellent way of correcting the inevitable inaccuracies?  I try to take care not 
to be excessive but i'm sure a couple wouldn't hurt.
Regards from
Tom :)
Unsubscribe instructions: E-mail to
Posting guidelines + more:
List archive:
All messages sent 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.