trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: April 2012

Re: [trinity-devel] Resolving the TWin/KWin Fork Issue

From: Aleksey Midenkov <midenok@...>
Date: Sat, 21 Apr 2012 11:39:21 +0400
On Fri, Apr 20, 2012 at 3:26 PM, Martin Gräßlin <mgraesslin@...> wrote:
> Hi all,
>
> I had to see that there is still development going on in your fork of KWin and
> I am very unhappy about that. This is something I really want to see resolved,
> any development to KWin should happen in KWin, it's such a waste to work on
> the same project without coordination.
>
> Let's first recapture the state of TWin:
> = Why does TWin exist? =
> Because KWin got forked together with everything else from KDE 3.5 to form the
> Trinity Desktop Environment (TDE).
>
> = Why has the TDE fork happened? =
> The TDE fork existist because of a combination of the following reasons:
> * Parts of KDE had to be rewritten in order to be ported to Qt 4
> * Early versions of KDE 4.x were lacking functionality compared to KDE 3.5
> ...

And now it is not lacking that functionality from KDE 3.5?

I watch TDE more than year and conclude that it has a number of
serious shortages:

1. Very small number of developers (3-4).
2. No or weak development policy. The development is spontaneous.
3. Insufficient development experience.

I would have placed problem number 3 as the basis of all troubles. The
project now plays the role of training playground. Which may be
benefit for those who learns. But is unexpected from the rest of TDE
users.