This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --RBJ8uFPtkrSPLpaIbU339gedNvKTP9DAQ Content-Type: multipart/mixed; boundary="cpiF59aWUG6Ax2mIxMvANbmvJYHcCrjFk"; protected-headers="v1" From: Harald Sitter To: Carl Schwan Cc: "kde-core-devel@kde.org" Message-ID: <7fb0c2ef-7350-1223-9b72-3f6650bd176c@kde.org> Subject: Re: Koko in KDEReview References: <7XBZgMI_S2VuPlLe3-KR3hMAXTId1AbKxk8ULQX_k_1SVRT7tNHR1TFmsruYVcSVAL6i7AiUYFklp1HJb8WC-4NYHio0k_J4s98KFt7Yn6Y=@carlschwan.eu> In-Reply-To: <7XBZgMI_S2VuPlLe3-KR3hMAXTId1AbKxk8ULQX_k_1SVRT7tNHR1TFmsruYVcSVAL6i7AiUYFklp1HJb8WC-4NYHio0k_J4s98KFt7Yn6Y=@carlschwan.eu> --cpiF59aWUG6Ax2mIxMvANbmvJYHcCrjFk Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable 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, somet= hing >>> that I look into every 6 months. We already have many issues opened i= n >>> invent and it's working fine for us. >> >> Did I miss something? The last agreement I recall was that we are usin= g >> 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 su= re >> not going to be a happy camper. >> >>> Also we don't use KCrash. >> >> Shouldn't you? >=20 > 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 wil= l 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 ;) HS --cpiF59aWUG6Ax2mIxMvANbmvJYHcCrjFk-- --RBJ8uFPtkrSPLpaIbU339gedNvKTP9DAQ Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wsF5BAABCAAjFiEEmUvOVl9TGc6jhe6fuSpfBOyUkSEFAmCQCjIFAwAAAAAACgkQuSpfBOyUkSFo IBAAw8dhCfCpfI4MrfVzFT3r1gs8eyUf1PaOFyriBz9XHTPvZFuZvEfKCq3/uQHaTQgh/glCA4wo HriPdtStdLntsjD//TEAraf5jQQ1IBqEnJWO1oooqpncPRXdSDgYUZnW0+HTMesimMdK5bATQo+S Y1+egWaJp/75PA7OUYeBXnc+4KUFFmwm3BcIS6rWVJ/DGb35RN0OyW9epQDLsw3rtXbNBqHKV1MA ui22c+hJdyJVjy3EHHWkC9FoxxguCLGkI3bXH75AHivl6ubxyiDagqlN4wOqrehAQ6PbJxbf4D/6 7m9HHmK7fVc/qe3ZX3rlwfwh+O7nAMMuZWQRtvTztC9ig407E4lL+stZc/E0E+9N3COZ/3Evb4d7 hIofJWqcSDw6oDNA7Dp4HU8ellRMIFEgSyOXqHik+wLWVPznleNMOrLiWnYnoBgdyDkvzUNSA2bZ CKWfdrR40+bjxYlDIUGsUpAI1ko0/MqwGjr0NGJoa+hcaYgmu0wFRPS2xa8vUkckhSJW3wXGtgld YI/hniJJ12FJ6Ypekg6tQp1tq6ezAm0uV5g4ybJWhJYzveMHZLmX5wbsXeuKV7DPWLT1XEhsDIAu zpHij+cYfW3jv8INEXGRfVnb3cnZ2szxnLzetd8M4oCw5S7A2wX2b7QtbYlCVA1ZGuqwT/xYQ7L4 Oe4= =fqrh -----END PGP SIGNATURE----- --RBJ8uFPtkrSPLpaIbU339gedNvKTP9DAQ--