Stasiek Michalski
The discussion identified two problems that we'd like to address:
* I'm new to openSUSE and I want to help. What are the packages that currently need help and how can I start contributing? There is currently not a single source of truth for such information.
This needs improvements to Bugzilla. Bugzilla needs to know OBS's packages, and allow to map one with the other. A thing similar to this (although connected to koji and not OBS afaik) is already a part of RH Bugzilla.
Definitely, the Fedora/RHEL Bugzilla handles this far better, where you can explicitly search for bugs assigned to a specific package. Currently we only assign bugs automatically to a maintainer if they've set themselves as a bugowner (otherwise it is afaik done manually). This has the huge disadvantage, that if the maintainer changes, then bugs don't get re-assigned and you cannot really find out which bugs are reported against which package.
- Neal mentioned that Fedora is trying to address the issue with some sort of Developer dashboard that displays over the health of packages where users can identify packages in a bad shape.
Hm, I don't think that the new packager dashboard is really useful for that. It is rather intended to provide an overview of the state of each of your packages to individual maintainers.
There was somebody implementing release-monitoring support into OBS, but idk where that ended up.
I have looked into that a bit last year, but unfortunately did not find
the time to really finish that work. It would mostly require to extend
the-new-hotness (https://github.com/fedora-infra/the-new-hotness) to
notify maintainers or (as the second iteration) create submitrequests on
OBS. If anyone wants to tackle this, feel free to reach out to me, as I
unfortunately won't have time to finish this in the foreseeable future.
Cheers,
Dan
--
Dan Čermák