Slashdot Mirror


ASF Lays Out Its Plan For OpenOffice.org

Thinkcloud writes "In an open letter, the Apache Software Foundation has made its plans for OpenOffice clear, including an Apache-branded OpenOffice suite targeted at developers coming next year." From The H: "The ASF says it does not want to force any vision on the ODF community noting that 'it is impossible to agree upon a single vision for all participants, Apache OpenOffice does not seek to define a single vision, nor does it seek to be the only player' in the large ODF ecosystem. Instead, it wishes to offer a neutral 'collaboration opportunity' and notes that its permissive licensing and development model are 'widely recognised as one of the best ways to ensure open standards, such as ODF, gain traction and adoption.'"

129 comments

  1. So how does this effect LibreOffice? by Anonymous Coward · · Score: 0

    Given the mass move to Libre-Office - what's the politics going on here?

    1. Re:So how does this effect LibreOffice? by Pi1grim · · Score: 5, Interesting

      The politics is to provide OpenOffice under more permissive license, as for some businesses this might be a deal-breaker, thus getting more traction for the ODF format. So people will have choice between Apache licensed OpenOffice, or GPLv3 licensed LibreOffice, whichever they go with — it's still compatible.

    2. Re:So how does this effect LibreOffice? by Kjella · · Score: 5, Interesting

      My guess it that Apache just got this from Oracle and they wouldn't want to piss them off by just handing it on to LibreOffice, since clearly Oracle didn't get along with those guys. So they'll make their Apache version, keep the lights on and the project running and then one of them is going to fade away and eventually all that's useful will be merged into the other. I expect more of a xfree86 vs xorg situation here, once the split has already happened there's really not going to be much of a conflict, the developers will pretty soon gravitate towards the one that is best.

      --
      Live today, because you never know what tomorrow brings
    3. Re:So how does this effect LibreOffice? by Anonymous Coward · · Score: 0

      Given the mass move to Libre-Office - what's the politics going on here?

      Oracle have donated the OpenOffice.org trademark to Apache foundation in the hopes of stimulating a little friendly all-out-warfare between GPL fans and Apache license fans. It should prove entertaining.

    4. Re:So how does this effect LibreOffice? by Anonymous Coward · · Score: 1

      Posting to remove accidental moderation

    5. Re:So how does this effect LibreOffice? by Grishnakh · · Score: 1, Insightful

      It'll probably be something like the all-out war between the Conch Republic and the USA a few decades ago.

    6. Re:So how does this effect LibreOffice? by ilguido · · Score: 1

      This GPL FUD of late is getting a bit annoying: why should an office suite released under the GPL be a deal-breaker for some businesses*? I recently bought some games from GOG and DotEmu and wonder what? During the installation there was an EULA for the closed source software and then the full text of the GPL: those games were in facts a bundle of a closed source installation/launcher program made by GOG/DotEmu, an open source GPL'ed application (DosBox or SCUMMvm) and the original closed source game. It seems that someone is not scared by the boogeyman Stallman. *if they want to just use the application or create some new templates (99.99% of them) they can do it without releasing anything; if they want to modify the program for internal use only, they can do it without releasing anything.

    7. Re:So how does this effect LibreOffice? by SteveFoerster · · Score: 1

      As I recall, the Conch Republic actually got what they wanted at the conclusion of that war.

      --
      Space game using normal deck of cards: http://BattleCards.org
    8. Re:So how does this effect LibreOffice? by Grishnakh · · Score: 1

      Which was to remain a part of the USA and get rid of the stupid customs checkpoints that were annoying tourists. Maybe a "war" between OOo and LO will just end up with OOo merged back into LO without a shot fired, although Oracle may have had other plans.

    9. Re:So how does this effect LibreOffice? by hairyfeet · · Score: 1, Informative

      Its not FUD when RMS himself says the goal of GPL is to destroy non free software and RMS makes it clear he WANTS GPL to be "viral" and cause businesses to be forced to open up their code, as his whole goal is to destroy non free software.

      So yes having a more permissive license is of the good, it means that companies that might need a document engine or spreadsheet engine can easily use OO.o as a base without worrying of running afoul of the GPL. Remember that like it or not RMS IS a militant, always has been, and with each version of GPL he tries his damnedest to close any and all possible loopholes that would allow a non free company to use it.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    10. Re:So how does this effect LibreOffice? by ilguido · · Score: 2

      RMS himself says the goal of GPL is to destroy non free software and RMS makes it clear he WANTS GPL to be "viral" and cause businesses to be forced to open up their code, as his whole goal is to destroy non free software.

      Maybe... however the post by RMS you linked says otherwise: "writing non-free software is not an ethically legitimate activity, so if people who do this run into trouble, that's good! All businesses based on non-free software ought to fail, and the sooner the better", which means that RMS thinks that non-free software is bound to fail and that's a good thing in his opinion. GPL or not.

      So yes having a more permissive license is of the good, it means that companies that might need a document engine or spreadsheet engine can easily use OO.o as a base without worrying of running afoul of the GPL. Remember that like it or not RMS IS a militant, always has been, and with each version of GPL he tries his damnedest to close any and all possible loopholes that would allow a non free company to use it.

      This is exactly the FUD I was talking about. If a company wants to use parts of a GPL program as a base for its own program without distributing the source code, it can. The GPL (version 1,2,3...) says that the aforementioned company has to distribute the source code alongside the compiled binaries, however if it does not distribute them to third parties, it is not bound to release the source code. Obviously if it intends to sell the program (in a way or the other), there's a price, like for everything I could add, and that price is the release of the source code.

      As for RMS willing to destroy non-free companies, I've got the impression that the feeling is reciprocal and that's not just because RMS is used to talking over the top, but because GNU and Linux (and not BSD) are a threat to the revenues of some companies. Even the mighty Apache web server owes a big part of its success to all those Linux servers.

    11. Re:So how does this effect LibreOffice? by shutdown+-p+now · · Score: 1

      Who cares what RMS wants? What matters is what the GPL says, not what RMS says.

    12. Re:So how does this effect LibreOffice? by hairyfeet · · Score: 0

      Sorry if that link wasn't clear enough of RMS' intent, maybe this one will be more clear. How about a quote "Using the ordinary GPL for a library gives free software developers an advantage over proprietary developers: a library that they can use, while proprietary developers cannot use it" RMS.

      Hell I can produce a couple dozen more easily if you'd like, it isn't like RMS is exactly shy on the subject. Again NOT FUD if the entire goal as stated by RMS is to block non free software which he has made perfectly clear time after time AFTER time is his goal and he IS the one writing the license you know.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    13. Re:So how does this effect LibreOffice? by Anonymous Coward · · Score: 0

      LibreOffice is not a library. It's an office suite.

    14. Re:So how does this effect LibreOffice? by WorBlux · · Score: 1

      It is FUD. The GPL (any version) does not require anyone to release code at any time. What it says it that your legal right to distribute to distribute software or code covered by the GPL is contingent on the provision or offer of provision of the source. It does not take away an authors copyright of the code they do write, and does not attempt to prevent a release of that code should it replace the GPL parts with parts that are BSD or written in-house. The only way you could categoricly prevent someone from using original code and program design that they have written is though software patents, which RMS additionally opposes.

      As to your second paragraph, it depends on what you mean by "the good". However merely referencing the same comment that you linked to it's not clear that Stallman would oppose adding a bright-line into the Open Document Formats, where merely saving code to the declared standard would not violate licences of existing implementations. Only if you implemented a new feature or extension would you need to release code or sufficient documentation for a programer to code such an extension onto existing implementations.

      I really think GPL + a bright-line (which is what the LGPL does) can be better that a simple BSD when trying to engineer a new standard that competes with an existing standard.

    15. Re:So how does this effect LibreOffice? by WorBlux · · Score: 1

      Lets take a similar statement of fact. "Using a proprietary licence for a library gives those specific proprietary developers an advantage over all other developers, a library they can use, while all other developers may not"

      Does it then follow that goal of any proprietary library is to block all other software?

      No indeed, your logic is faulty. The goal is to out-compete other software, to provide more features than the competition, to align the practical with the moral.

      Besides your objection would apply even more strongly to many proprietary project as they do no allow anyone the advantages of thier code. If we were to imagine RMS as the CEO or some corporation that controlled the copyrights for all of the GPL'd products his comments would seem perfectly mundane. Every proprietary developer competes in the same manner. The goal is to displace non-free software, which is categorically not the same as blocking it's use.

  2. they lie... by Anonymous Coward · · Score: 0

    about their lies! LibreOffice!

    1. Re:they lie... by Chrisq · · Score: 1

      they lie...

      about their lies! LibreOffice!

      Does that mean they tell the truth

  3. Why don't they just kill it? by hedwards · · Score: 3, Interesting

    At this point is there really any reason why we need OpenOffice? Libreoffice, stupid name aside, seems to do everything that people want and more or less all the developers jumped ship for it a long time ago.

    1. Re:Why don't they just kill it? by almostinsane · · Score: 0

      They should shut it down and return the money to shareholders.

    2. Re:Why don't they just kill it? by sakdoctor · · Score: 2

      There's nothing wrong with the name Libreoffice. OpenOffice dot org; now there's a ridiculous name.

    3. Re:Why don't they just kill it? by Anonymous Coward · · Score: 0

      Your mother and grand mother cannot pronounce Leebraoffice? I think you either underestimate them, or there are not smart enough to read, which makes them non-users anyway. I suspect the former.

    4. Re:Why don't they just kill it? by Anonymous Coward · · Score: 0

      That's *Freedom* Office to you, soldier.

    5. Re:Why don't they just kill it? by hedwards · · Score: 1

      I'm sure they can pronounce it, but because they opted not to use the much more clearly spelled Latin root one has to know how to pronounce it in order to pronounce it. Which creates all sorts of headaches when trying to get people clued in.

    6. Re:Why don't they just kill it? by Anrego · · Score: 1, Flamebait

      They are both stupid names!

      In addition to just sounding wrong, the word "Libre" is synonymous with the growingly more annoying RMS high horse crowd.. which has become more and more of a turnoff to many (there was an article the other day about how people are migrating away from GPL in general).

      OpenOffice was fine if you dropped the "dot org" part, which most people did.

    7. Re:Why don't they just kill it? by Anonymous Coward · · Score: 0

      Not to be too offensive (at least this time), but in most languages people are used to speak the ending of words; English, specially American, emphasizes too much the beginning and thus has problems with many words which have their endings muted.

      Suggestion: pronounce Liberoffice like (probably) the English do it... Liberoffice. Or, better yet, change the name of the suite. It's a good compromise, easier on US dudes and follows the latin root "Liber" (which in Spanish and French became "Libre").

      Or just say LO... it will be even easier for everyone, not only for your mom.

      Or simply lie and say it's Openoffice; if she notices the new name, say it's a version with, uh, better icons.

    8. Re:Why don't they just kill it? by Anonymous Coward · · Score: 0

      The funny thing is, I've seen at least three pronunciations, all of which were claimed, much like yours, to be "completely obvious and only an uncultured idiot wouldn't know right away"

    9. Re:Why don't they just kill it? by Grishnakh · · Score: 1, Interesting

      There's nothing wrong with the name "LibreOffice". Anyone who has an education knows that "Libre" comes from the Latin root for "free" (as in liberty), is a word meaning exactly that in several Romance languages, and so its meaning is pretty obvious: a free (as in liberty) office suite.

      It only sounds "stupid" to uneducated hicks.

    10. Re:Why don't they just kill it? by Grishnakh · · Score: 0

      The article about people migrating away from the GPL was false, because it was based on bad statistics (there's lies, damned lies, and statistics...). In fact, the movement of OOo to the Apache Foundation was one of the main reasons for the article: their bad statistics were based on how much "new" code was being "created" in GPL vs. permissive licenses. Well, their idea of "new" is Oracle gifting OOo to Apache.

      GPL fans can easily do the same: all they have to do is fork a bunch of giant GPL projects like the Linux kernel, then do absolutely nothing with those forks and abandon them. If they create 100 new forks of the kernel every month, that'll count (by the idiot article author's methodology) as a ridiculous amount of "new" GPL code, and then he'll have to write a new article about how people are migrating to the GPL in droves.

    11. Re:Why don't they just kill it? by Grishnakh · · Score: 0

      So your relatives have no education? Did they drop out of school in 8th grade?

    12. Re:Why don't they just kill it? by Anonymous Coward · · Score: 0

      All 8th graders I know can pronounce "Libre" perfectly. Also, when I was younger even drunks could pronounce it if ordering a rum coke with lime (Cubu Libre). His relatives must just be dumber than a sack of shit.

    13. Re:Why don't they just kill it? by Anonymous Coward · · Score: 0

      So your relatives have no education? Did they drop out of school in 8th grade?

      Where, pray tell, is Spanish, or French mandatory for all students the ninth grade? And, incidentally, is it the Spanish or the French pronunciation (they're different) which is correct?

    14. Re:Why don't they just kill it? by Anrego · · Score: 2, Interesting

      I actually didn't read the article, but when I saw the title, my gut said "yup".

      Maybe it's just the circle I hang with, but I've personally felt a shift away from the GPL over the last several years, with v3 being for many the stray that broke the back.

      I've largely attributed it to people my age who are now out in the work force and are running up against the restrictive elements of GPL when trying to bring open source into the work place. The realistic choice isn't creating a cool derived work and not releasing the code vs creating a cool derived work and releasing the code.. it's creating a cool derived work and releasing it under your own terms (which most non-fanatics would probbaly be happy with) vs not bothering at all. In my view GPL doesn't foster open source, it prevents it. And that's the vibe I get from those around me as well.

    15. Re:Why don't they just kill it? by Translation+Error · · Score: 1

      What, you can't pick up the phone? Are your arms broken? Mom and grandma would love to hear from you, even if you're just calling to say LibreOffice a few times.

      But more seriously, so what if people aren't sure how to pronounce the name without hearing it a few times? Will that stop them from using it? From typing its name in an email or search engine? How often did anyone really say OpenOffice besides those of us pushing its use? In my experience, when friends/family/coworkers needed help with OpenOffice the always asked about 'Office'/spreadsheets/'Excel'/documents/or however else they thought of it to themselves. I don't expect it to be any different with LibreOffice.

      --
      When someone says, "Any fool can see ..." they're usually exactly right.
    16. Re:Why don't they just kill it? by Grishnakh · · Score: 0

      It really doesn't matter whether you use the French or Spanish pronunciation AFAIC; just that you don't look at it funny and throw up your hands because you're a moron who doesn't know Latin roots.

      I don't know about your education, but I had plenty of exposure to Latin and Greek roots in (public) high school, in English class. And this was in the somewhat-backwards state of Tennessee.

    17. Re:Why don't they just kill it? by turbidostato · · Score: 1

      "is it the Spanish or the French pronunciation (they're different) which is correct?"

      The Spanish one since (AFAIK) RMS took the word from this language (in an intent of making clear the difference between free as in free beer vs free as in free speech).

    18. Re:Why don't they just kill it? by Grishnakh · · Score: 4, Insightful

      Your "vibe" means nothing. There's tons of highly-active open-source projects under the GPL that are doing just fine: Linux kernel, KDE, Gnome (crappy new dumbed-down UI notwithstanding), busybox, and countless smaller projects. If GPL "prevents" open source, then why is the Linux kernel the most successful open-source project in history, while the *BSD projects languish in obscurity?

      As for GPLv3, there's no requirement for anyone to use it, it's just an option. Lots of projects are sticking with v2, including the Linux kernel. In fact, I can't think of any big GPLv3 projects offhand. It's really quite irrelevant.

    19. Re:Why don't they just kill it? by tunapez · · Score: 2

      As in 'free speech' or freedom. While the software is also free 'as in beer', they apparently chose not to call it Gratis Office.

      --
      Imagination drew in bold strokes, instantly serving hopes and fears, while knowledge advanced by slow increments...
    20. Re:Why don't they just kill it? by Anonymous Coward · · Score: 0

      LibreOffice dropped the ball on revamping the GUI and so they dropped the ball on the most critical area of development. Apache's proposal is relevant because perhaps they will unfuckup the mentioned office suite and make it usable again!

    21. Re:Why don't they just kill it? by TemporalBeing · · Score: 1

      The name's not unimportant. My mom—and grandma—have heard of "that OpenOffice thing." They wouldn't know how to pronounce LibreOffice, much less know what it is. It might be worthwhile for the Apache Foundation to allow the Libre folks to use the OO name; but the Foundation apparently doesn't think so.

      LibreOffice should only be allowed to use it if they are part of OpenOffice itself or only distribute a non-modified version that uses that name. However, the LibreOffice folks tend to think of themselves as a gift from God bestowed upon the world from which all things OpenOffice shall continue with, and have no interest in really mending the issues caused by Oracle's lack of communication with the OOo community. (Seriously, read their mailing lists!)

      And FYI - Apache has reached out to them at numerous points to try to get them to join in; only to receive a bitchfest about Oracle or IBM in return.

      So yeah, I would agree with Apache that they shouldn't be allowed to use the various OOo trademarks.

      --
      Truth is like the sun. You can shut it out for a time, but it ain't goin' away. - Elvis Presley (source: imdb.com)
    22. Re:Why don't they just kill it? by mcgrew · · Score: 0

      Libreoffice, stupid name aside, seems to do everything that people want and more or less all the developers jumped ship for it a long time ago.

      Calc needs some work. I was trying to think of an easy way to get all my music into a single playlist and came up with (on the Windows machine) dir /s > everything.m3u, then edit in a text editor. But there was way too much stuff in the file that needed to be deleted, so I thought "hmmm, I'll import it into a spreadsheet and I can simply delete columns.

      Calc won't import a text file. If you try to, it opens in the word processor. This is a HUGE drawback, and I really wish they'd fix it.

      I did get my m3u file -- just drop the music's root directory into the MP3 player. Lots easier than the spreadsheet method. But still, there's no reason why calc can't open a text file and have user-selectable cell/field delimiters. I do this at work all the time to get text data into an Access database, import to Excel, do a few operations that Access can't (although it should be able to) and paste into the Access table.

      I'm now going to have to stop evangelizing Open/Libre office, I guess, until they finish building the sucker. I wonder how Oo's database program is? I'll have to screw around with it a little.

    23. Re:Why don't they just kill it? by Bucky24 · · Score: 1

      that the correct pronunciation of "LibreOffice" doesn't match many native English speakers' expectations, unless they know in advance how it's supposed to be pronounced;

      I would expect it to be pronounced lee-bre. Is that wrong? (I haven't taken Spanish classes for almost 6 years)

      --
      All the world's a CPU, and all the men and women merely AI agents
    24. Re:Why don't they just kill it? by MattBD · · Score: 1

      I sometimes think it would do better if it had been named FreeOffice. OpenOffice was my induction into the world of FOSS when I didn't want to shell out for a copy of MS Office (I went on to discover Thunderbird and Firefox, before moving from Windows to Ubuntu), and for all we like to talk about the importance of free-as-in-free-speech, the free-as-in-free-beer angle is what gets a hell of a lot of people using FOSS in the first place, and the name FreeOffice would emphasise this.

    25. Re:Why don't they just kill it? by tibit · · Score: 3, Interesting

      I don't know how you did it, but I've been opening csv text files in Calc for many years. It works fine. You can select how to format the columns (numeric/text) and how are they separated (what character or where are the breaks in case of fixed format). It does exactly what you'd want it to do. How did you try to open that text file? Start up calc with a new spreadsheet, do Open, limit file types to Spreadsheet, click on your text file, and it'll pop up a text import dialog.

      --
      A successful API design takes a mixture of software design and pedagogy.
    26. Re:Why don't they just kill it? by lennier · · Score: 3, Insightful

      I would expect it to be pronounced lee-bre. Is that wrong?

      Quite possibly. But how do you pronounce "bre"? "Bree"? "Bray"? "Bruh"? "Bra"? "Ber"? In fact, how do you pronounce that "r"? Is it an English "r" or something closer to a rolled "lr"?

      All I know is I can't get my tongue in the right place to pronounce the French "bre" as I've heard other people pronounce it. It's no doubt doable with training, but both the vowel and consonant aren't native English and I never studied French in high school. So I end up calling it "Lee-bray Office" which I know is wrong, but seems better than saying "Libber Office".

      (I'm also trying to learn Chinese and am painfully aware of how hard it is to try to learn phonemes which are not-quite-like your native phoneme set; one naturally attempts to approximate with the closest native sound, which is probably exactly wrong but is the best a newbie can do.)

      "Libre" in a consumer product name also has awkward connotations of a popular female hygiene product called "Libra". Yes, I know that's silly, but it's there.

      End result is I avoid saying the product name whenever possible, and would prefer it was called something like "LibOffice" which has an unambiguous English letter-to-sound mapping. It's just a bad choice of words for an English-language product and could easily have been avoided. Not as offensive as "The Gimp", but still worse than "OpenOffice.org", which was also pretty bad.

      --
      You are not a brain: http://books.google.com/books?id=2oV61CeDx-YC
    27. Re:Why don't they just kill it? by Anonymous Coward · · Score: 0

      Samba, and it's quite relevant, but you can make the point that it was GPLv2 up until a few years ago.

    28. Re:Why don't they just kill it? by lennier · · Score: 1

      Rereading the original poster it now strikes me that for an American speaker, "libre" could be Spanish, not French as I initially assumed. So as a non-American English speaker, now I have two incompatible non-English pronounciations with two incompatible phoneme sets to pick from. Great.

      --
      You are not a brain: http://books.google.com/books?id=2oV61CeDx-YC
    29. Re:Why don't they just kill it? by gral · · Score: 3, Informative

      If you go into Calc, and File->Open->Text CSV, it should import all in one column. Then you can export without the " character seperator, and it should give what you are looking for.

      --
      Scott Carr
    30. Re:Why don't they just kill it? by Anonymous Coward · · Score: 2, Informative

      A Frenchman will actually pronounce it Libroffice, and bro exists in English (brother)

    31. Re:Why don't they just kill it? by hairyfeet · · Score: 0

      That is what I don't get, is there like a rule that FOSS projects HAVE to have shitty names? We should probably have a little contest called "list every horrible FOSS project name" just to see how long it'll get, probably several pages if you use single spacing.

      What would have been wrong with simply calling it "Freedom Office"? Or doing something about its speed issues so you could call it Speedy Office or Zippy Office? Hell there has to be a thousand names they could have used that would have been better than Liber which is how I here it mostly pronounced, just as everyone I talk to seem to call it LIEnux as in Linus.

      C'mon FOSS guys, I know you probably think you're being cute with these names but it really just hurts getting people to use your product. Now I just call it "A different version of Open Office" rather than deal with the pronunciation of Libre. Sure with as many FOSS guys that are out there somebody could come up with a better name, maybe a contest?

      --
      ACs don't waste your time replying, your posts are never seen by me.
    32. Re:Why don't they just kill it? by Anonymous Coward · · Score: 0

      Dude.

      There are plenty of FOSS programs with excellent names and plenty of proprietary software with shitty names.

      Oh, and "Freedom Office"? "Zippy Office"? Meeeeeeh...

      But to be fair, "Speedy Office" appeals to me for some reason.

    33. Re:Why don't they just kill it? by Anonymous Coward · · Score: 0

      Quit being part of the occupy problem, waiting for a handout, and get on with your life.

      That's it! now we know the reason for this rotten economy. Its those OWS protestors. If they would only get to work and spend more money to support the big corporations our problems would be solved. Now where did I put my pepper spray.

    34. Re:Why don't they just kill it? by Grishnakh · · Score: 2

      For one thing, FOSS projects don't have marketing teams full of overpaid people with marketing degrees to go do studies and focus groups or whatever and find the best names they can.

      For another thing, lots of proprietary software (that do have access to said marketing teams) also have shitty product names. Just look at most of the names for Microsoft products; they're terrible. They have a few winners like Word, Excel, PowerPoint, and Exchange, but IIRC 2 of those were acquisitions from other companies, so they can't take credit for the names, and "Word" was really rather obvious. But most of their in-house-named products have had absolutely horrible names; with absolutely no imagination or flair to them whatsoever, or if they do, they just come off as lame. SQL Server? (no imagination) Microsoft Windows Vista Home Ultimate Edition? (no imagination and way too many add-on terms) BizTalk Server? (very lame) Zune? (weird and lame)

      Or how about Apple and all their iCrap? People make fun of the KDE project and all its K-names, but somehow Apple gets a pass on this. It was OK for a while, with iMac, iPod, etc., but it's just gotten ridiculous and tired lately with an 'i' in front of everything.

      Thirdly, FOSS software has a big disadvantage in that it's almost always playing catch-up to some proprietary product that got there first, and took the best name. Just look at Word; I'm not sure why other word processors like WordStar and WordPerfect didn't use that name first (probably because it was a little too obvious and short and not catchy), but when MS got it, FOSS projects had to go find other names that weren't too close for fear of being sued, so we have StarWriter, oo-writer, lo-writer, etc. When someone invented PowerPoint (and then MS bought it, keeping the clever name), anyone copying that product had to come up with something different. SO/OO/LO actually did OK here, calling their version "Impress". Anyone making a photo editing program can't pick a name too close to "Photoshop", or they'll be sued too (though admittedly, "The GIMP" is pretty bad).

      Don't forget, there's plenty of FOSS programs that actually do have pretty good names. "Impress" as I mentioned earlier, "Amarok" music player, "Okular" PDF viewer, "Firefox" web browser, "subversion" revision control system, (looking through my application menu...) "Marble" globe program, "Celestia" space simulator, "Inkscape" vector graphics editor, "Pidgin" instant messenger, "Akregator" RSS feed reader, "Wireshark" network analyzer (formerly "Ethereal", also a good name), "Audacity" sound editor, "Kontact" personal information manager. Of course, I could also name off a bunch of FOSS programs with lame or shitty names, but as I pointed out before, the commercial world is really no different here; for every good name, there's a shitty one.

    35. Re:Why don't they just kill it? by dudpixel · · Score: 1

      To paraphrase, you feel that the copyright owner should _not_ get a say in what you do with _their_ code?

      If you didn't write it, why do you feel entitled to distribute it under your own terms?

      (btw, you can do what you like with GPL code, as the restrictions only apply when you want to distribute it, not simply use it).

      So I'm not following your argument. For code you write, you can choose whatever license you want. And for code other people write, they can do the same.

      If the copyright owner was really "happy with" you releasing their GPL'd code under your own terms, dont you think they would've used a different license?

      The mere fact that the GPL disallows this would contradict your argument. If someone licenses their work under the GPL, it is likely intentional, and that intention is to NOT allow any derivative works except on the GPL's terms.

      If you want to release something on your own terms, then either write your own code, or use code that is licensed under a more suitable (for you) license.

      At the end of the day if you do _really_ want to create a derivative work of a GPL'd project, but want to release it under your own terms, then contact the copyright owner(s) and ask for permission. They may be willing to license it to you under a different license, on a one-off basis. If they are not willing to do this, then your problem is still back to the fact you want to use code that someone else wrote, against their wishes. This would seem unethical to me.

      --
      This seemed like a reasonable sig at the time.
    36. Re:Why don't they just kill it? by ak47wong · · Score: 1

      Look at the very first line of this article. It tells you exactly how to pronounce it.

    37. Re:Why don't they just kill it? by Anonymous Coward · · Score: 0

      The realistic choice isn't creating a cool derived work and not releasing the code vs creating a cool derived work and releasing the code..

      Yes it is, those are the terms.

      it's creating a cool derived work and releasing it under your own terms (which most non-fanatics would probbaly be happy with) vs not bothering at all.

      Also known as Piracy. Taking a copyrighted work, ignoring the terms and making up your own release terms instead.

      In my view GPL doesn't foster open source, it prevents it.

      I find the doublethink here confusing as fuck, requiring open source to be open source is somehow preventing open source? WTF is that even supposed to mean? Having people use open source everywhere isn't the point behind the GPL, having all software be GPL, not contain GPL code or just not exist is.

      In short, suck it up. If you don't like the terms, write your own library from scratch, you don't get to pirate a GPL library just because you don't like the GPL.

    38. Re:Why don't they just kill it? by Anrego · · Score: 1

      I never said that at all...

      I fully respect peoples right to choose whatever license they want.

      I personally don't like GPL, and I'm glad others are coming around to more permissive licenses, but I didn't say anything against going against the wishes of people who do use the GPL or feeling that they shouldn't be allowed to use the GPL...

      I'd also note that I think many people choosing the GPL do so because it's the default go to license, or they are using a GPL'ed component in it (the viral nature of GPL also annoys me greatly).. and in a lot of cases don't even realize the restrictions and practical implications.

    39. Re:Why don't they just kill it? by Anrego · · Score: 1

      Also known as Piracy. Taking a copyrighted work, ignoring the terms and making up your own release terms instead.

      My point was that the software doesn't get developed at all due to GPL restrictions. I'm not advocating violating the terms an author has chosen... just that I'm happy more people are choosing more permissive licenses.

      having all software be GPL, not contain GPL code or just not exist is.

      In other words, that last one...

      Personally I write software to be used, not to further some fanatical view on how the world should work. If someone wants to take my work and make something useful to them with it .. great. They want to share it with others.. even better. Want to distribute the code, awesome! Even if there are restrictions on it.. at least people can compile the damn thing and make it work right on their platforms. Wanna sell it and not give back, what the hell do I care.. the code I wrote is still around...

    40. Re:Why don't they just kill it? by Anonymous Coward · · Score: 0

      It only sounds "stupid" to uneducated hicks.

      Well, you want it to be used in the USA, right?

    41. Re:Why don't they just kill it? by xtracto · · Score: 1

      while the *BSD projects languish in obscurity?

      Hello, you are full of shit

      --
      Ubuntu is an African word meaning 'I can't configure Debian'
    42. Re:Why don't they just kill it? by Anonymous Coward · · Score: 0

      Where, pray tell, is Spanish, or French mandatory for all students the ninth grade?

      No, but having heard of the drink that is called Cuba Libre is mandatory for 9th graders.

    43. Re:Why don't they just kill it? by Grishnakh · · Score: 1

      Hmm.... you have a point there.

    44. Re:Why don't they just kill it? by Grishnakh · · Score: 1

      You have a link here with a bunch of Linux applications that happen to have the BSD license. What exactly is your point? My point before was that the Linux kernel, which is under the GPLv2 license, is wildly popular, while the BSD kernels languish in obscurity, which is true.

    45. Re:Why don't they just kill it? by dudpixel · · Score: 1

      I can only speak for myself but if I were to choose the GPL (and I haven't yet) for any of my projects, it would be intentional.

      My default go to license is the BSD license...but I do have to say "each to their own".

      If you really believe people only use the GPL as a default choice, then why not take up my suggestion and contact the copyright holders of whatever software you want to distribute a derivative of?...unless of course its the linux kernel and there are hundreds or even thousands of copyright holders...?

      but for small projects I dont see too many developers objecting to another well-meaning and talented developer wanting to utilise their code.

      --
      This seemed like a reasonable sig at the time.
    46. Re:Why don't they just kill it? by hairyfeet · · Score: 1

      First of all there is no "Home ultimate" there is Home, there is Ultimate, but no Home Ultimate. And with MSFT OSes the standard convention is "Name Of OS/Name of version" so it would be Vista Home or Vista Ultimate. Funny thing is you screw yourself on support if you buy Ultimate as MSFT only gives 5 years for consumer OSes and 10 for Business so you'd be better off just getting pro and saving a hundred bucks.

      Now as for Apple? Its not iCrap its iShiny which hilariously the Macs spellchecker sees NO problem with which disturbed one of those Macbook owners when he typed it in and saw its true. As for why they get away with it Jobs thought of that and old Steve is looked upon as a mythical figure to Apple heads.

      And finally as to your list, Amarok is a shitty name (WTF is an Amarok? I bet if you asked a dozen people they'd have NO clue what that is), Firefox was a third choice they got stuck with when they were threatened with lawsuits first for Phoenix and then for Firebird, BTW their icon sucks as I've had people tell me it looks like a tadpole or a fetus, and I won't even mention the Gimp which always gets the "bring out the gimp!" jokes and sometimes even the whole spiel from Pulp Fiction.

      Frankly though in the end I think its not so much the names that screw FOSS and makes sure its always a teeny niche but the consistency. We can joke about the iShiny but everything in the iShiny follows pretty consistent rules, same as Windows programs follow Windows conventions. there really aren't any standards as far as UI with FOSS goes, its too many guys scratching itches and doing their own thing and none of it feels like its really meant to go together because...well its not.

      In the end I think the whole FOSS community needs to sit down and hash out some standards and stick to them. standards on which toolkit to use, which icon sets, make everything nice and consistent, so that frankly it won't matter WHAT anything is called it'll be "If you've learned one FOSS program you know them all" thanks to everyone following the standard. the LSB tried to get everyone on board but sadly the developers ignored them, maybe in 4 or 5 years someone else will try again and get it to stick.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    47. Re:Why don't they just kill it? by badkarmadayaccount · · Score: 1

      command line utils, anyone?

      --
      I know tobacco is bad for you, so I smoke weed with crack.
    48. Re:Why don't they just kill it? by WorBlux · · Score: 1

      Not just linux application, but vast parts of it's kernel are available under BSD licences. GEM, KMS, DRM and many of the drivers are availible under extremely permissive licences. The slower development of the BSD's is not I think due to the licence (as there are parts of the kernel that have quickly developed under that licence or similar ones) but that they are more closed in who they allow to contribute to the kernel and more cautious in what contributions they accept, and the fact that the development teams also do a great deal of work on user-space utilities. The best licence really depends on your intent for your code and the strategy you want to pursue for it's adoption.

    49. Re:Why don't they just kill it? by Grishnakh · · Score: 1

      And finally as to your list, Amarok is a shitty name (WTF is an Amarok? I bet if you asked a dozen people they'd have NO clue what that is),

      Don't be stupid. Amarok is the Inuktitut word for "wolf", and the project was named after the "Amarok" album by Mike Oldfield. That's why the logo is a wolf. Just because you're ignorant of something doesn't mean it's a bad name. Only in the minds of asshole Americans does everything need to be in American English.

      Firefox was a third choice they got stuck with

      Firefox is a cool word and the name of a Clint Eastwood movie about a Russian jet, and also refers to the Red Panda. Just because you and some other people don't like the logo doesn't mean it's a bad name, in fact the logo is irrelevant to the name.

      I won't even mention the Gimp

      I think I already said before that Gimp was a bad name. It was kinda funny back in the days when Linux was only used by Linux geeks, but now that they're trying to get more mainstream acceptance, and given the fact that Gimp is supposed to be a full-featured alternative to Photoshop (rather than, say, some very small and minor piece of software that few people use), it really should have a name with broader appeal and no bad associations. Given the aspirations its developers had even back in the "old days", they really should have thought of this back then too.

      but everything in the iShiny follows pretty consistent rules, same as Windows programs follow Windows conventions

      I totally disagree. Yes, Mac stuff generally is very consistent because of Steve and his insistence on that. But not in the Windows world, not by a long shot. Sure, all of MS's own software is consistent, but the third-party stuff is anything but. There's tons of third-party Windows stuff that's just as wacky in their UIs as some of the worst Linux stuff, sometimes much worse.

      In the end I think the whole FOSS community needs to sit down and hash out some standards and stick to them. standards on which toolkit to use, which icon sets, make everything nice and consistent,

      Not gonna happen, unfortunately. As I said before, lots of third-party software isn't even consistent. I don't think they even have standard toolkits there either, as MS has created a bunch of different, incompatible APIs (Win32, .NET, MFC, etc.) And as Macs gain in popularity, the situation over there is going to get worse as third-party software makers port their software to that platform in the fastest and cheapest way they can, without worrying much about following MacOS UI conventions because they'd rather their product look the same on all platforms.

      And with users ditching Gnome (and KDE before that) and moving to alternative DEs like LXDE and XFCE, things are getting even more fragmented in the Linux world. Who knows what's going to happen when Windows releases version 8 and starts pushing that with its crappy Metro interface; we'll probably have tons of people refusing to budge from Win7, and a bunch refusing to leave XP. The only way we'll get more consistency in Linux is if large numbers of users start converging on a single DE, making it the de facto standard (along with its toolkit), but things are going the opposite direction right now because the DE developers aren't listening to their userbase, they're trying to chase after "the next big thing" which they think is touchscreens.

    50. Re:Why don't they just kill it? by mcgrew · · Score: 1

      Command lines are fine for you and me, but 3/4ths of even slashdotters would be lost without a GUI, let alone normal people.

  4. LibreOffice? by Aladrin · · Score: 2

    Does anyone still use OpenOffice.org? I was sure it imploded when LibreOffice was formed to get out from under Oracle's thumb? Plus, it doesn't have to have the stupid .org tacked onto it's name to avoid trademark issues.

    If Apache is doing this right, they had better court the LibreOffice devs back into the fold.

    --
    "If you make people think they're thinking, they'll love you; But if you really make them think, they'll hate you." - DM
    1. Re:LibreOffice? by PybusJ · · Score: 2

      The tragedy is not that no-one is using OpenOffice, it's that millions of Windows and Mac users who downloaded it directly from the OOo website still are.

      The Linux users are fine, their distros will either transition them to LibreOffice or provide security patches to OpenOffice, but the vast majority of OOo users were not slashdot readers who follow the twists and turns of OpenSource politics, they're people who don't know that Oracle bought Sun (nor care about such details); they just downloaded a free office suite. They are not getting any security updates, even as vulnerabilities are fixed in LibreOffice. They are not even getting any good information that they're being given a vulnerable, unsupported product. The OpenOffice website still has all the same download links, and the same security information, including a Security Bulletin with no mention of vulnerabilities beyond 2010.

      I really think Apache and any ASF members should be ashamed. Whatever you think of having separate code-bases and a whole new incubator project, treating OOo users like this (especially when a maintained fork exists) is awful and detrimental to the standing of OSS in general.

  5. One Office to rule them all by Anonymous Coward · · Score: 0

    I really hope that ASF/OpenOffice and LibreOffice will join forces now. Now that Oracle is out of the picture, I would think and hope that the initial reason for creating LibreOffice is no longer valid.

  6. dumb question... by Zibodiz · · Score: 1

    I feel like I should know the answer to this, but what does Apache have to do with OOo? I thought Oracle owned OOo and ruled it with an iron fist.

    1. Re:dumb question... by OakDragon · · Score: 3, Interesting

      And what would Open Office that is "target at developers" look like, in contrast to plain ol' vanilla Open Office?

    2. Re:dumb question... by Anonymous Coward · · Score: 0

      they transferred all the rights to Apache sometime this year to get rid of the responsibility

    3. Re:dumb question... by Anonymous Coward · · Score: 0

      http://www.zdnet.com/blog/open-source/oracle-gives-openoffice-to-apache/9035

    4. Re:dumb question... by Crudely_Indecent · · Score: 1

      By no means should you read the first sentence of the second linked article in TFA.

      All the way back in June, we covered Oracle's announcement that it would move OpenOffice.org to a community-based project overseen by the Apache Software Foundation.

      I didn't know that either - or, at least I didn't remember that happening. Once I switched to LibreOffice, all of the OOo news just became irrelevant.

      --


      "Lame" - Galaxar
    5. Re:dumb question... by asdf7890 · · Score: 4, Insightful

      Oracle realised that they had no hope of the control they wanted (as all the devs left for LibreOffice) so they just gave in.

      Instead of just letting it stagnate and die, they handed it over to the Apache foundation so it could stagnate and die there without any need for Oracle to go to the hassle of ignoring support tickets.

    6. Re:dumb question... by narooze · · Score: 3, Funny

      And what would Open Office that is "target at developers" look like, in contrast to plain ol' vanilla Open Office?

      \LaTeX, of course.

    7. Re:dumb question... by Anonymous Coward · · Score: 0

      Oracle realized that spending money in many open-source projects basically made SUN go broke and decided not share the same fate.

      Common public doesn't get a grasp of how extensive the costs of maintaining a project like OpenOffice.org really was. LibreOffice doesn't currently match the size of the pre-forked Oracle Open Office.

    8. Re:dumb question... by Anonymous Coward · · Score: 0

      Your C++ code has newer looked so good printed. Also, your C code reaches new artistic high, with the tools available.

    9. Re:dumb question... by Anonymous Coward · · Score: 0

      Kind of like the Apache foundation took up Subversion, for which there is no actual use with git out in force?

  7. What they should do, by Capt.DrumkenBum · · Score: 2

    Let it die.
    http://www.libreoffice.org/
    Is fantastic.

    --
    If I were God, wouldn't I protect my churches from acts of me?
  8. grep Libre... by Hogmoru · · Score: 1

    ... yields no result in the open letter (TFA does mention it but only about old news).
    Even if they don't merge back, I feel they should still work together (or did I miss something ?)

  9. One (Open)Office to rule them all by Anonymous Coward · · Score: 0

    I really wish that ASF/OpenOffice and LibreOffice would join forces now. Now that Oracle is out of the picture, I would think and hope that the initial reason for creating LibreOffice is no longer valid.

    1. Re:One (Open)Office to rule them all by walterbyrd · · Score: 1

      I don't think this can happen because of incompatible licenses.

    2. Re:One (Open)Office to rule them all by datavirtue · · Score: 1

      LibreOffice is looking really good. They seem to have their shit together. Why break the momentum?

      --
      I object to power without constructive purpose. --Spock
    3. Re:One (Open)Office to rule them all by Dr_Barnowl · · Score: 5, Informative

      Apache Software License 2.0 is GPL3 compatible. Which doesn't actually matter ; LibreOffice and OOo are actually released under the same license - LGPL3

      The main license issue was that Sun / Oracle wouldn't accept patches without copyright attribution. This kept their options open - because they owned the copyrights of all the source, they could re-license it as they saw fit, including as a commercial product (StarOffice).

      Since then I am not aware of The Document Foundation demanding copyright attribution. There was basically no point doing so - the copyrights were still owned by Oracle, so it's not as if they could ever re-license the code as anything other than the license they acquired it under. The positive effect this has is that patches are easier to get into the code because contributors don't have to enter into a legal agreement with the foundation (which they may or may not be permitted to do, depending on their employment conditions, age, etc).

      Because the licenses continue to be LGPL3, LibreOffice can continue to merge patches from OOo at their leisure. Apache may only merge patches from LibreOffice if they have abandoned the practice of demanding copyright attribution (as of right now, the relevant page still demands that you sign the Oracle Contributor Agreement).

      So until Apache makes it very clear what their position on copyright attribution is, they remain the less Free of the two projects, and LibreOffice definitely has a purpose, and continues to have a technical advantage, despite being somewhat overshadowed by the brand capital that the OpenOffice.org name has accrued.

    4. Re:One (Open)Office to rule them all by Anonymous Coward · · Score: 0

      The Apache Foundation doesn't require "copyright attribution". And the Apache License is way more "Free" that the LGPL, as it has less restrictions, otherwise it wouldn't be GPL3 "compatible":
              http://www.apache.org/licenses/LICENSE-2.0.html

    5. Re:One (Open)Office to rule them all by orcmid · · Score: 1

      As someone else is mentioning, the Apache Contributor License Agreement is not a copyright transfer. It is a license only. Also, Oracle did not transfer the copyright on OO.o to the Apache Software Foundation - they licensed the OO.o code base to Apache in a way that allows Apache to release it and their derivatives under the Apache License.

      Also, at the ASF forking is a feature. There is no problem with forks, even of the Apache Licensed version, so long as in that case the Apache License and applicable trademarks are honored.

    6. Re:One (Open)Office to rule them all by orcmid · · Score: 1

      Oh, and the openoffice.org web site has not been moved under ASF custody yet. So a lot of material there is now obsolete, especially around licensing and code donations.

  10. It's now for derivating software by marcosdumay · · Score: 3, Interesting

    They could quite well turn it into a library, and let people write their software with it. They are publishing it with the APL, if you redistribute it you must fork (because of trademark issues), and most people did already migrate to forks.

    It is a nice way to make everybody colaborate on making ODF better, put everybody in sync, and make more ODF editors available. You can't do that with GPLed software. For once Oracle created something good. Too bad they had to try to screw everybody before they give up and do the right thing.

    1. Re:It's now for derivating software by Anonymous Coward · · Score: 0

      Oracle did not screw things up and try to tighten clutches on Open Office, a mentally retarded Executive in a corner office did.

      Blame the cancer not the patient.

    2. Re:It's now for derivating software by Anonymous Coward · · Score: 0

      They didn't "do the right thing." They waited until the project was about completely dead and a better alternative (LibreOffice, and fuck all of you ignorant asswipes who think the name of a program has any significance beyond your own preferences, by the way). Then they gave it to Apache, otherwise known as "where web projects go to die." Those people took how long to finally offer a solution to the relatively simple Slowloris attack? Long enough for their competitors like nginx and cherokee to go through several revisions.

      Apache is in essentially the same boat as XFree86 at this point. Some businesses depend on them and that's what keeps them afloat, but that's only because they haven't moved on to bigger and better things yet. They will eventually, and OpenOffice will be forgotten about.

    3. Re:It's now for derivating software by Anonymous Coward · · Score: 0

      Can't do what with GPLed soft? Fork? Re-use? Use? I call BS on you.

    4. Re:It's now for derivating software by TemporalBeing · · Score: 2

      They didn't "do the right thing." They waited until the project was about completely dead and a better alternative (LibreOffice, and fuck all of you ignorant asswipes who think the name of a program has any significance beyond your own preferences, by the way). Then they gave it to Apache, otherwise known as "where web projects go to die." Those people took how long to finally offer a solution to the relatively simple Slowloris attack? Long enough for their competitors like nginx and cherokee to go through several revisions.

      Please get your facts correct:

      • Oracle did not decide to wait for OOo to die. They simply stopped communicating as they don't understand the Open Source communities.
      • Oracle waited too long to communicate before doing anything. Probably as they were trying to understand what they had just bought; and figuring out how it fit into the organization.
      • a small group (3 people) decided they didn't want to wait for Oracle any more, forked the project, and have since sown a lot of discontinuity between the communities, having only had a small portion of the community join them, but acting like the entire community followed - which is not the case.
      • In light of the fork, and the discontinuity sown, Oracle decided to divest themselves of it, and returned it over to Apache as there was nothing they could do to "fix" the issue. So they simply followed plans already in the works to move OOo to an independent organization.

      Apache is in essentially the same boat as XFree86 at this point. Some businesses depend on them and that's what keeps them afloat, but that's only because they haven't moved on to bigger and better things yet. They will eventually, and OpenOffice will be forgotten about.

      And yet, Apache is one of the largest FOSS contributers, managing some of the largest projects out there, now inheriting another large project. The only other entity out there by comparison that has as many projects under one roof is the FSF. Yes, some projects at Apache end up petering out; but they are not kept afloat because people refuse to move on.

      --
      Truth is like the sun. You can shut it out for a time, but it ain't goin' away. - Elvis Presley (source: imdb.com)
    5. Re:It's now for derivating software by marcosdumay · · Score: 1

      Bring together lots of different parties, that release code on different licenses (some even proprietary), so they share a toolbox? No can't be done with the GPL.

      I tought people here at /. would be informed enough to know the OO ecosystem; or at least smart enough to saerch it.

  11. Comment removed by account_deleted · · Score: 5, Informative

    Comment removed based on user account deletion

  12. I'm good with this by Anonymous Coward · · Score: 5, Insightful

    The Apache license isn't the perfect "open" license, (I preferred GPL2), but I'm still good with the Apache License. Since Apache is a neutral player, they won't be imposing 'will' or 'vision'. Still, its connections with Oracle presses me to use LibreOffice instead, at least for the immediate future. The hazards of forking any project is that a once viable branch inevitably falls behind. However, whenever I look at the demise of a branch, I look at the reasons surrounding the fork (usually greed, or some kind of restriction where the license or code base is used to beat contributors over the head), at which point, the fork occurs. Usually there is remorse afterward, but once a project forks, it never goes back. Its happened a lot. The 'open' version of Java is now the default version of Java. XFree86 is now X.org. Before GTK, the license restrictions around mosaic were incredible. The people who started Mambo tried to turn 'Free' into 'Mine'. The fork became Joomla. Backpeddling ensued, but stick a fork in it, it was done. Hello LibreOffice.

    1. Re:I'm good with this by Anonymous Coward · · Score: 0

      "The 'open' version of Java is now the default version of Java

      I wish that were true, but at my work station at work the default is definitely not the open source version. I am no looking forward to the day when the oracle version hoisted on my dt causes my OSS software to no longer run.

    2. Re:I'm good with this by Anonymous Coward · · Score: 0

      but once a project forks, it never goes back. Its happened a lot.

      GCC forked and then re-merged. But yeah, that's the exception.

    3. Re:I'm good with this by Anonymous Coward · · Score: 0

      I'm not sure it merged as such, rather the fork was "blessed" as the new version. The projects merged I suppose.

      Compiz and Beryl re-merged similarly too.

    4. Re:I'm good with this by chooks · · Score: 2

      ...once a project forks, it never goes back...

      This happened to Christianity in 1054, with another major fork happening in the 16th century. I guess it had a lot to do with questions regarding the disagreements with management of the code base and who is best able to do that (or something like that).

      Now it seems like there is a fork every week or so. Who can keep up with the versions? No wonder we had to develop distributed version control, since everyone seems to want their own local branch to work with. Merging it all back to the tip (or trunk) it pretty much impossible -- the devil is in the details!

      --
      -- The Genesis project? What's that?
    5. Re:I'm good with this by Anonymous Coward · · Score: 1

      Don't forget that Christianity is just a fork from Judaism. And Islam is a fork also.

    6. Re:I'm good with this by StormReaver · · Score: 1

      Before GTK, the license restrictions around mosaic were incredible.

      Did you mean Motif, rather than Mosaic?

    7. Re:I'm good with this by Anonymous Coward · · Score: 0

      And Zarathustinism ?

  13. Comment removed by account_deleted · · Score: 4, Insightful

    Comment removed based on user account deletion

  14. Use Calligra instead by ingwa · · Score: 3, Interesting

    If you want to embed or reuse a library then I would suggest that you would be better off by using the Office Engine from the Calligra Suite (http//www.calligra.org/). It is already used in many mobile and embedded places, e.g. the office viewer in the Nokia N9 smartphone. The engine -- and the apps themselves -- are all under LGPL which makes it usable even with non-free apps.

  15. No dumb questions, just dumb.... by Anonymous Coward · · Score: 0

    No, Oracle ended up donating the OpenOffice.org trademarks and rights to the source code fully to the Apache foundation after all the hullabaloo over the OpenOffice/LibreOffice split.

  16. Yes they do by Anonymous Coward · · Score: 0

    They pronounce it "libber office", same as every average American.

    (Yes I do consider it a poor choice for a project name, and I'm a programmer, not a marketing stiff.)

    1. Re:Yes they do by tunapez · · Score: 1

      My Spanglish skills are quite rusty, I had to look it up. For the life of me I could not understand why they called the fork 'Book Office'.

      --
      Imagination drew in bold strokes, instantly serving hopes and fears, while knowledge advanced by slow increments...
    2. Re:Yes they do by Anonymous Coward · · Score: 0

      book is libro, not libre.

      Ooh, CAPCHA --> decipher.

  17. OT, but comparison of LibreOffice to OpenOffice? by edmicman · · Score: 1

    It's actually been awhile since I've installed or used OpenOffice...I've been using Google Docs myself mostly and for family they've all been running old copies of OpenOffice forever. I'd originally dismissed LibreOffice as a cumbersome-named knockoff and OO was working for me so I just ignored it. My wife does have some complaints she's run into with OO; is LO more actively maintained, faster/more efficient, or have imrpoved features over OO now? Is it worth changing over or upgrading?

    Ya know what I'd really like - instead of either of these packages chasing MS Office 2003, I'd like to see something like what Firefox (and now Chrome) did to the browser product space, but for office productivity suites. Where's my small, lightweight, and fast word processor, spreadsheet app, or presentation software that is straightforward to get into but also has the pro features I might need, too. But not buried under tons of menus, nor ribbonized. Where's the innovation that we didn't know we even needed? Maybe Apple's office software does some of that, but I've never used it. But I always remembered OpenOffice feeling very bulky and dated. It worked, was better than shelling out $200 for MS Office, but didn't really improve on what it was replacing.

  18. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  19. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  20. Re:Use Calligra instead - KOffice take two by Anonymous Coward · · Score: 0

    This is KOffice, right? I have always been impressed with the architecture of KOffice but haven't ever been able to get over the UI. It made OpenOffice look minimal and organized! I truly hope that with Calligra 2.4 they release something that is also stable and nice to use. There needs to be a second reasonable Office Suite option for Linux.

  21. Re:OT, but comparison of LibreOffice to OpenOffice by walterbyrd · · Score: 1

    From what I have seen: OpenOffice is faster, but LibreOffice has more features.

  22. Re:OT, but comparison of LibreOffice to OpenOffice by perryizgr8 · · Score: 1

    on my laptop, google docs on chromium or even microsoft live documents on chromium perform better than libreoffice native program. faster operations, auto-saving, much better ui (both google and ms), and documents are saved in standard formats that can be used everywhere else without headaches.

    --
    Wealth is the gift that keeps on giving.
  23. Re:OT, but comparison of LibreOffice to OpenOffice by udoschuermann · · Score: 4, Informative

    is LO more actively maintained, faster/more efficient, or have imrpoved features over OO now? Is it worth changing over or upgrading?

    Yes, yes, yes, yes, and again yes to all of your questions!

    LibreOffice has not only merged countless improvements that OO.o cannot merge (because of license issues), but has cleaned up a lot of code, removed dead code, fixed known problems, improved work flow, removed limitations, improved compatibility with other software, upgraded to ODF 1.2, and made the program better in countless respects. They're also providing explicit release schedules for major and minor versions (e.g. 3.5.0 is due Feb 8, and 3.5.1 is due in the first week of March, then 3.5.2 is due in the first week of April, etc.), and are properly open about the coming features, the road map, funding, etc.

    Sure, you can certainly get plenty of mileage out of existing installations of OO.o today, but if you have no compelling reason to stay with OO.o you should definitely consider upgrading to LibreOffice. I'd wager that you'll be very glad to have done it.

    Bottom line, OO.o is dead and gone in all but name. I really don't see much point in continuing to spend energy on OO.o these days.

    instead of either of these packages chasing MS Office 2003, I'd like to see something like what Firefox (and now Chrome) did to the browser product space, but for office productivity suites

    The core difference between browsing the web and working with documents is the persistence of data and how predictable (consistent) your data is presented. Nobody in their right mind expects web pages to look the same, regardless whether you use Opera, Firefox, Chrome, MSIE, or Lynx. But when it comes to documents, people get upset if a word wraps earlier in one product than another, their carefully crafted one page document suddenly overflows by two words onto a second line, their embedded images aren't properly aligned, etc. Sometimes these are legitimate concerns, sometimes it's just a matter of mismatched expectations, but overall it's a different ball game.

    So if you want to play in the office/document playground, you can't afford to alienate too many people before you start stepping out of line, and improving on the old and trusted formula that so many people take for granted.

    --
    --Udo.
  24. Possible to release LibreOffice as Apache License? by gral · · Score: 1

    Changing a license means that you have to work with the Source owner. Now that Apache Foundation owns the OpenOffice.org codebase, does that mean that LibreOffice could change the license to ASF? Assuming the developers on LIbreOffice are ok with the move...

    --
    Scott Carr
  25. Re:Possible to release LibreOffice as Apache Licen by Anonymous Coward · · Score: 0

    I don't think so - mostly because the GNU/Nazis would flip their lid. Why make your code open and free to maximize adoption when you can push a sketchy agenda?

  26. The ghost of Christmas Future points out: by jensend · · Score: 2

    Unless a lot of things about this project change it is pretty much doomed. (Well, doomed to be ignored by everybody outside of IBM; they can finance their own Symphony devs, but nothing else will come of this unless things change.)

    If you glance at the Apache openoffice mailing lists, a few things become clear:

    • Rob Weir, who is basically running the show and who seems like a perfectly reasonable person from his blog, acts like a caustic, sarcastic, and poorly socialized adolescent in communicating with other developers. He's alienating people right and left. People have tried to get him to stop, but he either ignores it or just acts like it's those he's offended who are to blame for any unpleasantness.
    • Due to Rob's attitude and other unfortunate factors, any chance of gaining cooperation from anyone who's been involved in LibreOffice has pretty much evaporated. If there'd been a little bit of diplomacy, I bet a lot of people would have been OK with dual-licensing their patches for Apache OO to use as well, and the two projects could have gotten a lot of mutually beneficial effort in support, security, localization, language tools, and extensions; AOO folks have instead opted to prioritize insulting LibreOffice folks over getting anything done.
    • They tore a lot of functionality out of OpenOffice for their license compliance crusade. I can understand that they can't ship copylefted code, but tearing out the use of LGPL'ed libraries seems kind of ridiculous. (For me personally, the loss of WordPerfect import is going to force me to LibreOffice.)
    • Apache OpenOffice 3.4 won't be released until the middle of next year-- the first OO release since this January, with relatively little improvement over OO 3.3 and a fair bit of missing functionality-- LibreOffice will have gone through three "major" releases and another dozen point releases, fixing a lot of bugs, refactoring a lot of code, and introducing a few new features. AOO will have taken roughly a full year (June 2011-2012) to make their first code shipment and people will have long since moved on.

    I really wanted to see Apache OpenOffice succeed and become the main branch; I think that for a project like OO, having either a permissive license or copyright assignment to a well-governed nonprofit (as with GNU software) is a really wise idea. But I can't see them making much progress as things stand.

    1. Re:The ghost of Christmas Future points out: by Anonymous Coward · · Score: 0

      I see that Rob has learned the lessons of Theo de Raadt: make a fork, pretend it matters, and crow about the "features" that no one uses because they can't even get it installed.

      Oracle didn't buy Sun to take over this project: they bought it to get the MySQL customer list and the high end database hardware customer list.

  27. Re:OT, but comparison of LibreOffice to OpenOffice by jensend · · Score: 1

    An office suite can't be "small" and "lightweight" and have all "the pro features I might need, too." You sound just like Agnes in Simpson Safari: you want all your groceries in one bag, but you don't want the bag to be heavy.

    You can get lightweight, fast office software; for example, you can use AbiWord for your word processing needs. But it doesn't have every feature under the sun, and if it did have every pro feature anybody "might need" it wouldn't be lightweight.

  28. So... by ThisIsNotMyHandel · · Score: 1

    So pretty much ASF is killing OpenOffice....

  29. OO + symphony by Anonymous Coward · · Score: 0

    The release will be good if it is paired with Symphony and use latest Eclipse technologies.

  30. Re:OT, but comparison of LibreOffice to OpenOffice by Anonymous Coward · · Score: 0

    "The core difference between browsing the web and working with documents is the persistence of data and how predictable (consistent) your data is presented."

    Soon there won't be any difference between browsing the web and working with documents, because you will work with documents on the web. Office packages will get web GUI's created with canvas (HTML5). GIMP can already be used in a browser, because GTK+3 has canvas output support.