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?"
by Anonymous Coward
on Wednesday September 19 2007, @10:37AM (#20668317)
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?
If they are doing a bad job of managing it, then yes. Releasing it under an open source license is good, and they should be recognized for that. However, doing so doesn't automatically excuse other problems they may have.
This sounds like more Sun bashing rather than any real issues. Consider Linux. Only a few people have commit privs. Any forked version is pretty much guaranteed to die by the wayside due to the momentum of the parent. And if you have good ideas there's a reasonable chance that they may be copied by a more established kernel dev and checked in under their name. Look at Firefox, only a few people can participate. Both are arguably less open than OOo and yet we don't see anybody pissing on them.
This is similar to the situation wiht Mozilla when it was still owned by AOL and Netscape. All of the code has to be "owned" by SUN and that turns some people off, especially when SUN slows the direction of OO.org to further it's Java or StarOffice agenda rather than letting it go on it's own. I think people would like to see OpenOffice spun off to it's own organization like IBM did with ellipse or Netscape did with Mozilla. That way the community has "assurance" that the needs of the Open product are be
Interesting opinion, but not relevant to the issue. Linus controls the kernel. Mozilla controls firefox. They will go where the controlling body determines. At absolutely no time is Linus or Mozilla at the whim of the community. The directions of the products will absolutely be to the needs of the respective controlling body. It's no different than Sun telling their developers to work in the directions Sun needs them to work. If you don't like their direction, fork.
Linus controls the kernel. Mozilla controls firefox.
Yes.
At absolutely no time is Linus or Mozilla at the whim of the community. The directions of the products will absolutely be to the needs of the respective controlling body
Umm, partly true. Linus listens to the community, that's what the LKML is all about. Is he at the community's whim? No. Does he accept input from others and make decisions that will be of the most benefit to the community? Yes.
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
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.;)
Is it a good idea to lie to a company or not provide any (constructive) feedback on negative issues just because they're being nice? If nobody is honest with them then their product may start off well and then head south quickly due to the pandering masses.
Speaking as a Sun employee, and on behalf of many of my fellow employees: hear, hear! Sun has always had control issues. It's part of the corporate culture. People here criticize this every day, both constructively and otherwise. Why should the larger community be any different?
One suggestion: don't complain to other Slashdotters: not a lot they can do. And don't complain to me: I'm just a hardware tech writer. Take your complaints to the top [sun.com].
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.
Lets see... I must be doubly evil, since I'm running openSUSE both at home and the office... and don't have a single piece of apple gear.
Sun isn't perfect, and neither are Novell, but they've done some of the major heavy lifting, and we should try to sound bit more appreciative, because we're not perfect either.
Otherwise, we just end up sounding like a bunch of fickle myspace bloggers.
The open source "community" doesn't exactly have the best track record developing complex GUI intensive applications. There is Gimp which is OK but not great. Firefox isn't exactly doing much as far as UI goes. KDE and Gnome both have... issues... in particular the fact that there are two desktops in the first place fragmenting application development and massively duplicating effort.
There are times when its not exactly bad to have one entity, whether it be a company or an individual, who puts an end to the bickering, makes a decision, sets the direction, imperfect though it may be, and makes everyone pull in the same direction. Linus serves that role for the kernel, SUN does it for Open Office.
Debate is good, expressing different views is good, one entity with poor vision dictating direction is bad. But, a project with a hundred chiefs and no Indians, and design by committee is not a always a prescription for success.
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).
Yep and if these developers really don't like it why not work on Koffice? I am sure that some people are frustrated. I know as a user I am frustrated over some of OOs short comings. However I think it is a pretty dang good system so far.
For open source development, there's only one community that really matters when it comes to picking the direction for a project: The community of people who contribute code[1] to that project, or pay others to contribute code. If you are not contributing to the project, your opinions are worth nothing, and the project should care about you exactly as much as a company would care about people who aren't in their target audience. If you want a voice, write some code, or documentation, provide some artwork
This is a panic piece, trying to rile upfeelings, almost trolling. Relax guys, Sun hasnt shown the steps that is being worried about here. When it does, then let us begin discussing. Till then, it is useless speculation and little better than FUD.
I don't think it's even a panic piece. The "uncertain future" isn't whether it will be developed or not. It's just uncertain how much control Sun will maintain, and whether developers displeased with Sun will bother to make a fork.
Either way, OpenOffice will continue to exist, continue to be developed, and continue to be used.
What's the biggest threat to the success of OpenOffice.org?
That's easy; Microsoft suing Sun for violating patents for MS Office 'inventions'. You know it's coming.
As far as Sun's dominant position over OOo goes; as long as they keep performing I don't see the problem. New 2.x releases have been appearing every few months and each is a notable improvement. They're doing a good job and while they keep doing it they'll remain in control. Their latest release provides a platform for extensions; go develop your miracle feature and let Sun keep cranking on the core platform, as they have been.
You're not happy with the direction of the project?
Fork it. It's LGPL'd. Take the code, release it under your new project, and make improvements that "the community", whatever the heck that means to you, will approve of.
Sheesh, as a previous poster said, tough crowd. Sun can't do anything right in the eyes of slashdot smitties.
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).
by Anonymous Coward
on Wednesday September 19 2007, @10:43AM (#20668409)
Why all the Sun bashing? Opensolaris is open source. Java is almost fully open sourced now. OpenOffice is open source. What the hell is wrong with Sun wanting to maintain some influence over the projects they started?
You're damn right. Anyone who doesn't like it can go fork it themselves.
If you don't like the community around OO.o, fork it and make your own community. If you think the codebase is too unwieldy to fork, there are plenty of other open source office suites you can contribute to.
You raise a rather valid point. Linus himself will tell you his position in the kernel development is basically, will this patch go in, won't it. From my understanding of the whole situation, Sun's position is more involved than Linus even. They actually write a whole bunch of stuff themselves and decide to put it in, along with other stuff that other people write out. Maybe I'm misunderstanding, but it seems to me that Sun is doing more to further OS development than Linus.
That being said, watch as I get modded down massively.
...more proficient in programming than me explain why OOo uses its own inbuilt font rendering and toolkit? Aren't these things already provided by all modern guest OS's?
IANAPBPKEAITBD [I Am Not A Programmer But Probably Know Enough About It To Be Dangerous] but if cross-platform-ness is a big thing, would it not be easier to have a series of OS-independent libs in the background with native frontends in win32, GTK, Qt, etc? This would also make it easier to make the user interface more "friendly" by way of familiarity and not sticking out like a sore thumb? To my mind the problems users see with OOo, aside from some user unfriendliness in some sections such as mail merge, are that it's slow as hell to start up, even from warm, the GUI is sometimes unresponsive/laggy and it looks (superfically) different from most apps they're used to (apparently this is "allowed" for stupid flashy apps, but a big no-no for "serious" apps).
Chances are I'm barking up the wrong tree and my knowledge of OOo is hopelessly wrong, but for non-developers these things can be tricky to understand.
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.
If you can do a better job coding, owning, and making key decisions, then fork the project and demonstrate.
If you can't fork because you need Sun's expertise, then maybe you should admit that Sun deserves to participate on their own terms, just as you participate on yours.
For years I've been amazed at how people will whine and whine about the direction an Open Source project is taking, rather than just demonstrating that another direction is better. The people doing the work are exercising their freedom to do whatever they want however they want it done. If you don't like it, not only is nobody making you participate, but lots of people have invested lots of work in giving you the freedom to do it the way you want to, instead.
It worked for EGCS and X.org. But 99% of the time, it's just whiners whining that they don't have control. Power and control don't matter in Open Source; we all have equal power. You have the power to control your own version, and if that's truly holding the project that you're whining about back, then obviously once you unleash your new vision of project management yours will blow away the one you're whining about.
"If you can't fork because you need Sun's expertise, then maybe you should admit that Sun deserves to participate on their own terms, just as you participate on yours."
It is a logical fallacy to say that someone only has a valid complaint against someone if they can do it better.
"we all have equal power" No, we don't. It is perfectly valid for someone who can't code to complaing about a bug or the lack of a feature, or the fact that it is slow. Just like a automobile owner can complain if their breaks don't work. No one is going to say to them to shut up unless they are willing to build there own car.
Complaints can be valid all day long, but that doesn't necessarily make them helpful.
When you're managing a project, usually you have to make decisions that are going to piss some people off. Those people can whine about it forever or simply realize that the decision had to be made and shut up about it. If they feel a bad decision is THAT big a deal, then it's time to put up or shut up, and show everyone else how wrong they are. That's productive and helpful, complaining isn't.
I find OpenOffice to be really good software, and it's improving rapidly. I don't see the problem in the grand scheme of things.
Disclaimer: I am one of the founders of NeoOffice [neooffice.org].
I think there's already interesting proof that forks can provide a very viable alternative to the overhead of the OOo project. Although the reasons are many, one of the big problems I historically had as a Mac OOo engineer was trying to get patches approved by Sun engineering. It has proven to be more efficient to have engineering freedom, allowing us to implement things that might never be approved by Hamburg. Being independent also has allowed us to implement a binary patching system so our bug fixes can be delivered quickly and independently if any marketing driven release schedules. Being outside the politics has also allowed us to integrate other open source technologies into the application that are important to Mac users, such as VBA support as well as OpenXML import and export. Yes, OpenXML import and export could be integrated into OOo today but engineering politics and Sun's manipulation of the project to foment a document format war have kept this functionality out of OOo, doing nothing except harm users that need to seamlessly integrate with MS Office environments.
NeoOffice has been shipping a solid, native, GPL licensed Mac product for over 2 whole years. We have shown forking is successful. Dropping the politics of the OOo organization has made us more efficient and resulted in a better product that users appreciate. We have had a free software solution for Mac for years, and all OOo has done is exorcise all reference to us from their website. Perhaps it is just banishment for daring to do things differently and not helping to propogate the name of OOo (which Jonathan Schwartz has publicly said is Sun's second most valuable brand after Java). Seems a bit like Sun wants control to me. It will be interesting to see if Sun has the stones to snub IBM for its Lotus Symphony brand in the same fashion.
I just think OO.o lacks a focus. As other Slashdot members had said earlier, it seems to be over engineered and not thought out enough in a 'direction.' An engineer says "Java is a good idea to have" so they add Java... and bring other woes.
While I know some people may dislike the new Office 2007, after using it for a while now, I can say honestly that it's the best version yet. The usability and UI are greatly improved (once you get used to them). Open Office lacks the 'polish' that a Microsoft Office delivers. This isn't about document format wars folks -- it's about the sheer usability of one platform over another. You cannot invent a similar animal as a MS Office, and then go your own direction even if it's smarter. You have to adopt the platform, and make it your own. That's how Firefox has taken off so well. They came in as a web browser, same functions, and built upon it.
Open Office (and I haven't checked out the latest version) comes in and says that it's a replacement for MS Office... but it does things its own way. Some shortcut keys are similar, but a lot of stuff is different. It's usable for sure, especially for/. users, but for the average Joe who has used Office everywhere else, OO.o is a different animal. And it's uglier and slower.
Make it pretty, make it similar... then build upon it. Not before. Just my thought anyway... maybe Sun will take it to heart. I don't see any benefit or disadvantage to having more control in the community hands, because like they say.. too many cooks spoil the broth. And we will have a LOT of cooks all trying to make feature decisions, instead of a focused core of people that guide the direction of a project.
While I know some people may dislike the new Office 2007, after using it for a while now, I can say honestly that it's the best version yet. The usability and UI are greatly improved (once you get used to them). Open Office lacks the 'polish' that a Microsoft Office delivers. This isn't about document format wars folks -- it's about the sheer usability of one platform over another.
Not a popular position here, but I'm forced to agree.
I'm genuinely glad that there is an Open Office and people who work
While I greatly appreciate the work that is done on OOo, there does seem to be something wrong when it comes to getting bugs fixed. For example, cell notes became badly broken in oocalc 2.x because they no longer move when their cells are moved (e.g. by sorting). The bug [openoffice.org] (yes, I filed it and I am biased) has remained open for nearly two years, and the developers have classified it as an "enhancement" rather than a "defect" even though it worked fine in version 1.x and is apparently causing problems for quite a few people with no work-around. I don't mean to whine, but leaving such obvious and problematic bugs unfixed for so long isn't good for the project. I don't know if this happens because they are understaffed or if there is a problem with how things are being managed, but getting the OOo people to pay attention to bugs seems to be a problem.
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".
What I see with OpenOffice is that it is perpetually trying to be MS Office. It shouldn't try to be MS Office, with an always circa-5-years-ago. For OO to succeed, it needs to be better than MS Office. Make people want to use it instead of MS's offerings. This seems to be the case with a lot of open office software - they're pushed as alternatives that mostly do the job, but the "big" selling points are that they are free to the end user, mostly compatible with the competition, and use open formats. Look at what Firefox did - they didn't try and replicate an alternative to IE that was always chasing IE's features...they made a *better* browser.
If material cost were not an issue, now or ever, who would pick OO over MS Office? All OO is, and will be in the forseeable future, is the bastard wannabe kid brother of MS Unfortunately, Exchange is in the mix, too, because of the links between the office suite, email, and intranet. Where's the open source initiative to create a *better* solution than the MS Exchange environment? Everyone just focuses on Exchange compatibility, and as long as you do that, you're perpetually going to be playing catch up.
Really, they should start from the ground up, and create a whole new office app/email app/email backend. Whose goal is to be *better* than the competition instead of a cheap or free alternative. That is, if anyone really wants to try and supplant MS's share. Just my $.02.
I think IBM weighing in will make it easier (more developers) but I'd be sad to see the commercially-oriented development structure go away. I doubt IBM are planning that considering their focus is a Microsoft-competitive Lotus suite and not entirely freedom-oriented.
Taking some of the control from Sun, and having IBM give in some effort and direction will mean the product can only get better. Wresting control from them and doing a design-by-committee open-source movement might fundamentally destroy the package.
There are only very few projects which have been spawned from a commercial development and moved to a true open source, open development and open community design model and survived with a great product. One might say Firefox is one of them, but would it have even gotten there if Netscape/AOL hadn't been pushing their buttons to produce browsers? It's perfectly possible that, given the way most open source projects are run, we would still be running Mozilla 1.8 beta right now and Firefox would never have been spawned from it.
I guess, if you want to fork Open Office, you're free to. Go ahead, make Open Open Office and see how far you get. The best parts of it might be rolled into Lotus Suite and Star Office, or.. they might not.
Sun being in charge is not necessarily the problem; the problem is that they lack the competence and vision to bring the necessary changes to OOo and are making it hard to bring in external expertise to fix it. Lets face it, they're a hardware company that also does server software. They sell products to enterprises, not to people. They've never had to deal with end users and they are not very good at it.
The simple reality is that Sun historically has done a less than great job designing and implementing user interfaces for end users. It's true for netbeans; solaris; Java and indeed open office that each of these products has a very long history of quirky, non standard user interfaces that pale to competing products. In all these products progress has been made. Basically solaris now sports a nice Gnome desktop (but they took their time killing their old UI), netbeans is undergowing the zillionth lets "fix the UI" effort, Java did great on the serverside but so far failed to get people enthousiastic on the desktop side (JavaFX being the latest misguided/doomed effort).
The Open office UI looks out of place on any platform. Ugly icons; weird fonts; clumsy stuff like the cross references dialog or the poor excuse for a bibliography manager. Yes you can sort of do most office related stuff in it and for most people that is enough. Sun has been fighting the symptoms for years and they seem to be pretty proud of their work. The truth however is that the overall Sun UI experience is mediocre or adequate at best across their product line.
What open office needs is somebody like Blake Ross to kick out the old UI and do a proper one. Blake and friends rescued the quirky mozilla from the fate that OOo is now facing: being a second choice cheap product that people use for cost rather than quality.
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".
At the moment, Sun pays for 80% of the development work on OO.o, Novell for about 15%, and a few other contributors do the rest. If you fork it, you will immediately lose 80% of the developers, and may lose a lot from the remaining 20%, so I hope you're up for a lot of work.
Or do you mean you want the 'community' to control it, but not actually have to write any of the code?
In order... (Score:5, Funny)
Not continually improving both feature- and UI-wise, yes, no, around 3/5, yes, yes, probably, and both.
Now that we've cleared that up, anything else I can help with?
Re:In order... (Score:5, Funny)
Parent
Re:In order... (Score:5, Insightful)
If they are doing a bad job of managing it, then yes. Releasing it under an open source license is good, and they should be recognized for that. However, doing so doesn't automatically excuse other problems they may have.
Parent
Re:In order... (Score:5, Insightful)
Parent
Re: (Score:3, Informative)
Re: (Score:3, Informative)
Re: (Score:3, Interesting)
Linus controls the kernel. Mozilla controls firefox.
Yes.
At absolutely no time is Linus or Mozilla at the whim of the community. The directions of the products will absolutely be to the needs of the respective controlling body
Umm, partly true. Linus listens to the community, that's what the LKML is all about. Is he at the community's whim? No. Does he accept input from others and make decisions that will be of the most benefit to the community? Yes.
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
Re:In order... (Score:5, Interesting)
Parent
Re:In order... (Score:4, Funny)
That sounds like a commendation and not a criticism to me. . . .
Parent
Why not? (Score:5, Insightful)
Is it a good idea to lie to a company or not provide any (constructive) feedback on negative issues just because they're being nice? If nobody is honest with them then their product may start off well and then head south quickly due to the pandering masses.
Re:Why not? (Score:5, Informative)
One suggestion: don't complain to other Slashdotters: not a lot they can do. And don't complain to me: I'm just a hardware tech writer. Take your complaints to the top [sun.com].
Parent
Damned if you do... (Score:5, Insightful)
Sun gets bad press for developing free software...
Tough crowd.
You must be new here (only Apple,Google=good) (Score:4, Interesting)
Parent
Re: (Score:3, Insightful)
Lets see ... I must be doubly evil, since I'm running openSUSE both at home and the office ... and don't have a single piece of apple gear.
Sun isn't perfect, and neither are Novell, but they've done some of the major heavy lifting, and we should try to sound bit more appreciative, because we're not perfect either.
Otherwise, we just end up sounding like a bunch of fickle myspace bloggers.
Re:Damned if you do... (Score:5, Insightful)
There are times when its not exactly bad to have one entity, whether it be a company or an individual, who puts an end to the bickering, makes a decision, sets the direction, imperfect though it may be, and makes everyone pull in the same direction. Linus serves that role for the kernel, SUN does it for Open Office.
Debate is good, expressing different views is good, one entity with poor vision dictating direction is bad. But, a project with a hundred chiefs and no Indians, and design by committee is not a always a prescription for success.
Parent
Re:Damned if you do... (Score:5, Interesting)
And the "greatest understatement of the year" award goes to.... *drum rolls*
Parent
Re:Damned if you do... (Score:5, Insightful)
Some could successfully argue that Firefox contains a HUGE amount of UI work. The entire app is one large UI system.
Parent
Re:Damned if you do... (Score:5, Interesting)
Parent
Re: (Score:3, Interesting)
I am sure that some people are frustrated. I know as a user I am frustrated over some of OOs short comings.
However I think it is a pretty dang good system so far.
Re: (Score:3, Insightful)
Crying wolf.. (Score:5, Insightful)
Re: (Score:3, Insightful)
I don't think it's even a panic piece. The "uncertain future" isn't whether it will be developed or not. It's just uncertain how much control Sun will maintain, and whether developers displeased with Sun will bother to make a fork.
Either way, OpenOffice will continue to exist, continue to be developed, and continue to be used.
Biggest threat? (Score:5, Insightful)
As far as Sun's dominant position over OOo goes; as long as they keep performing I don't see the problem. New 2.x releases have been appearing every few months and each is a notable improvement. They're doing a good job and while they keep doing it they'll remain in control. Their latest release provides a platform for extensions; go develop your miracle feature and let Sun keep cranking on the core platform, as they have been.
Re:Biggest threat? (Score:4, Insightful)
When they do that, it'll just mean that OpenOffice.org is ready for primetime.
Parent
Re:Biggest threat? (Score:5, Insightful)
For real.
You're not happy with the direction of the project?
Fork it. It's LGPL'd. Take the code, release it under your new project, and make improvements that "the community", whatever the heck that means to you, will approve of.
Sheesh, as a previous poster said, tough crowd. Sun can't do anything right in the eyes of slashdot smitties.
~X
Parent
Ergocracy (Score:4, Interesting)
Parent
Diffuse or Focused? (Score:5, Interesting)
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).
Sun Bashing (Score:5, Insightful)
Re:Sun Bashing (Score:5, Insightful)
If you don't like the community around OO.o, fork it and make your own community. If you think the codebase is too unwieldy to fork, there are plenty of other open source office suites you can contribute to.
Parent
Re: (Score:3, Insightful)
Re:Sun Bashing (Score:4, Informative)
That being said, watch as I get modded down massively.
Parent
Can anyone... (Score:3, Insightful)
IANAPBPKEAITBD [I Am Not A Programmer But Probably Know Enough About It To Be Dangerous] but if cross-platform-ness is a big thing, would it not be easier to have a series of OS-independent libs in the background with native frontends in win32, GTK, Qt, etc? This would also make it easier to make the user interface more "friendly" by way of familiarity and not sticking out like a sore thumb? To my mind the problems users see with OOo, aside from some user unfriendliness in some sections such as mail merge, are that it's slow as hell to start up, even from warm, the GUI is sometimes unresponsive/laggy and it looks (superfically) different from most apps they're used to (apparently this is "allowed" for stupid flashy apps, but a big no-no for "serious" apps).
Chances are I'm barking up the wrong tree and my knowledge of OOo is hopelessly wrong, but for non-developers these things can be tricky to understand.
Re:Can anyone... (Score:5, Interesting)
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.
Parent
Then fork (Score:5, Insightful)
If you can do a better job coding, owning, and making key decisions, then fork the project and demonstrate.
If you can't fork because you need Sun's expertise, then maybe you should admit that Sun deserves to participate on their own terms, just as you participate on yours.
For years I've been amazed at how people will whine and whine about the direction an Open Source project is taking, rather than just demonstrating that another direction is better. The people doing the work are exercising their freedom to do whatever they want however they want it done. If you don't like it, not only is nobody making you participate, but lots of people have invested lots of work in giving you the freedom to do it the way you want to, instead.
It worked for EGCS and X.org. But 99% of the time, it's just whiners whining that they don't have control. Power and control don't matter in Open Source; we all have equal power. You have the power to control your own version, and if that's truly holding the project that you're whining about back, then obviously once you unleash your new vision of project management yours will blow away the one you're whining about.
Re:Then fork (Score:5, Insightful)
It is a logical fallacy to say that someone only has a valid complaint against someone if they can do it better.
"we all have equal power"
No, we don't. It is perfectly valid for someone who can't code to complaing about a bug or the lack of a feature, or the fact that it is slow. Just like a automobile owner can complain if their breaks don't work. No one is going to say to them to shut up unless they are willing to build there own car.
Parent
Re:Then fork (Score:5, Insightful)
When you're managing a project, usually you have to make decisions that are going to piss some people off. Those people can whine about it forever or simply realize that the decision had to be made and shut up about it. If they feel a bad decision is THAT big a deal, then it's time to put up or shut up, and show everyone else how wrong they are. That's productive and helpful, complaining isn't.
I find OpenOffice to be really good software, and it's improving rapidly. I don't see the problem in the grand scheme of things.
Parent
Proof is in the pudding...and it's ready to eat (Score:5, Insightful)
Disclaimer: I am one of the founders of NeoOffice [neooffice.org].
I think there's already interesting proof that forks can provide a very viable alternative to the overhead of the OOo project. Although the reasons are many, one of the big problems I historically had as a Mac OOo engineer was trying to get patches approved by Sun engineering. It has proven to be more efficient to have engineering freedom, allowing us to implement things that might never be approved by Hamburg. Being independent also has allowed us to implement a binary patching system so our bug fixes can be delivered quickly and independently if any marketing driven release schedules. Being outside the politics has also allowed us to integrate other open source technologies into the application that are important to Mac users, such as VBA support as well as OpenXML import and export. Yes, OpenXML import and export could be integrated into OOo today but engineering politics and Sun's manipulation of the project to foment a document format war have kept this functionality out of OOo, doing nothing except harm users that need to seamlessly integrate with MS Office environments.
NeoOffice has been shipping a solid, native, GPL licensed Mac product for over 2 whole years. We have shown forking is successful. Dropping the politics of the OOo organization has made us more efficient and resulted in a better product that users appreciate. We have had a free software solution for Mac for years, and all OOo has done is exorcise all reference to us from their website. Perhaps it is just banishment for daring to do things differently and not helping to propogate the name of OOo (which Jonathan Schwartz has publicly said is Sun's second most valuable brand after Java). Seems a bit like Sun wants control to me. It will be interesting to see if Sun has the stones to snub IBM for its Lotus Symphony brand in the same fashion.
ed
Parent
Tell me about open source... (Score:4, Insightful)
I just think OO.o lacks a focus. As other Slashdot members had said earlier, it seems to be over engineered and not thought out enough in a 'direction.' An engineer says "Java is a good idea to have" so they add Java... and bring other woes.
While I know some people may dislike the new Office 2007, after using it for a while now, I can say honestly that it's the best version yet. The usability and UI are greatly improved (once you get used to them). Open Office lacks the 'polish' that a Microsoft Office delivers. This isn't about document format wars folks -- it's about the sheer usability of one platform over another. You cannot invent a similar animal as a MS Office, and then go your own direction even if it's smarter. You have to adopt the platform, and make it your own. That's how Firefox has taken off so well. They came in as a web browser, same functions, and built upon it.
Open Office (and I haven't checked out the latest version) comes in and says that it's a replacement for MS Office... but it does things its own way. Some shortcut keys are similar, but a lot of stuff is different. It's usable for sure, especially for
Make it pretty, make it similar... then build upon it. Not before. Just my thought anyway... maybe Sun will take it to heart. I don't see any benefit or disadvantage to having more control in the community hands, because like they say.. too many cooks spoil the broth. And we will have a LOT of cooks all trying to make feature decisions, instead of a focused core of people that guide the direction of a project.
Re: (Score:3, Insightful)
Not a popular position here, but I'm forced to agree.
I'm genuinely glad that there is an Open Office and people who work
LOTUS SMARTSUITE? (Score:3, Funny)
Something is wrong - bugs not fixed (Score:3, Interesting)
Sun is the biggest problem? (Score:5, Interesting)
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".
The problem is it needs to be better (Score:4, Insightful)
If material cost were not an issue, now or ever, who would pick OO over MS Office? All OO is, and will be in the forseeable future, is the bastard wannabe kid brother of MS Unfortunately, Exchange is in the mix, too, because of the links between the office suite, email, and intranet. Where's the open source initiative to create a *better* solution than the MS Exchange environment? Everyone just focuses on Exchange compatibility, and as long as you do that, you're perpetually going to be playing catch up.
Really, they should start from the ground up, and create a whole new office app/email app/email backend. Whose goal is to be *better* than the competition instead of a cheap or free alternative. That is, if anyone really wants to try and supplant MS's share. Just my $.02.
IBM good, but not for "community" (Score:3, Insightful)
Taking some of the control from Sun, and having IBM give in some effort and direction will mean the product can only get better. Wresting control from them and doing a design-by-committee open-source movement might fundamentally destroy the package.
There are only very few projects which have been spawned from a commercial development and moved to a true open source, open development and open community design model and survived with a great product. One might say Firefox is one of them, but would it have even gotten there if Netscape/AOL hadn't been pushing their buttons to produce browsers? It's perfectly possible that, given the way most open source projects are run, we would still be running Mozilla 1.8 beta right now and Firefox would never have been spawned from it.
I guess, if you want to fork Open Office, you're free to. Go ahead, make Open Open Office and see how far you get. The best parts of it might be rolled into Lotus Suite and Star Office, or.. they might not.
the problem is that sun lacks competence (Score:3, Interesting)
The simple reality is that Sun historically has done a less than great job designing and implementing user interfaces for end users. It's true for netbeans; solaris; Java and indeed open office that each of these products has a very long history of quirky, non standard user interfaces that pale to competing products. In all these products progress has been made. Basically solaris now sports a nice Gnome desktop (but they took their time killing their old UI), netbeans is undergowing the zillionth lets "fix the UI" effort, Java did great on the serverside but so far failed to get people enthousiastic on the desktop side (JavaFX being the latest misguided/doomed effort).
The Open office UI looks out of place on any platform. Ugly icons; weird fonts; clumsy stuff like the cross references dialog or the poor excuse for a bibliography manager. Yes you can sort of do most office related stuff in it and for most people that is enough. Sun has been fighting the symptoms for years and they seem to be pretty proud of their work. The truth however is that the overall Sun UI experience is mediocre or adequate at best across their product line.
What open office needs is somebody like Blake Ross to kick out the old UI and do a proper one. Blake and friends rescued the quirky mozilla from the fate that OOo is now facing: being a second choice cheap product that people use for cost rather than quality.
YES (Score:4, Interesting)
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".
naw (Score:4, Funny)
Parent
Re:Dont think so. (Score:5, Funny)
or OfficeWeasel?
Kind of has a ring to it ... sort of like calling Major Frank Burns (M*A*S*H) ferret-face.
Parent
Re:Dont think so. (Score:5, Funny)
OfficeSpace
I mean, lookit: the clueless would look and go "oooh, cool name - space to do my docs n' stuff!"
The rest of us will simply giggle when we get asked why the app suite insists on showing a red stapler on the splash screen.
Parent
Re:Dont think so. (Score:5, Insightful)
At the moment, Sun pays for 80% of the development work on OO.o, Novell for about 15%, and a few other contributors do the rest. If you fork it, you will immediately lose 80% of the developers, and may lose a lot from the remaining 20%, so I hope you're up for a lot of work.
Or do you mean you want the 'community' to control it, but not actually have to write any of the code?
Parent