This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --vIZaAIXgIa7gmD2EmJmN1DEd9NXGga8el Content-Type: multipart/mixed; boundary="1gjBmo8lAyfj5OKkY61nyGVLJDsksx1P3"; protected-headers="v1" From: Harald Sitter To: Nate Graham , kde-core-devel@kde.org Message-ID: Subject: Re: Koko in KDEReview References: <7XBZgMI_S2VuPlLe3-KR3hMAXTId1AbKxk8ULQX_k_1SVRT7tNHR1TFmsruYVcSVAL6i7AiUYFklp1HJb8WC-4NYHio0k_J4s98KFt7Yn6Y=@carlschwan.eu> <7fb0c2ef-7350-1223-9b72-3f6650bd176c@kde.org> <53e95e93-29d0-95fe-c1b7-a26a4132e133@kde.org> In-Reply-To: --1gjBmo8lAyfj5OKkY61nyGVLJDsksx1P3 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 04.05.21 15:28, Nate Graham wrote: > On 5/4/21 1:16 AM, Harald Sitter wrote: >> Every time the bugz vs gitlab schism comes up I eventually tune out wi= th >> 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 us= e >> 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. >=20 > There is policy, and there is reality. Policy is not self-enforcing, an= d > if it attempts to prescribe a reality too different from the actual one= , > it breaks and looks somewhat silly. >=20 > Since we have no way of actually *disabling* the Issues feature in our > GitLab instance, certain projects are inevitably going to start using i= t > despite all the policy we can come up with. Why? Because it's generally= > better for most of the things that most of us care about (it does not > have to better for literally everything to still be a net win) . I don'= t > see anyone really trying to argue otherwise. >=20 > Therefore, I think we need to re-focus the conversation towards "how do= > we migrate to GitLab issues in a coordinated and supported manner." Sure, I suppose, I mean, not this conservation, this conversation was about koko and how it needs crash tracking because quite clearly there's opportunity for crashing. The reality right here right now is that drkonqi only sports bugz support and will not gain gitlab support until at least October. Which is why I said that this is the reality we live in short to mid term. HS --1gjBmo8lAyfj5OKkY61nyGVLJDsksx1P3-- --vIZaAIXgIa7gmD2EmJmN1DEd9NXGga8el Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wsF5BAABCAAjFiEEmUvOVl9TGc6jhe6fuSpfBOyUkSEFAmCRVesFAwAAAAAACgkQuSpfBOyUkSH8 hg/7BdgZlmCD4fqifq783uqW/oP9260g7ph7QSlfzOD6tqy35ywQbCuZwW9kGOeZZU0qfVtNwCMV AIOUmfnRJ4pSnENlxl91UC8hrmHovqIH09098wWh0LwmSaOaMuBocR6M7zOovu7YaRHeNCOtWgxJ J1TEWomuMWAbyIAhf9VS5RFBqTVCh/rcmiL+vEVa+CkeLQz2Slo+VAy1vhoFa2UR/Q9rJZmSkOWQ 6oAngNG56ngZFGJuuc07ZlduS+jR6cXO16sdlElsR/OyTxfxehTR3QjHDCWLA9NZdOg4DQhbGKrS 6DH9i4+xpNyAd8dFGdOYRamANGz4FdfpYFhuLo7KbgCxZDuwHv6PK3GtQMAA9OsT4IB252v3ONqA LiBp4xiOxcFOOx4cLrFEYJ58vu4LOu3sQl/8eVfcTwSxYWa7UHYiFV+c4AD47r8A9Syw+M0Wy17a 04JHQURZF56mlTNegKbXa0Y5HGwkLPTuyj5qN7zm1Eg+E+WLZFiZTnjPbuMmbQ1WwP4wB6Ib0xbL p+RM7MPB/o6eAfIhFzdyH5qA7X7XTXGOsDaXY6a4Lpq/3qlCufr6U3S1jhxMjmx4ib3K+hMbyjlk WxnxGksi34G6Q3w6G0KLy8neYlYsOJfal4zbQhl1MrzbwL1xmYkUeW5F1r98lcwrTfBsE5Is6NQF T9c= =kvjc -----END PGP SIGNATURE----- --vIZaAIXgIa7gmD2EmJmN1DEd9NXGga8el--