[Bug 1956412] Re: crash reports don't go to proper dev team

[erik flister]

why would you say you won't fix this?  it would be easy to implement
systems and policies for ubuntu modders and upstream teams to
coordinate.  at minimum, give upstream access to the crash reports,
issue trackers, etc.

it doesn't take manpower, you don't have to test.  all you have to do is
forward by default, or at least provide access.  if upstream wants to
ignore the forwards, that's on them.  don't ruin it for everyone by
assuming you have to accommodate the least cooperative teams.

i doubt that the vast majority of reports have to do with ubuntu mods
anyway -- they almost all belong upstream.  the majority case is the
case you should design for.

it is a huge shame to take your users' reports and efforts in reporting
issues, and let them go to waste.  the spirit of oss is a partnership
with users, upstream teams, and not wasting anyone's contributions and
efforts.

as an example please note the crash i reported regarding gnome-remote-
desktop.  where did it go?  how do we find it?  it had nothing to do
with any ubuntu mod.  how do i get it to that upstream gnome team?  how
do we give them access to the system holding it?

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1956412

Title:
  crash reports don't go to proper dev team

Status in apport package in Ubuntu:
  Won't Fix

Bug description:
  i'm on 21.10.  i was reporting a crash to a gnome dev team and they informed me that the crash report dialog that submits coredumps, etc. never makes it to the actual responsible party.
  https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/issues/80#note_1346891

  you need a process that forwards these to the proper team

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1956412/+subscriptions