23 Aug
2012
23 Aug
'12
6:34 p.m.
On Thursday 23 August 2012 18:09:29 Slávek Banko wrote:
On Thursday 23 of August 2012 17:52:59 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
On Friday 17 August 2012 16:05:59 David C. Rankin
wrote:
When we add to KBugBuster support for new versions of Bugzilla, so no one
will defend you to take changes also into KDE4 version of KBugBuster. That
will be your choice, as it is our choice to not use KDE4, but to develop
the Trinity. Has anyone pulled the latest kde4 version?
there is no latest kde4 version [1]. The bugzilla interface changed too
much, kbugbuster just does not work with later versions of bugzilla [2].
I would be surprised if the Trinity version of kbugbuster works with the
Trinity bugzilla. If it works, then I would highly recommend to update
your
bugzilla installation (as in that case it would have severe security
issues).
Btw. these are the things were a closer interaction between KDE and
Trinity
would help. Instead of long discussions and trying to fix it, the relevant
information could have easily been gathered.
It would be so awesome if Trinity could concentrate on the things that
matter and stop forking everything and the kitchen sink. I still hope that
we can unfork Trinity.
Oh yeah and in case you really want to fix kbugbuster it would be super
awesome if you would take up the kde 4 version and work upstream instead
of
a fork.
Best Regards
Martin Gräßlin
[1] http://websvn.kde.org/tags/unmaintained/4/kbugbuster/
[2]
http://websvn.kde.org/tags/unmaintained/4/kbugbuster/version.h?revision=11
9
3777&view=markup