-2

First, don't kill me while reading this.

Calligra and LibreOffice could share the same base code.

Instead of splitting resources...

This way, both Softwares could get and incredible boost since devs will be working all together for the base code ("how" to read documents, how to write them, etc)

Kill Calligra? NO! I'm not saying that!! I'm just proposing that Calligra could be the Interface for LibreOffice in Kde!
So the devs could have more time improving Calligra and not doing lots of work that is already done in LibreOffice (and LibreOffice would benefit of improvements done in Calligra too)

Note: some will point that this is also (and more) applicable to OpenOffice and LibreOffice... but well... I don't know what's really happening there...

Killing you is tempting…

But seriously, what you suggest could be said about any software with the same goal, probably for more than half the applications that call themselves KDE or GNOME applications, or even Qt and GTK applications (and I’m skipping other toolkits and desktop environments, which are also relevant).

But:

• It’s seldom as easy as it sounds.
• It’s seldom as useful as it sounds.

If there is a real need to share code, it will be shared. Otherwise, I think it’s rather healthy for free software to have variety.

Gallaecio wrote:Killing you is tempting…

Thanks for not doing so

I guess you're right in every aspect.
I'm just one of those that don't like to see splitted efforts for the same goal...

It's just brainstorming

jpxsat wrote:I'm just one of those that don't like to see splitted efforts for the same goal...

The general idea of not reinventing the wheel is completely valid, and I think everyone agrees on that. The thing is that, while similar, the goals of different applications are seldom completely the same. Also, they say “it's not about the destination, it's about the journey”; with software development is the same, and questions as apparently stupid as the preference for a different programming language, toolkit, or even a license, are for some people reason enough to fork things and build things differently. I for instance wouldn’t hesitate to fork a project because of not agreeing with their licensing.

Anyway, rather than suggesting to merge two (big!) projects because they share the same goals, you might want to ask why they both exist, which goals they share and which they don’t share, and what other differences there are between them underneath.

An interesting read on why Calligra does: http://ingwa2.blogspot.com.es/2011/05/c ... tware.html (first result from a search engine).