[boud]
> Sorry, that's just something you'll have to dig in for yourself. It's not
> worth my time at least to get you started on something like that: it will not
> help me achieve my goals.
I guess it depends on the scope and ability of parallel works to give
back to Krita. KOffice/Calligra was a
> So, proposed alternative solution: We make sure that all projects that
> want a public-facing bug tracker have a product on bugzilla, and that
> they communicate that as the only bug tracker to users for the time being.
> Would that work?
Probably not.
1. As Nate points out, the bugzilla UX isn
Ok, lots of email in the last few hours, lets recap a bit.
1. "Top" projects don't like GitLab issues because they are too
simple. Can we try to make a comprehensive list of issues on a pad
somewhere? Sa far, I see:
1.1 It doesn't allow custom combo boxes like BZ/RedMine which then
forces manual a
chlab) or for longstanding KDE related apps whose maintainer moved
on and someone else wants to share some of the maintenance burden with
us to spread the costs (kdiff3)). So, no, from within, there is no
such proofs, but there is a lot of them in the larger ecosystem.
On Thu, 4 Jul 2019 at 17:
