Hi Charles,
Wow - this reply is horribly late; I was doing some unrelated search
and noticed this thread. If you want a reply - you need to CC me as well
as the list - and not follow the screwed-up Reply-To: mangling that
destroys community ;-) Sorry about that, but I can't regularly read
'marketing' (13k unread mails as of today).
Anyhow - that aside:
On Fri, 2009-06-12 at 14:45 +0200, Charles-H. Schulz wrote:
> Well, I don't see the GPL/ LGPL v3 in there, and that's a substantial
> difference concerning the legal uncertainties surrounding Mono.
Oh - Mono is a mix of licenses, for sure - but AFAIR & (as Ismael said)
the core JIT is LGPLv2 & class libraries X11. OTOH, the recent Community
Promise move from MS around .Net should substantially re-assure people
terrified of legal uncertainties. Marketing wise that's prolly not
terribly relevant for OO.o though.
> No, it's not. Because the news that the contributions from Novell
> under LGPL v3 are 100% news to me and to many around here
Why ? as I wrote:
On Tue, 2009-06-09 at 18:10 +0100, Michael Meeks wrote:
> Not at all. All our OO.o changes are available under the terms
> of the LGPLv3, and we would be more than pleased for Sun to accept
> them under the terms of the project license.
Which is the case. I don't think a reasonable person would confuse the
untouched whole of Mono (as used to write a plugin for OO.o) as a
'change' to OO.o :-) In the same way that someone would not demand a
LGPLv3 licensed copy of python, to include a LGPLv3 python script to
drive OO.o.
> I'm still expecting a 100% answer about the OOXML filter,
> because that's 100% on topic, and so far I only got 0% answer.
Sure - so if you are thinking of the (BSD licensed) CleverAge XSLT
converter - it is (IMHO) a technically lame solution to the document
conversion problem, and I wouldn't suggest we include it in OO.o :-) and
last I checked the Sun engineers agreed.
This is the reason you don't see any integration for this in OO.o, oh
and of course the CleverAge converter is a joint effort with various
other parties under the BSD - it would need to be included (if it was
worth including) under that license - as is eg. python.
So - to take a simpler / different example: if we want SVG import in
OO.o, that's easy, the work is done, and it is available under the
project license: LGPLv3.
HTH,
Michael.
--
michael.me...@novell.com <><, Pseudo Engineer, itinerant idiot
-
To unsubscribe, e-mail: dev-unsubscr...@marketing.openoffice.org
For additional commands, e-mail: dev-h...@marketing.openoffice.org
