Sun Urged to Give Up OpenOffice Control
inc_x writes "Developers from OpenOffice.org are urging Sun to set the project free and bring it under a foundation. Sun's dominance over the project makes other companies such as IBM, Redhat and Novell reluctant to contribute more. Both Mozilla and Eclipse managed to attract an increasing number of developers after the projects were moved over to an independent foundation."
The next logical step - should have been done allready. I can't really se OO go very much further unless they go this way.
I for one.. Just kidding. I don't actually see why Sun would not agree with this. But on the other hand I'm thinking from the user aspect and not corporation aspect. More developers sounds good for me, usually more and better features. But putting OO under its own foundation probably means less money for Sun?
While it's probably possible to fork it, it wouldn't be a good idea imho, especially seeing that the bulk of OO developers are from Sun anyway. So I don't think a fork would achieve much and I don't think a fork is really merited in any way at this point.
This isn't about forking however, but about better organizing OO developement, in order to attract more external developers, which would of course be a very good thing and probably also benefit Sun.
Mozilla, for all the support it has, still hasn't achieved any of their goals. 4 years later it's still essentially NS code, and it's plagued by code nobody likes, and bugs both inherited and introduced.
With Sun at least you've got one company at the wheel so to speak.
Considering that over 80% of OpenOffice.org developers are employed by Sun (statistic provided by Novell), I wonder who, exactly, the developers asking for this are. I attended a talk by a Novell OpenOffice.org guy a while back, and his view was that the baroque build system was the biggest reason that new developers didn't get involved, and they had people working on simplifying that.
I am TheRaven on Soylent News
If Sun is interested in goodwill, then this seems a great way to go.
Open Office is possibly the single most important reason why Linux is useful as a workstation OS. Seems to me like they deserve all the goodwill anyway.
That's strange. We do hear that request from IBM.
But in fact I heard that most FLOSS developers are turned down by the size and overall (low) quality of OOo code.
As one developer said on blog (I failed to find that remark again) the thing is only paid Sun developers would work on it. And only because they are paid to do so. Compilation take ages and level of requirements for development is high - that all creates entry barrier to FLOSS developers, most of whome work in their own spare time.
To put in prospective: what would you want to spend you time on: hacking Linux kernel and then in 10 minutes seeing your changes or waiting N hours when OOo compilation finishes?
I never looked into OOo sources. But the pace of progress project makes - and the kind of progress it makes - tell quite much about how project is organized. I truly hope that KOffice would be able to run on Wind0ze - in office unfortunately I'm completely confined to the M$ Wind0ze. At the moment only OOo can read the SXW files OOo produces upon import from M$O... AbiWord fails completely to pick up styles in such documents. KOffice 1.4 is quite close to render the files the way as OOo does.
All hope abandon ye who enter here.
Mozilla has gotten new developers since Firefox, NOT because it's not controlled by AOL/Netscape anymore.
I wish developers would be less pretentious about their choice of projects. Surely successful projects
which have significant amounts of corporate backing, both financial and in terms of management, are some
of the better projects to work on. You have defined goals, a great infrastructure to work in, and nobody
ever complained about the way Mozilla was being run before The Foundation (in fact The Foundation works
exactly the same way for every developer in terms of bug tracking, IRC events, software testing and
releases, as it did during AOL's tenure)
OpenOffice could get more developers if it had some unsubstantial hype or managed to get a bunch of new
features it already had (get rid of Java and implement everything the same way, some other way
not just because Sun would have dropped it. I actually think OpenOffice (like Seamonkey becoming a tiny
little sideproject in view of Firefox's popularity) would suffer for it.
Eclipse has become the dominant IDE because it was set free, otherwise there would have been no other reason to use Eclipse 1.0 over NetBeans or what have you. Because it targets Java programmers you can bet that it definately benefited by this (I see a Java bug in the tool I do my Java coding, I fix it)...
I'm not sure Mozilla is not so open and shut, devs would have had different reasons for working on it which may have been related to past loyalty to the browser, hatered of IE, or just plain curiousity... But I'm not sure what the OSS developer counts were for the Netscape/AOL Mozilla vs. Mozilla.org Mozilla releases.
In my view OO.org biggest problem is not that SUN pays most engeneers but huge complexity of OO.org. I've heard even some rumors that OO.org contains ASSEMBLER language in some parts!!!
To make much more flexible whole project needs to become much more modular (which equals trash all existing codebase and start from scratch):
- file modules (input/output) - in ideal world OO.org would share this part with AbiWord, KOffice etc...
- "processing" module (document "managment", scripting etc.) - imagine running OO.org without GUI (some server document processing etc.)
- "GUI" module - native Qt, GTK, Windows, MacOS, etc..
But I'm 99% sure that this will not ever happen. More probable is that KOffice will become much more usable and supported on Windows/MacOS.
MS could of course turn to just rely on MSN and Xbox
Didn't the XBox related activities make a loss?
http://blog.nexusuk.org
Genuine question - did Mozilla and Eclipse gain developers because they were "set free", or is that just coincidence? (Remember - just because B followed A, doesn't mean that A caused B)
Genuine answer - Alot of developers have clauses in their employment contracts about what they can and cannot do in their spare time in terms of software develoment. In my own case (I had a lawyer check my contract) I can am free to work on OSS projects if they :
1) Do not undermine the business of my employer. That is the OSS project represents a competing product.
2) The project is not conntrolled by a competing company or corporation.
So I am guessing that it was at least partly a case of Mozilla and Eclipse gaining developers because they were 'set free'.
Some developers have truly draconian clauses in their contracts about the extent to which they can participate in OSS projects. I have even heard of people being forbidden by contract to develop software for anybody but their employer no matter what the circumstance or the nature of the development work (ie. even if it is an OSS project that is solely for their own enjoyment, unrelated to the employers line of business and not for profit). Such clauses would probably not hold up in court, at least not in most EU countries, but corporations include them in employment contracts anyway. The same goes for anti competition clauses, ie. "If you quit and start working for a rival corporation you must remain unemployed for N months before starting your new job". Supreme courts in a nubmer of European countries have have declared such anti competition clauses to be invalid but they keep being included in employment contracts regardless. I suppose employers are counting on their terror value since employees may be reluctant to take the matter to court even if they will win because of the legal cost and the time-demands and hassle of a court case.
Only to idiots, are orders laws.
-- Henning von Tresckow
OOo is at the same stage as Mozilla was: a functional but bloated and messy codebase and system. Unfortunately, that's what big companies tend to produce (I think it's a consequence of having too many engineers, many of which are mediocre).
What needs to happen to it is what happened to Firefox: the thing needs to be split up, the GUI and cross platform toolkit need to be overhauled (or even replaced with Gtk+), and Java needs to be exorcised from it.
And, yes, severing the connection with Sun would be a good thing for OOo, and ultimately for Sun as well.
It is not only OpenOffice, Linux kernel development also should bring under a foundation and set an example for the open source community. The "Linux" trademark also should bring it under that foundation.
I love OO.o, but I sometimes wonder if we would now have a significantly lighter, "cleaner" office suite had OO.o not dropped into the picture when it had.
You may be right, but, sadly, I don't think that users want a light clean suite - they want something that looks like MS Office.
On the other hand, if IBM, Red Hat et al are encouraged to commit manpower to the project by a loosening if licence restrictions, wouldn't that help in cleaning up the codebase?
That's couple of pretty big ifs, of course. Many open source projects, for good or bad, tend to focus on the addition of new features rather than just making the old ones work properly and cleanly, every time; so chances are, more manpower might well be used deployed on tasks other than cleaning and streamlining, despite OOo sorely needing a bit of both. Still, a guy can dream.
i am always buffled with the ignorance of the people who thinks Java is causing the problems with the OpenOffice project.
- Java is used in a small amount of the OpenOffice (database and some less known seperate components). i wish it would be used more. Especially in the GUI part, check NeoOffice if you want.
- Bloat is caused by the C++ side of the application. And not Sun's fault it was already rotten when Sun bought the company.
- Complexity is caused by the C++ side of the application. it would be hell if they tried to use C++ for all the database part.
- People thinks everybody will rush to participate code if it would e an organization are dreaming. if Sun does not pay, it will be in the hands of one or two stinky hacker. coding C++ code is no feast especially for this magnitude of the project. Firefox has a bunch of core developers and one million people who just rub the developers back, thay are suffering grately. Eclipse is lucky on that side because they use a better and easier programming language (Java).
"...they automatically forfeit the copyright. "
C'mon you know better than that.
They merely allowed other people to copy it under the terms of the licence. If the licence is breached then normal copyright applies. Similarly in the event that you had a line of code included in a project then you would be able to enforce the terms of licence for *your* line of code.
As to the rest, I might agree with your summary but I find the "how dare they compete with us" attitude of the middle bit a little silly.
Boring Old Fart (40, married, 3 kids...er no...make that 49, married, 3 grown up kids...it's been a long time)
A lot of the people here have high hopes for OpenOffice to be the killer app that could bring enterprise users to Linux. Hence the many suggestions and ideas about what Sun should do with it.
But to me, the key is not OpenOffice but OpenDocument. With the widespread adaptation of an open document format, in a few years people will stop caring what Office suite you are running - just like I don't care about your brand of email client, I just assume you can read the emails I send you.
For that reason, Suns ownership of OpenOffice has been all for the good - they could probably not have justified the expense to their shareholders if they had just given it all up to a foundation - and we should all be very grateful. Now we have ODF, we have a working implementation (OO.o), and all FOSS developers can choose to work on their Office software of choice, as long as they are ODF-compliant, which will in the end lead to real choice for all of us that are mostly users.
As for Sun keeping OpenOffice or giving it to a foundation - who cares?
It seems to me that there is a double agenda here. This is what I hate the most about the open source community. They think all software should be open, regardless of what the developer of the code actually wants. Mr. Torvalds (I applauded btw, when he stuck with GPL v2) can release the Linux kernel under what ever license he wants to, since he's the one who developed it. Likewise, OOo is Sun's baby, and they should be able to do with it what they want. Now, before you all think I'm a troll I like open source. I like the fact that I can go into the code and figure out how it works. I even run Linux as my main desktop OS at home, and I use it to run my home-built media center and firewall. However, it should be up to who ever owns the code...and in this case, it's Sun. This is a free society right?
Wow. They release the best office suite for Linux/Unix, not to mention the only truly cross-platform office suite, under the LGPL and it still isn't enough. No, they have to set up a foundation.
Come on.
The only reason for the Mozilla Foundation was because AOL/Netscape wanted to stop bleeding money into a project that was giving them nothing. Sure, it's been a good move for Mozilla projects, but Sun's ongoing commitment to OpenOffice/StarOffice just shows how strongly they believe in the project. If OpenOffice was languishing, then it might be time to ask them to step aside and establish a Foundation. This is clearly not the case. Moreover, OpenOffice's license is very cut and dried. You can easily fork the project (as has been done with Workplace and, to a lesser extent, with NeoOffice.) Heck, you can even fork it and setup a foundation. Good luck replacing those Sun engineers, though.
OpenOffice is hugely important to Linux, Unix and Open Source in general. For the most part, I think that Sun has been doing an outstanding job with the code. Why ask them to further distance themselves from the project now? It's not like they're doing it a disservice. (As was arguably the case with Netscape/Mozilla.)
And another thing, people taking potshots at OOo 2's use of Java in Base should realize that this was yet another significant contribution to the project from Sun. Base, even with it's faults, works very well. In fact, it has already allowed me to use MySQL/OOo in place of Access at work. Sure it uses Java, but this was done for legitimate reasons with an eye on compatibility. The proof of this being that Red Hat et al. were so quickly able to port Base to the gjc. I highly doubt that the relative ease of this task was a coincidence.
Really, that this has come up at all is a true shame. I fear that it shows that even if Sun were to open source Java, people would still find some way to complain. Sun certainly does some strange things, but their contributions to OpenOffice have been nothing short of fantastic. They should be commended for Giving Microsoft their first real competition in years.
If Sun releases control over the project, that will make it more likely that an independent project will split OO.o into a server and AJAX clients. And that another project will cluster the OO.o server. Then Web forms and GUIs can finally have the kinds of editing control we deserve in the 21st Century. Like automatic version control. Or anything that beats these slate-like TEXTAREAs.
--
make install -not war
I thought the goal was to get more companies to open source products?
Sun has spent a lot of money on this product, and now people are demanding that they give this up too? I don't get it. Wouldn't this discourage people from opening up their projects to OS?
You can already fork this and do your own thing right? There's no incentive for Sun to "give up" more control over this, unless they want to fire a bunch of developers Sun pays for to lower their costs.
- sigs are for wimps.
... from the IBM P.R. department with the title: "IBM urges Sun to give up OpenOffice control"
... more than half of the OpenOffice.org developers are Sun EMPLOYEES! So how could _OpenOffice.org_ want "Sun Microsystems to give up control over the OpenOffice productivity suite, and donate the intellectual property to an independent not-for-profit foundation" (quote from the article)? And what developer would consciously use a term like intellectual property in the first place?
The truth is that if a high enough percentage of the OpenOffice.org people wanted to break up with Sun nobody could stop them - they could just FORK. But wait
If you don't fail at least 90 percent of the time, you're not aiming high enough. (Alan Kay)
Much of the rapid development that was happening to bring KOffice along went quiet when OO.o was released, if I remember correctly.
Ahh... the famous KDE fallacy. Some nice screenshots and a bit of user interface code and a hype article on slashdot == finished app. It's been a common theme on slashdot for 5 years now.
Clue: KOffice slowed down because all the low-hanging fruit had been picked. It entered the phase of development in which all much of the fun easy pay-off stuff had already been done... and it moved in the phase that all software developers know about the "elbow-grease" phase, in which you must buckle down and get all the tough stuff done.