Language Selection

English French German Italian Portuguese Spanish

Open Letter to Larry Ellison about OpenOffice.org

Filed under
OOo

Dear Mr. Ellison,

I'm sure there are many reasons for Oracle buying Sun. You might not be having meetings this week about OpenOffice.org. You might be having meetings next week about spinning it off into a foundation. But if you keep interest or control over OpenOffice.org, please consider the following.

You know how huge, and pervasive, the use of Microsoft Office is. You know the massive amounts of partner and corporate revenue that comes not just from selling the product but from associated services and add-on products. (The certification program alone generates a decent chunk of change.) So you know that getting a bigger market share for OpenOffice.org would be a nice benefit to Oracle.

On that note, let me make my laundry list for what I think is important for OpenOffice.org. My letter to Santa Claus, perhaps; my wish list for a win/win/win situation for Oracle, users, and of course me and other OpenOffice.org providers of products and services.

rest here




More in Tux Machines

Red Hat News

Development News: LLVM, New Releases, and GCC

PulseAudio 10 and Virtual GPU in Linux

  • PulseAudio 10 Coming Soon, Using Memfd Shared Memory By Default
    It's been a half year since the debut of PulseAudio 9.0 while the release of PulseAudio 10 is coming soon. PulseAudio 9.99.1 development release was tagged earlier this month, then usually after x.99.2 marks the official release, so it won't be much longer now before seeing PulseAudio 10.0 begin to appear in Linux distributions.
  • Experimenting With Virtual GPU Support On Linux 4.10 + Libvirt
    With the Linux 4.10 kernel having initial but limited Intel Graphics Virtualization Tech support, you can begin playing with the experimental virtual GPU support using the upstream kernel and libvirt.

Licensing FUD and Licensing Advice

  • On the Law and Your Open Source License [Ed: Black Duck is just a parasite selling proprietary software by bashing FOSS]
    "Looking back five or ten years, companies managing open source risk were squarely focused on license risk associated with complying with open source licenses," notes a report from Black Duck Software. Fast-forward to today, and the rules and processes surrounding open source licensing are more complex than ever.
  • Explaining the source code requirement in AGPLv3
    This condition was intended to apply mainly to what would now be considered SaaS deployments, although the reach of "interacting remotely through a computer network" should perhaps be read to cover situations going beyond conventional SaaS. The objective was to close a perceived loophole in the ordinary GPL in environments where users make use of functionality provided as a web service, but no distribution of the code providing the functionality occurs. Hence, Section 13 provides an additional source code disclosure requirement beyond the object code distribution triggered requirement contained in GPLv2 Section 3 and GPLv3 and AGPLv3 Section 6.