Hey, guys
Each company has its development policy and way of doing things, but wouldn't an application to automatically send problem reports be interesting for novice and experienced openSuse users, considering that some Distros already have this method, like Fedora?
We would certainly have a wider range of problem reports and, consequently, more solutions. What do you think?
https://imgur.com/Ff5RcZU
ABRT (the solution Fedora uses) requires some tweaking to adopt for openSUSE/SLE. We could certainly benefit from it, but it would require SLE buy-in. @lkocman, what do you think?
I'll raise the question with Architects.
Just to mention: One thing which is fundamentally different from ABRT/RH is that we do not have component per srpm in Bugzilla, and dumping a lot of tickets there would create a huge overhead for our triaging team.
Exactly
I have no objection from a technical perspective but I think the process requirements of doing this are likely to make it unfeasible
One possibility would be to have "searching if such bug has been already reported / fixed" before it's actually reported. Duplicit bugreports happen, but just adding someone to Cc with "happens to x too" would be better.
@locilka I agree that's basically how abrt works.
Metadata Update from @lkocman: - Custom field SUSE Jira - SUSE Linux Enterprise adjusted to https://jira.suse.com/browse/PED-3803
I think it would look really nice if we'd have integration with cockpit which would then show you all related bugs to your system on the landing page when you login to the host management inteface.
Similarly to https://scc.suse.com/landing
Cockpit is a local (although remote) 1:1 system management tool for a single machine. If you connect "your" bugs (your Bugzilla account) with such single instance of Cockpit, then it stops to be a multi-user system, because "your" account would be visible to any "root" and thus it's good only for openSUSE. I've reported many bugs that were often not connected with a single system, but they are still under my account. Those systems are long gone.
PM mentioned that we have to be mindful of these: a) Air-gaped scenarios b) on/off switch c) transparancy
Login to comment on this ticket.