[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice-devel
Subject:    Re: KOffice split
From:       Sebastian Sauer <mail () dipe ! org>
Date:       2010-10-29 2:33:09
Message-ID: 201010290433.09997.mail () dipe ! org
[Download RAW message or body]

Dear Thomas,

On Tuesday 26 October 2010 23:38:04 Thomas Zander wrote:
> The main reason for splitting is not about
> applications, the main reason is also not about application maintainers.

Let's stick closer to reality please. The main reason is that lot of our long-
time koffice-developers have problems with you. There are serious 
interpersonal "issues" going on between a group of koffice-developers and you 
for a *very* long time now. We are talking about at least 5 years here. There 
where tons of tries to solve that over the past years and they all failed.

> The actual background reason is about focus and how to be part of a
> community.

1. "focus"

Focus sounds always good but that's not the current problem. Even if everybody 
would share focus (what is silly to ask for in a FLOSS-project btw) the 
interpersonal problems would still be there.

2. "to be part of a community"

Nope.

> The split as its proposed really is not a split for applications. As
> Cyrille wrote; the group B will fork KWord. So lets call this whole thing
> what it is, a fork off of KOffice

Only kword, the textshape and maybe parts of libs will be forked and nothing 
else cause that's where the problem is code-wise.

I believe that the KWord-fork will have a good and promising future as a very 
good wordprocessor for the KDE-desktop. I do count at least 5 kword-developers 
who already contributed in the past and would join the kword-fork. That 
includes me and 2 other long-time koffice-developers. The majority of that 
group is btw unpayed.

I would suggest we are looking now how to get cooperation between your and our 
kword done as very next step. Since we will stay within the same repository 
under the same KDE umbrella that shouldn't be that difficult. Let's move 
forward!

> focusing on getting it ready to render
> MSOffice documents properly and getting it working for Meego using the
> ways of working that Nokia uses for such projects.

This has nothing to do with Nokia (which you are an employee of iirc) or with 
any other commercial or non-commercial entities. This has to do with 
interpersonal problems between you and others. Please let's not try to turn 
that into something it isn't and let's stick closer to reality. Thanks.

If it comes to priorities mine btw look like;
1. get koffice stable
2. get koffice fast
3. Improve display+edit in the application
4. improve loading of ODF documents
5. improve loading of MSOffice documents
6. Improve saving of ODF

In that order cause of koffice's filter-architecture which looks like;
MSOffice-document=>ODF-document=>KOffice-application
So, every MSOffic-document is translated to ODF and then loaded from the 
application. The whole stack is worked on. My priority was always like that 
since our akademy2005 ODF-sprint.
_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel
[prev in list] [next in list] [prev in thread] [next in thread]