Hi Dan, > The problem is actually a bit more complicated. OOo uses a dual-license > strategy, where the code is dual-licensed SISSL/LGPL. When you commit > code to the OOo CVS, you have to have signed the JCA (Joint Copyright > Agreement) in which you assign copyright of the code over to Sun for use > under the SISSL and LGPL licenses.
OK, that is clear. Thank you so much for the explanation. But why can't this be waived for the Mac? If you have GPL code in the tree, you wouldn't have to contribute back unless you actually use GPL code, right? This would at least isolate the problem to the Mac code.. > Patrick and Ed are (IMHO understandably) quite reluctant to re-license > the NeoOffice code, since that means that any company can take the code > and reuse it _without_ _contributing_ _back_. That is the main problem > here. Then the question is: Can the license holder waive the requirement for contributing back if he/she wants to? And does it require that all changes to an entire software package of which only a tiny bit uses GPL have to be contributed back? Or just changes to the parts the are under GPL? > I hope that clears up a few things. It certainly does, thank you. I'm just trying to find a way out of this dilemma by thinking as laterally as I can. Maybe I should have left this to a lawyer Best wishes, Oscar __________________________________________________________________ Switch to Netscape Internet Service. As low as $9.95 a month -- Sign up today at http://isp.netscape.com/register Netscape. Just the Net You Need. New! Netscape Toolbar for Internet Explorer Search from anywhere on the Web and block those annoying pop-ups. Download now at http://channels.netscape.com/ns/search/install.jsp --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
