<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:todventtu@suomi24.fi" title="Buovjaga <todventtu@suomi24.fi>"> <span class="fn">Buovjaga</span></a>
</span> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WONTFIX - Migration to GitLab or a similar service"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=126818">bug 126818</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>REOPENED
</td>
<td>RESOLVED
</td>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>---
</td>
<td>WONTFIX
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WONTFIX - Migration to GitLab or a similar service"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=126818#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WONTFIX - Migration to GitLab or a similar service"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=126818">bug 126818</a>
from <span class="vcard"><a class="email" href="mailto:todventtu@suomi24.fi" title="Buovjaga <todventtu@suomi24.fi>"> <span class="fn">Buovjaga</span></a>
</span></b>
<pre>This is not a single opinion.
For examples of other voices, from a recent discussion on kde-community mailing
list:
The lead developer of Krita commenting on GitLab:
<a href="https://mail.kde.org/pipermail/kde-community/2019q3/005446.html">https://mail.kde.org/pipermail/kde-community/2019q3/005446.html</a>
"for tracking bug reports it is an _inferior_ tool because it lacks the
abilities needed to work with large numbers of reports for complex
applications. It doesn't even have components -- as far as I can tell,
everything needs to do be done with just one thing: labels."
Krita dev doing a more finegrained comparison:
<a href="https://mail.kde.org/pipermail/kde-community/2019q3/005450.html">https://mail.kde.org/pipermail/kde-community/2019q3/005450.html</a>
"So, what gitlab issues have over bugzilla is a rich text editor and a
confidentiality flag. What bugzilla has over gitlab issues is reasonable solid
set of features that help actually tracking and managing the bug report. It's
not that I'm a huge bugzilla fan, it could be much better, but I need those
features.
The reason for that is that gitlab's issues feature seems to have been designed
for the way smaller, internal teams work inside a company, where they would
create their own issues during development, or create issues for tasks they
receive from their product owners. It's not designed for receiving thousands of
end-user reports a year. It's not designed to be the public face of a project."
Kate editor dev:
<a href="https://mail.kde.org/pipermail/kde-community/2019q3/005444.html">https://mail.kde.org/pipermail/kde-community/2019q3/005444.html</a>
"In our company we multiple times reviewed bug trackers (for migrating from
Bugzilla), but none actually had a good enough feature set to be considered,
beside perhaps Jira (which is non-free/open)."
Another Kate dev:
<a href="https://mail.kde.org/pipermail/kde-community/2019q3/005460.html">https://mail.kde.org/pipermail/kde-community/2019q3/005460.html</a>
"but I have to agree Boud and Christoph here. We currently use the Gitlab
tracker at work, for a quite
small project, and it doesn't even really scale to that. I think for a
free-time kind of project one person does with 200 users and 15 issues
reported over 2 years it's fine, but to me that seems to be the use case
it targets."
Bugzilla is not lacking a Kanban style board, it has had an extension for it
for years and will ship Kanban as core feature in version 6 - yet, LibreOffice
development is not done in a way that Kanban boards would be useful. I have
once asked about it and the engineering steering committee decided it would be
useless.
Regarding Tags / labels, these are just metadata, which Bugzilla offers plenty.
GitLab/-Hub do not offer an advanced search that would allow making proper use
of such metadata. Closest to labels, in Bugzilla we have keywords, whiteboard
(for free text input) and flags (which we do not use).
Search is in fact the most concrete part, where the inferiority of GitLab/-Hub
can be seen. We need the granular search of Bugzilla in order to do quality
assurance and development in a sane way.
Related issues are offered when filing a new report.
In addition to the revamp of Bugzilla (where much of the UX work is in fact
done by a volunteer), Mozilla is developing a system leveraging machine
learning, which will allow for a certain degree of automated bug triage:
<a href="https://github.com/mozilla/bugbug">https://github.com/mozilla/bugbug</a>
If you want to see a preview of how BZ 6 looks like, you can visit Mozilla's
BZ: <a href="https://bugzilla.mozilla.org/">https://bugzilla.mozilla.org/</a></pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>