On Thursday 23 of August 2012 20:34:18 Martin Gr��lin wrote:
> From what I understand in this thread you want to improve KBugBuster.
> That's awesome because there is no community aroung KBugBuster anymore. I
> have been hoping that someone would pick up KBugBuster and make it work
> with new Bugzilla versions for years.
>
> Now what I do not understand is that if there are people who want to work
> on it, why they need to fork and why they have to use an outdated version
> as the start point of the fork? Could you please explain me the reason why
> the Trinity project had to fork KBugBuster? Please give me an explanation I
> understand and which provides some very good reasoning why it is more
> important to work against each other than to work together.
>
> And no, because it's KDE 3 does not count in this case. What exactly in
> KBugBuster was so bad that the KDE 3 source base had to be forked?
>
> Best Regards
> Martin Gr��lin

I use Trinity, I'm trying to improve the Trinity, KBugBuster I will use 
exclusively in Trinity and mainly for Trinity Bugzilla. Another motivation 
for me is the interest of other Trinity developers.

Now you tell me, what would motivate me, that instead for Trinity, should I do 
it for KDE4? ...that I do not use. And where was the "interest" such that you 
have stopped development? I miss a reason.

Slavek
--