11

Why?
We've all read about how revolutionary the different parts of Koffice are.
We've all wondered what could happen to OpenOffice.org now that its makers have been bought by potentially FOSS unfriendly forces.
We all use one kind of app or another that there is an equivalent to in Koffice (eg OOo / Gimp / Inkscape etc)
We've all heard how little manpower Koffice has for the value and size of the project.

Why?



The Problem:
People wanting to help with Koffice are mainly blocked by the need to either:

• Compile all the Koffice apps and dependencies they need (NEWSFLASH: no normal user compiles, but they can still contribute!)
• Use packages that are often very outdated. I reported and were quickly resolved from *April* that I still can't test.

The Solution:
Compare this to nightly packages. I don't compile, yet I help with current SVN versions of:

• Amarok
• Pitivi
• Chrome
• Firefox 3.6
• the Kde Multimedia apps.
• KDE-plasma-addons
• Inkscape

All these projects provide nightly builds. Project Neon already creates the base KDE libraries nightly to all (K)ubuntu users. Other distros are rumored to possibly be added later. Either way, this system is set up and working *now*. Contributions from users of one distro benefit *all* KDE users. Adding Koffice to the automated packaging lineup would make it so easy to bring many testers and contributors to this important but understaffed area of KDE. Setup once and forget.



Help Out in Under 2 Seconds:
So, if:
you would like to see Koffice with more enthusiastic users...
you would like to see Koffice get the contributions it needs...
you would like FOSS to have a backup plan if something happens to OOo...
you would like to take the FOSS battle deep into the heart of MS's cashcow (Office)....
you would like to give the hardworking Koffice devs a hand (or 50)...

...then please vote YES on this suggestion now! Thankyou!