Announcing itself today is KOfficeSource GmbH, a
company that will sell services around KOffice. The founders comprise a small group of
members of the developer community, as well as outside talent. They share an interest in furthering KOffice by supporting it
commercially in addition to the non-commercial support that can be
found on the mailing lists and IRC. As the name suggests
it has been created in Germany but will operate across Europe and further afield.
"The founding of KOfficeSource GmbH shows the commercial potential of the KOffice suite.", said Sebastian Kügler, KDE e.V. director. "It is great to see a company spinning off the KDE Community. Combining the commercial experience in the field with excellent connections in the community seems to be a recipe for success. And success is also what we wholeheartedly wish to the founders of KOfficeSource.
Kügler continues: With the upcoming release of KOffice 2 later this year, this makes for a new contender in the office market space which no doubt will be beneficial for institutional, commercial and home users alike."
The founders of KOfficeSource GmbH are:
- Tobias Hintze: CEO (Geschäftsführer)
- Boudewijn Rempt: maintainer of Krita
- Inge Wallin: marketing coordinator and maintainer of KChart
- Kalle Mattias Dalheimer: KDE founder and owner of Klarälvdalens datakonsult.
From the announcement:
What is it?
From the start, KOfficeSource GmbH will function as a pure services
company. We will offer professional services around KOffice such as:
- Customising, e.g. by adding features or creating new GUIs.
- Integration into workflow systems or other products.
- Training for users, system administrators and programmers.
Since KOfficeSource does not own any copyright to the code, we can not
and do not want to steer the development in any particular direction.
We will work with the community, basing our services on what the
developers are already producing
Sometimes we will create new features, new modules or maybe even new
components for KOffice. We will then offer the new features to the
community to accept into KOffice or decline as it sees fit. We will
work with the current developer community as closely as possible when
developing new code. This means that we will work in the existing Subversion
repository, under the existing licensing rules and the existing governance customs.
What Will This Mean for KOffice?
In the long run, we think the mere existence of a company like this
will make KOffice more interesting for other companies to deploy. It
gives KOffice yet another piece in the Whole Product puzzle. If KOffice will ever be
able to challenge OpenOffice or the proprietary competition, we will need all of these pieces and more.
This is the first step in that direction.
On a shorter time scale it will probably not mean much at all. We
do not expect to become very active until KOffice 2.0 is out, maybe
even 2.1. We do not have any large funds at this time that we could
use to sponsor any development. We will offer our services when the
chances arrive and in time we will be more active.
What Will This Mean for the Developer Community?
Probably nothing, right now. The developers involved in this company
will hack on as usual, In the longer run, over a few years, we
might be able to hire developers part or full time. We have great
hopes, but they will take time to become real.
You can read more on our website.
It's great to see how the business ecosystem around KDE is flourishing. It makes KDE and KDE applications more attractive to *other* businesses simply by putting the right "face" on the community. It also makes it possible to hold on to developer talent better by offering a job at doing KDE hacking. Well, at least I hope Boud continues to do hacking and doesn't get tied up in business administration ;)
Oddly enough, I just got a Qt / C++ work-from-home recruitment offer minutes ago before reading this announcement. Things are thriving.
(PS: although I'm on the board of KDE e.V. and sometimes drink coffee with Sebas, this is the first I had heard of KOfficeSource, so above is genuine enthusiasm and not pre-cooked.)
Hey, you too?
So it doesn't matter if *I* get tied up in business administration, huh?
nah, we expect you too ;-P
congrats, guys, this is great news.
These are great news!
We all wish you good luck!
I really admire the KOffice project - it rests on *excellent* technical underpinnings (compared to OO.o's sprawling and frankly horrific codebase) and all the devs seem like nice people, too :)
Seeing some paid development on it would be great!
...but here goes: if a company requested / paid for the addition of support of various MS formats (existing binary formats, new XML wrapped binary formats aka OOXML), what would the answer be? are there moral / legal / community issues about this?
I think this is great that a company is forming around koffice and I'm really wishing you guys all the best. I'm just asking this out of pure curiosity and not trying to start flame war (which i know are usually the last lines written preceding most flame wars, d'oh)
I see no reason why paid development couldn't be for legacy file formats.
In a recent dot story the KOffice developers explained that they weren't interested in spending their own time developing it, but that's something completely different to paid development. It is also not connected to any KOffice developer's opinion if for instance OOXML should be made an ISO standard (it shouldn't) or if the file format itself is badly specified (it is) and impossible to implement fully (it is).
Thats pretty much my take on it also. Its simply neither expedient nor particularly desirable to implement 3rd party proprietary formats.
I guess the issue though is mainly that the aforementioned dot article was held up by RMS as a counterpoint to the somewhat MS-happy approach of other development efforts and there is a big opportunity for future paid for efforts to include particularly OOXML being presented in a negative light and starting all kinds of flame war fun on the usual tech blogs etc.
It matters a great deal to implement proprietary filters for *import*.
Export is another story.
Borker, notice that the KOffice community doesn't necessarly need to merge the work done by this company. I bet they will have a special build for their customers; possibly even single builds for special cases.
Except that at least half their board is composed of major Koffice contributers. (I don't recognize the names of the other 2 board members, but that doesn't mean they are outside the koffice community, just that I don't know them) While in theory the koffice community could reject their patches, since they are the community this is less likely.
I suppose it is possible they will get paid for an ugly hack that sortof works and meets a customers needs now, but isn't the direction they want koffice to go long term.
Special builds for customers, and single builds are likely. Sort of like Code Weavers has their own version of Wine, but it only better than Wine as a whole in places where they have ugly hacks that make one things sort of work while making others less likely to work.
Exactly, it's natural for variants of software to exist for different applications. No need for something unnecessary to be added to the main code base.
One thing that I kept in mind while doing plugin-interface design for KOffice2 in general and for text specifically is to make sure companies can add their own workflow features without touching the KOffice codebase.
If a company wants to have something like a special variable in text that connects to their internal database (for example), they can write a text-plugin quite easily to do that, again without touching the KOffice codebase. (see the techbase tutorials about koffice plugins)
Since the libraries KOffice provides are LGPL the company may very well choose to make the plugin they want to use closed source. Which obviously means it will never hit the KOffice codebase.
There is a nice incentive for companies to go via KOfficeSource instead of doing it in-house not only because of the expertise, but also because of the Qt licenses required to do this.
Bottom line; this significantly lowers the trashhold for large rollouts to succeed. Any missing thing can now be added by paying the experts to do exactly that.
Exciting times :)
a __BIG__ 'Good Luck' from not only me, but whole Community.best wishes for you all.
This is probably the best KDE related news in months - probably not for long, as the release of something big is imminent - and came completely unexpected for me. I hope the business side of this works out nicely, and Boud and Inge can spend a lot of time on improving KOffice even more than was the case before :P
Great stuff, and I'd like to wish you the best of luck too :D
that's really nice 2 know!
Just a question. Why is the quote at the end of the page
"World domination doesn't come by itself." -- Ralf Nolden
precisely whent I read this article :)
Wish you a lot of funy work, benefiting both your incomes and your user comunitiy.
I hope you'll have a lot of succes with this!
ok this sounds quite good, a win-win situation
make no mistake about this, i think if this works, it will be GREAT for everyone involved here, and for the users just as well.
BUT there is one thing that I want to voice (or ask), even though others might have voiced that already.... will koffice become dependent on it?
I am asking because right now, the whole linux distributions are influenced by companies just as well, and every line of code comes with a price - someone has to understand it at least enough to maintain it.
My personal feeling is, that there is a huge difference between "a company joins a project" and "a company forms out of a project" since at the later case it's more the project which influences the company rather then the other way around :-)
The real divider is whether the company owns the copyright to the program or not. In this case we don't, which I also address in the announcement, so we could never control the KOffice project.
Now, influence is of course something we hope to have, but that's hardly control. KOffice is jointly owned by the developers and that's how it will remain.
agreed; there's one other ingredient: the people involved.
in fact, it's the people part of the mix that determine whether the legal safeguards are ever brought into play. usually the legal safeguards, which are extremely reassuring and pretty vital imho, are there for the case where things go wrong. even with safeguards in place, nobody ever wants to go there. so the people being Good, Upright, Honest and Trustworthy are the key ingredients.
both Inge and Boud, along with the rest of the KOffice team, are exactly those kinds of people in my experience having worked along side them in KDE and spent time in purely social circumstances as well. i have no doubts in my mind that with the people who are forming KOfficeSource that a good community relationship will be maintained and that we will likely never end up needing to rely on those legal safeguards.
having both legal safeguards as well a good people is a killer combination. i can only see good things coming of this collaboration =)
I guess that legal safeguards are no protection against bad influence. IMHO what [email protected] was refering to are fights between different forces within a project that harm the harmony and have an impact on "how a project feels like". But that's more a general question not related to companies but to individuals aka the people involved what makes it rather difficult to find another answer then what Aaron wrote in his 3th paragraph already (and agreed there too :)
"If KOffice will ever be able to challenge OpenOffice or the proprietary competition,"
as long as KOffice stays as simple to use as it is for now, it would be OK to challenge OOo or even MS-Office. Simplicity and ease of use should be the goals for any software.
A while back someone (I think it was TJ Brumfeld) suggested that IBM could work with KOffice developers to produce a better version of Lotus Symphony that doesn't use OOo's clunky old codebase, that causes Symphony to have the speed of a turtle trapped in toffee. Would KOfficeSource GmbH be able to help in this regard by talking to IBM people about collaboration or does this have only a minuscule chance of success?
I'd also like to hear about this: IBM have smart engineers, and they should surely see that they could probably get much better progress with hiring the same amount of engineers with KOffice than with OO.o.
Mmmmm toffee turtle
IBM has made contributions to Linux because they wanted to sell hardware. They use a totally different business model for Lotus. In fact, OpenOffice has never seen a line of code from IBM (they forked while it was permitted to go close source).
I feel a ton of glad-ness about that bold move on the part of some key KOffice developers. I wish them well and all the best in this ambitious endeavour.
(I also feel a grain of unhappy-ness because they decided to single out OpenOffice.org to name as their main competitor which they intend to tackle. No, guys! Your main target should be MS Office, and OOXML. You should rather ignore OOo instead of making yourself sound envious of OOo's success. Most KDE people nowadays would think it's wrong to make a press release saying KDE4 aims to take market share away from Gnome. And it is not just "tactics" to do so. It is to recognize who your *main* adversaries and competitors are: and these are MS and Apple, not The Second Free Desktop...)
Well I'm fine with it, currently I'm an unhappy OO.o user due to various bugs in KOffice. I hope this company will end up improving quality control and reduce the OOo market share by one user. :)
You're right, of course.