Lotus Symphony code for OpenOffice coming soon

Posted May 18, 2012 0:02 UTC (Fri) by ewan (guest, #5533)
In reply to: Lotus Symphony code for OpenOffice coming soon by ingwa
Parent article: Lotus Symphony code for OpenOffice coming soon

"IBM wants the Apache License"

OK, but why? If IBM wanted the Apache licence so they could keep going with proprietary Symphony, that would make sense. It doesn't matter whether I like it or not, it does makes sense. There's a clear argument there for why it would be in IBM's interest, if not anyone else's, to take the hit of having two separate forks of basically the same codebase.

But they're not keeping proprietary Symphony, they've just freed the lot. So, once again - what's the need to insist on an Apache licensed project?

Lotus Symphony code for OpenOffice coming soon

Posted May 18, 2012 0:25 UTC (Fri) by Trelane (subscriber, #56877) [Link]

> But they're not keeping proprietary Symphony, they've just freed the lot. So, once again - what's the need to insist on an Apache licensed project?

I think the answer at this point is perfectly clear. Rob's reluctance to even discuss the origins of the decision to go with Apache over other projects makes the intent even more explicit.

They release OOo under Apache so that proprietary forks can be made. Then they release Symphony under the Apache license so that proprietary forks of their proprietary application can be made. This is for one reason and one reason only.

Only a proprietary fork can contain a back door that can be used for spying on users. Who would want to read all Symphony ODT documents badly enough for super-secret meetings with IBM to start all these wheels a-turning?

I'll connect the dots for you:

Aliens. Want. To Read. Your. Email.