Slashdot Mirror
The Uncertain Future of OpenOffice.org
eldavojohn writes "What's the biggest threat to the success of OpenOffice.org? Is it Microsoft Office? Is it the simple fact that Dell doesn't offer it with computers? Not according to some participants in the 'open' source project itself, they say the biggest problem with OO.o is the fact that Sun codes, owns & makes all key decisions for the project when it should be more community oriented. A professor who participates in the project itself said 'enough developers are frustrated by both the technical and the organizational infrastructure at OpenOffice.org' and cites this as 'a real problem that is weighing on the project.' Other members of the community agree like Michael Meeks who asked 'At what fraction of the community will Sun reconsider its demand for ownership of the entirety of OpenOffice.org?' Hopefully with IBM's entrance into OO.o participation we will see the product become more community controlled & accessible. Has anyone else experienced this when developing for OO.o or another 'open' source project? Is it a good idea to criticize a company when they've put so much effort into a project that is technically open source and completely free? Is Sun trying to control OO.o like Java? Do they have good reasons or evil underlying intentions?"
Exactly, except the fraction. Either the community owns it, or it doesn't... There's no 'partially community owned'. It doesn't REALLY matter, though, since the project is open source. If Sun gets stupid, fork time - 'Completely Amazing Office' has a nice ring to it. The fact that the initials CAO is pronounced 'cow' should not be taken into consideration. ;)
"If you make people think they're thinking, they'll love you; But if you really make them think, they'll hate you." - DM
The question becomes does the community want another diffuse, nobody really in charge project, or do you want a benevolent dictator ensuring focus and quality control? Sun should be commended for sticking with OO for so long, when they could have just dumped all responsibility and let it drift aimlessly. They obviously have an interest, because with a few other tweaks they sell (or give it away to proper channels) as StarOffice, so it's doubtful they'll want to let go too much. Unless the Linus of OfficeSuites steps forward, then I'd rather see Sun or IBM maintain final say, to keep it on track.
From reading the comments here for years, the biggest issue with contributing seems to be that the code is a behemoth, and takes time and skill to understand. This hasn't stopped the NeoOffice folks from getting it running on Macs, and Sun's continuing final say shouldn't stop anyone from adding some missing features (such as a decent reference manager, or spell and grammar checker).
the more accurate the calculations became, the more the concepts tended to vanish into thin air. R. S. Mulliken
You must be new here. On Slashdot, only Google's "black box" search engine (and related products) and Apple's proprietary OS and hardware are considered "good". All other products and companies (with some rare open source project exceptions) are considered bad and/or evil.
And the "greatest understatement of the year" award goes to.... *drum rolls*
As near as I can tell, OOO has two major problems. Once upon a time, StarOffice actually had it's own mini-desktop from which the major pieces of the app like Writer and documents could be started from. This desktop even had its own widget set called VCL. Sun wisely did away with the goofy Desktop UI but OOO's UI is still implemented in this widget set. Whenever OOO is ported to a new environment, the major sticking point is that a binding layer has to be created from VCL to a widget set in the environment. Being a C++ widget set with more or less conventional semantics, VCL mapped well to GTK2 and Windows so Linux and Windows are easy ports in that regard. It is a very poor impedance match to Cocoa on Objective C and still appears to be hosing a truly native Mac port to this day. The NeoOffice guys use Cocoa through Java which makes a thin shim programming wise but a pig memory and resource wise as they have to have Java active and resident in memory for their VCL -> Cocoa mapper.
The other problem is that OOO isn't well divided up internally. It was designed to load as a huge glop o' code back in the StarOffice days and still does. I once argued about this until I was blue in the face with a OOO developer on NewsForge. I could not get it through his head that I wasn't talking about splitting off Writer, Calc and so-forth into separate apps. I understood that OOO's "apps" are developed from an internal common set of objects (which also means an equivalent to MS' COM system is also loaded with the main app). I was talking about being smarter about which objects to load initially and then loading others on demand. This would get the startup time and usual memory usage down. It would also make it easier to use OOO as an API the way Office is used as an API.
Weird.... why is it then that other projects like AbiWord, KOffice and the various other open source office utilities haven't taken over the market?
The main problem is OpenOffice isn't 100% compatible with MS Office documents. I have tried using Openoffice as a replacement to MS Word and Excel several times. Each time I end up getting burned because some executive pencil pusher thinks my layout sucked and looked bad. So in my attempt to use OpenOffice, I end up looking like a moron.
SO sure, I can use openoffice for my own documents, and then open it in Word or excel and format it completely when giving it to others, but comon. I don't have enough hours in the day to use something just to "stick it to microsoft", because honestly, the company I work for already has site licenses for Office and all other microsoft products. So in reality my attempt to use Open Office won't ever "stick it to microsoft".
Funny you should say this, because to date, the only radial menu system I have ever encountered was an open source window manager. I would say that counts a massive step forward in UI design (I live for the day when radial menus are the norm, but like Dvorak keyboards, it probably won't happen).
Palm trees and 8
For most free software, it is the case that those who contribute most work to the project, also influence its direction the most.
The question was: has anyone else experienced the kind of frustration described by the OO.o coders, on another open-source project. And my answer is yes, I have had some experience with that.
I got involved in a minor way with a certain open-source project which shall remain nameless. A co-worker of mine, however, put a lot more into it. The "leader" of the project, who ran the SVN server and merged the code and the like, pretty much had full control over what was included into the project. The problem is, the guy was arrogant, spiteful, and himself a terrible coder.
My co-worker submitted a change to the core code that increased its speed in some cases by as much as 100 times. However, the "project leader" apparently did not like his own code being fiddled with. (He had written the module containing the inefficient code.) At first he rejected the code changes, saying that he "did not like the coding style". Then, he incorporated the code changes incorrectly, which broke a lot of other things. Then, when he finally merged the code correctly, he publicly derided it for causing errors, when in fact the errors were in completely different parts of the program and he knew that.. and which was later demonstrated, also publicly. Did he ever apologize? Hell no. He cut the contributor off from the project, and me as well when I spoke up about this.
In short, the guy was a real ass. I am glad he was not my boss at work or something. I would probably punch him in the nose and walk out. He was completely unsuited for "leading" a "team effort".
The same more or less holds true for Mozilla. Mozilla is not a money-making venture. Their sole purpose is to make Firefox, Thunderbird and Sunbird and related technologies available to the community. That's it. Nothing more, nothing less. What other agenda could they possibly have?
My blog
The valuable part of the old days is that the number of pointless comments (like this one) were small, and without even moderation you could spot the comment from the engineer who actually was working on the product or technology discussed. The comment would typically contain 4-10 corrections of the article and a discussion for the rationale of the thing and their direction in making it.
It was really the most efficient technology news discussion system around. 1 - Post woefully flawed tidbit on upcoming technology or product. 2 - Engineer/developer working on said thing posts intelligent, informative and interesting report on same. 3 - Everyone reads said comment.
A combination of factors has destroyed this. Slashdot no longer appeals to the types of people who actually build and design such systems; the comment system and field is much noisier due to popularity, trolls, and other miscellany; there is more corporate awareness about "blogs" posting key information about upcoming things without explicit corporate blessing is generally frowned upon.
-josh