Koko in KDEReview

Harald Sitter sitter at kde.org
Tue May 4 08:16:16 BST 2021

On 04.05.21 00:07, Carl Schwan wrote:
> Le lundi, mai 3, 2021 4:35 PM, Harald Sitter <sitter at kde.org> a écrit :
>> On 23.04.21 01:00, Carl Schwan wrote:
>>>>>>> -   please get a bugzilla produce created for it
>>>>> Not a fan of that. This will ends up exactly like the www bugs, something
>>>>> that I look into every 6 months. We already have many issues opened in
>>>>> invent and it's working fine for us.
>>>> Did I miss something? The last agreement I recall was that we are using
>>>> bugzilla for bugs and gitlab for tasks for the time being. If even as
>>>> developer I have to go hunting where $project tracks their bugs I'm sure
>>>> not going to be a happy camper.
>>>>> Also we don't use KCrash.
>>>> Shouldn't you?
>>> The problem is that DrKonqi doesn't really work on Plasma Mobile and I don't think
>>> this justify getting locked up in using Bugzilla. If having a bugzilla product
>>> is really required, we can request one but I can't guarantee that I will look at it
>>> more often than I look at the kde-www bug reports in bugzilla (every 6 months).
>> Let's consider it required then.
>> If you don't care about crash reports that's your choice I guess, but it
>> does kinda call into question the product quality since you also don't
>> have an alternative system to the kcrash-drkonqi-bugzilla caravan. Quite
>> clearly koko would have benefited from crash tracking and since the only
>> solution we presently have for that is the aforementioned stack it quite
>> clearly also would have benefited from being on bugzilla to receive
>> those crash reports and potentially move to other products if the crash
>> is not in koko. After all, crashes get submitted to the product that
>> crashed, not the library of the top most frame.
>> I have to be honest, it is a bit surreal to even have to argue this. I
>> get thorough enjoyment out of throwing tomatoes at the current system
>> but to actively pretend that the problem-domain of crashing software
>> doesn't exist so you don't have to look at bugzilla sure as heck doesn't
>> solve anything. In particular since you pitched koko as convergent and
>> useful on the desktop.
>> If all that's stopping you from embracing crash tracking is drkonqi then
>> I am happy to tell you that sticking a mobile-suitable UI on top
>> shouldn't be all that difficult ;)
> Would you be open to an MR adding GitLab support to DrKonqi?

Once there's actually agreement on moving to gitlab. The code is not the
problem here. Code is easy. We are hackers after all.

Every time the bugz vs gitlab schism comes up I eventually tune out with
the distinct feeling that there is strong opposition to moving. What I,
what we all, do not want is to end up with two systems that require us
to maintain two client libraries with double the bugs for the next 10
years, and everyone gets to roll a dice which platform a given product
tracks bugs on. So what we need is community agreement which BTS to use
long term and then we can drive the technical changes to make that happen.

Short to mid term bugz is the reality we have to live with.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20210504/314f8b97/attachment-0001.sig>

More information about the kde-core-devel mailing list