Language Selection

English French German Italian Portuguese Spanish

Should Google acquire Open Office?

Filed under
Google

I think there could be a lot of benefits to both parties if Open Office were to work along side the Google Docs team. Now I’m not talking about Google buying Open Office; instead I’m talking about Google hiring some programmers to work on the Open Office application and help integrate the two. I know this is going to cause some controversy, but just hear me out.

First off, if the project remained under a GPL license then Open Office would just be gaining more developers. Sure Google would also help steer Open Office. But Google is very good at working with other companies after merging. And I think Google does a very good job with its own software and their products just seem to work. And that’s what really matters.

Full Story.

Won't happen

First thing, the license is not GPL, it's LGPL.
In any case, nobody said google developers cannot contribute to openoffice. Any person on earth can contribute to openoffice. Google is already free to work on openoffice.
This in a bit ignorant from the author of the article (Digital Ninja) in my humble opinion.

re: Won't happen

If only he would write a "open letter" to Sergey, it might happen!

Sergey

Sergey said that Google would not be working on an office suite. That was almost 2 years ago.

re: Sergey

Yeah, that was sarcasm as I've posted before that "Open Letters" have as much chance at influencing corporate policy as does a "magic 8 ball" (as in none).

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

NHS open-source Spine 2 platform to go live next week

Last year, the NHS said open source would be a key feature of the new approach to healthcare IT. It hopes embracing open source will both cut the upfront costs of implementing new IT systems and take advantage of using the best brains from different areas of healthcare to develop collaborative solutions. Meyer said the Spine switchover team has “picked up the gauntlet around open-source software”. The HSCIC and BJSS have collaborated to build the core services of Spine 2, such as electronic prescriptions and care records, “in a series of iterative developments”. Read more

What the Linux Foundation Does for Linux

Jim Zemlin, the executive director of the Linux Foundation, talks about Linux a lot. During his keynote at the LinuxCon USA event here, Zemlin noted that it's often difficult for him to come up with new material for talking about the state of Linux at this point. Every year at LinuxCon, Zemlin delivers his State of Linux address, but this time he took a different approach. Zemlin detailed what he actually does and how the Linux Foundation works to advance the state of Linux. Fundamentally it's all about enabling the open source collaboration model for software development. "We are seeing a shift now where the majority of code in any product or service is going to be open source," Zemlin said. Zemlin added that open source is the new Pareto Principle for software development, where 80 percent of software code is open source. The nature of collaborative development itself has changed in recent years. For years the software collaboration was achieved mostly through standards organizations. Read more

Arch-based Linux distro KaOS 2014.08 is here with KDE 4.14.0

The Linux desktop community has reached a sad state. Ubuntu 14.04 was a disappointing release and Fedora is taking way too long between releases. Hell, OpenSUSE is an overall disaster. It is hard to recommend any Linux-based operating system beyond Mint. Even the popular KDE plasma environment and its associated programs are in a transition phase, moving from 4.x to 5.x. As exciting as KDE 5 may be, it is still not ready for prime-time; it is recommended to stay with 4 for now. Read more

diff -u: What's New in Kernel Development

One problem with Linux has been its implementation of system calls. As Andy Lutomirski pointed out recently, it's very messy. Even identifying which system calls were implemented for which architectures, he said, was very difficult, as was identifying the mapping between a call's name and its number, and mapping between call argument registers and system call arguments. Some user programs like strace and glibc needed to know this sort of information, but their way of gathering it together—although well accomplished—was very messy too. Read more