On Fri, 16 Sep 2016 10:01:30 -0400
Matthew Miller <mat...@fedoraproject.org> wrote:
> On Thu, Sep 15, 2016 at 05:31:31PM -0700, Adam Williamson wrote:
> > > > So, what if we steer end users away from Bugzilla and
> > > > bug-trackers completely² and to Ask Fedora³ instead? The triage
> > > > team could [...]
> > > But there's no triage team. Adding another layer of indirection
> > > without a dedicated new workforce would likely just divert
> > > resources away from the existing bug fixing process.
> > And before anyone asks - we've tried to have a triage team several
> > times and it has never really worked so far. It's a hard and
> > relatively
> Right, so, this is part of the context for my idea above. There
> *isn't* a triage team, but there *is* a community around Ask Fedora,
> and we could build from that. It wouldn't be the same at all as
> previous efforts to "bugzilla-garden"
Wouldn't it make more sense to have a way for package maintainers to
decide if a bug was local or upstream, and a button they could push to
automatically send it upstream?
Suppose that if a fedora package has an upstream bug tracker, *fedora*
owns a login to their bug tracker. Then, when the maintainer looks at
the bug, he or she decides whether to send it upstream by clicking a
button. If it is sent upstream, the [yet to be designed and built
application] converts it to the appropriate format, logs in to the
upstream bug tracker, and puts it there. And it places a message in
the bug on redhat bugzilla stating that the bug has been sent upstream
for resolution. That leaves the package maintainer dealing only with
local bugs, and new releases. Sort of like abort for packages.
Lots of issues here, but it greatly simplifies the package maintainer's
job. I have 10 bugs today. I look at them and send those for
upstream there, with a click. Leaving me 4. Much more manageable.
But it takes work to have this happen, mostly one time, but with some
Database of upstream logins and passwords has to be built and
Getting a package approved requires a fedora login and password to be
approved, or an exception if it doesn't exist, and entry into the
I don't know how many different kinds of bug trackers there are,
but translating bugzilla to multiple other layouts might be an
issue. Maybe instead, just place a link to the fedora bugzilla on
their bug tracker. Still, this requires programming and maintenance.
Is the trade-off of resources worth it?
devel mailing list -- email@example.com
To unsubscribe send an email to devel-le...@lists.fedoraproject.org