Re: bugs.kde.org: kio vs frameworks-kio vs kfile etc.
- Date: Tue, 10 Apr 2018 18:26:51 +1200
- From: Ben Cooksley <bcooksley@xxxxxxx>
- Subject: Re: bugs.kde.org: kio vs frameworks-kio vs kfile etc.
On Tue, Apr 10, 2018 at 6:43 AM, Nate Graham <pointedstick@xxxxxxxx> wrote:
> ---- On Mon, 09 Apr 2018 11:35:49 -0700 Elvis Angelaccio<elvis.angelaccio@xxxxxxx> wrote ----
> > Yes.
> > Note that this is not kio-specific: every library in kdelibs that used to
> > have its own bugzilla product should be "merged" with the new
> > frameworks-xxx product (actual bugs still open should be moved, everything
> > else should be closed). As you can guess, it requires a lot of work.
> Right, I was just bringing up KIO because it's a pretty high-profile example.
> > >and then eventually remove kio and kfile?
> > What about old bugs? They should still belong to those products because
> > that's where the bug used to be. So we cannot just delete them.
> Old bugs should be triaged and closed or moved. I've already started doing that. Can we at least hide the old products from view once they're empty?
We can hide old products yes. I did this for a KMyMoney product which
was no longer in use following their shift from KDE 4 to KF5.
> Who has permission to create new components and mark existing products as not accepting new bugs? I'd like to gain those permissions myself, given my bug triaging activities (I'm #2 in closed bugs over the past 365 days: https://bugs.kde.org/weekly-bug-summary.cgi?tops=20&days=365).
Like many things, this is held by Sysadmin.