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

On 11/23/2010 05:05 AM, Graham Lauder wrote:
On Tuesday 23 November 2010 21:14:39 Charles-H. Schulz wrote:
Le Mon, 22 Nov 2010 18:04:27 -0800,

NoOp<>  a écrit :
On 11/22/2010 10:10 AM, Ian Lynch wrote:
Is the take over of Novell going to affect the document foundation?

Actually, isn't this sort of thing the reason TDF was created to
begin with?

Yes exactly. And I'm glad to have Michael, Thorsten and the Suse team
on board with us, hopefully for a very long time.



Amen to that

can you clarify what you mean by having " And I'm glad to have Michael, Thorsten and the Suse team
>> on board with us, hopefully for a very long time."

are these people that used to be employed by novell, have left and are now working with TDF?

Personally, off topic i know, I stopped any association with SUSE once they jumped in bed with M$ (no matter how, through what subsidiary/organization/movement/non-profit or contractual agreement). The Patent and copyright infringement discussions are going to get very interesting. I for one like to acknowledge all the comments made by trust worthy adversary in the open source world and understand why they say implementing any sort of mono functionalities or dependencies is a large risk for your project and open source in general.

Thanks for your time,
Nathan Heafner

Unsubscribe instructions: E-mail to
*** All posts to this list are publicly archived for eternity ***


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.