On Wed, Jun 15, 2016 at 10:13 AM, Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote: > > > On Tue, Jun 14, 2016 at 1:41 PM, Josh Boyer <jwboyer@xxxxxxxxxxxxxxxxx> > wrot:e >> >> How do you plan on addressing the problem reporting issue? In your >> example, the Inkscape package will still exist in RPM form for other >> Editions. That means there are potentially two versions of Inkscape, >> one from upstream and one packaged in Fedora. How do you ensure >> problem reports are routed to the correct issue tracker? > > > Something Flatpak, or any other packaging method, could make easier for > developers and users is integrating an in-app bug reporting mechanism. That is a thing that could be done. > The packager chooses which (and possibly more than one) bug tracking system > to use and bakes that into the application in a way that abstracts the user > from this very long standing mess. So upstream packaged applications would > behind the scene submit the bug to the upstream preferred bug reporting > system; and Fedora packages applications to RHBZ or upstream or both. One of the issues with this idea is scale. It requires app developers to do this. Not every app developer will do this. Which means the distributions are still going to have to solve this problem. josh -- Fedora Marketing mailing list marketing@xxxxxxxxxxxxxxxxxxxxxxx https://lists.fedoraproject.org/admin/lists/marketing@xxxxxxxxxxxxxxxxxxxxxxx
