Slashdot Mirror

← Back to Stories (view on slashdot.org)

One Year Of OpenOffice

Posted by ryuzaki0 on from the what-a-burpy-baby-you-have dept.

no parity writes "Last year on October 13, much of the source to Sun's StarOffice was released as the OpenOffice project. They have set up a birthday page to celebrate what they have achieved in that one year - yes, it prints, spellchecks and has online help. Keep up the good work, guys!" Yep - and my installation still spits up, too. *grin*

3 of 215 comments (clear)

  1. Getting there by CmdrTroll · · Score: 5, Interesting
    My roommate was an intern at Sun last summer, and he was assisting the OpenOffice team with resolving compatibility issues with MS Orifice 2000. He said that was the biggest stumbling block for the project, aside from memory management and speed issues. He also said that the DoJ was privately talking to a few of his co-workers and they were interested in widening the probe into monopolistic file format practices. I doubt that the current administration will give it a green light, but if they do, that would help knock down the last barriers to seeing OpenOffice on every Windows desktop in the near future.

    Wishful thinking...

    -CT

  2. OpenOffice needs MacOS X programmers! by sakusha · · Score: 5, Informative

    Since StarOffice dropped official support for MacOS X, OpenOffice needs more MacOS X programmers. Microsoft is going to make a huge marketing push for Office X, but if we had working OpenOffice versions, their monopolistic push could be thwarted. But it's too late for now. We need help!

  3. Re:Congrats - What will it take? by Tumbleweed · · Score: 5, Interesting

    Well, _most_ businesses wouldn't bother unless it _can_ read and write with MS Office apps. I think that's what the DOJ should really do - force MS to open their file specs.

    I think it'd be great for Lotus to open the source to SmartSuite - since IBM owns them, one wonders what the chances are. Then again, they've not opened the code to the OS/2 WPS. *shrug* I've heard from people inside IBM that there's too much licensed code inside those products for them to be able to do that - they simply don't outright own the code those products are made from. That's a shame.