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

List:       kde-devel
Subject:    trinity koffice
From:       Boudewijn Rempt <boud () valdyas ! org>
Date:       2010-01-23 10:04:18
Message-ID: 201001231104.18445.boud () valdyas ! org
[Download RAW message or body]

We've been seeing automake patches going into the trinity fork of KOffice 1.6 
this week. I don't really mind: it's free software and all that, but I'm 
worried that if this project gets users, people will go to krita.org for 
information, submit krita bugs in bugs.kde.org, ask for help on #krita and 
generally bother me about software I can't even run myself anymore, and which 
will be utterly obsolete by September -- when we have the first ready-for-the-
public release of Krita 2.

I'm not even sure I want to be in the about box of a forked Krita 1.6, to be 
honest. Krita has changed so much and improved so much -- a couple of years of 
hard work later, we've got a host of new features, lots of performance work 
that will be done over the next few months. No current Krita developer wants 
to support 1.6 anymore.

I guess many of the other KOffice authors will feel the same for their 
applications.

Could there be some way of renaming the applications so users won't get 
confused? As I said, it's free software and I'm absolutely fine with forks, 
but renaming a forked application is a basic part of forking.

-- 
Boudewijn Rempt | http://www.valdyas.org
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]