Hi all, On 15.10.2010 13:13, Thorsten Behrens wrote:
> Christian Lippka wrote: >> Because the Novell go-oo people decided not to contribute theier >> gstreamer implementation to OOo and OOo respected that. Later Kai >> Ahrens was so brave and did another implementation of gstreamer for >> OOo. Due to health problems he didn't make it in time for OOo 3.3. He >> was just a few days of so Oracle decided to contribute it anyway in OOo >> 3.3 but two people from the comunity, one who is now Foundation Funding >> Member and the other is from Novell overuled this. Go figure... >> > Hi Christian, > > let me translate that: the gstreamer backend was not available under > SCA conditions, just under plain LGPLv2+ - like tons of other > libraries (including gstreamer itself FWIW) that OOo makes use of, > and Sun/Oracle had *zero* problems accepting. When I asked a colleague I was just reminded that SUN had this rule that it was fine to use open source code wiht a suitable license IF (and only if)! the OOo code did only link against that code. That is it was not ok to use patches without SCA that would be included into libraries provided by SUN. I think those rules were named 'SUN architectural guidelines' and one always needed to confirm to legal that we did abide to them when new dictionaries for the linguistic were to integrated with OOo. I don't know though if the above applies to the gstreamer issue or not. That is if the gstreamer implementation is/was done completely by using libraries only and without 'LGPLv2+ patching' SUN source code. Regards, Thomas --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
