Re: Re: [trinity-devel] kbugbuster

On Saturday 25 August 2012 15:41:40 Slávek Banko wrote: I am not hostile to you. I am trying to improve the situation of the fork. Yes part of that includes to unfork to make Trinity acceptable to the KDE community. Please realize that I am basically the only one of the KDE project reaching out to Trinity. I want the communities to be one community. I want to overcome the hostile situation we are in caused by the Trinity fork. You know that KDE developers consider the fork performed as Trinity as hostile? You know that developers asked you to change names as they don't want that people think that its the same product? You know that many KDE developers are very concerned about the drop of quality? You know that many KDE developers fear that Trinity destroys the reputation of KDE 3? You know that many KDE developers feel it's an affront that Trinity devs talk about the KDE version which they have not developed as "their" app? If it is a hostile act to ask you to rethink your forking strategy because you don't have the manpower to cary out the tasks previously done by hundreds of developers by a little bit more than a dozen, then sorry, then I'm hostile. well if comparing a person with a dictator is not an offense, well then I have a different understanding of offensive talk. Btw. it does not matter that it was not meant offensive (we don't know that because Philip has not replied yet), it only matters how the person being insulted feels about it. A simple sorry, was not meant that way clears matters up. Your project? Keep in mind that the code of your project has been written by the KDE community. But well you wanted respect for Trinity. I applaud any effort to keep Kicker/KDesktop (the KDE 3 "desktop computing") alive. I know and acknowledge that there are users disliking KDE Plasma. I would love to have something I could offer them to use. That is what I would love Trinity to provide. That is what I am interested in to see. That is why I contacted the Trinity team in the first place. But at the moment I cannot tell users disliking Plasma to use Trinity, because it includes forks of everything and the kitchen sink where KDE just has the better products. Think of KWin, Kate, Krita and so many more excellent KDE applications where the KDE 3 version is just on a different level. Then there is the problem that I cannot tell users to use Trinity because it uses EOL-ed libraries like Qt 3. I have done my Computer Science Master degree at a Chair for Computer Security. I just cannot recommend anyone to use unmaintained libraries which are security relevant. And that's just a pity. But you see I have an interest in Trinity. I hope that is enough shown respect. Think about whether its help or not. My first contact with this mailinglist was to ask you to use KWin instead of your fork, because you have not been able to maintain the window manager. I have shown you wrong commits, I have later on reviewed code to the fork. I offered you to get a well maintained codebase instead of something you have no expertise on. Well I call that help even if it includes dropping part of your fork. Want a list of bugs reported against KDE 3 and fixed in 4.9? Recently I have told you here in this thread that KBugBuster has been dropped from KDE and given you the reasons which you were unaware about. I think that's already quite some help. good. No you are wrong. KBugBuster used to be part of KDE-sdk till 4.5 - which is two years ago. Much younger than the 3.5 version Trinity forked. Also there had been some work which has not been finished going on by some students to be found in [1]. Best Regards Martin [1] http://websvn.kde.org/branches/work/kbugbuster-isi/KBugBuster-v2/