The Problem: many bugs filed for openSUSE go to the screening-team by default and often remain there for weeks, so that developers (who would be interested in analyzing or fixing these bugs) do not learn about them. However, the screening process is a hard one
The Idea: build tools that facilitates getting bugs to the right people.
1) a tool with a DB of which files belong to which package, which package is built from which srcpkg which in turn can be used with the existing osc maintainer tool or my http://aw.lsmod.de/cgi-bin/public/opensusemaintainer/MozillaFirefox
Data can be sourced from /mounts/dist/full/full-head-x86_64/ARCHIVES.gz
1b) optional: some tool to access ChangeLog entries of packages in Factory or maintenance-updates to better track down regressions
2) an addition to the above that scans the bugzilla text for pathnames or packagenames and finds the best assignees
3) a tool (as part of OBS?) where interested people can register and unregister to be notified about bugs in certain packages or whole devel-projects.
This project is part of:
Hack Week 11
Activity
Comments
-
about 11 years ago by bmwiedemann | Reply
old relevant project: https://hackweek.suse.com/projects/77 http://git.suse.de/?p=yac/suserevdepfinder.git;a=tree
-
-
Similar Projects
Bugzilla goes AI - Phase 1 by nwalter
Description
This project, Bugzilla goes AI, aims to boost developer productivity by creating an autonomous AI bug agent during Hackweek. The primary goal is to reduce the time employees spend triaging bugs by integrating Ollama to summarize issues, recommend next steps, and push focused daily reports to a Web Interface.
Goals
To reduce employee time spent on Bugzilla by implementing an AI tool that triages and summarizes bug reports, providing actionable recommendations to the team via Web Interface.
Project Charter
https://docs.google.com/document/d/1HbAvgrg8T3pd1FIx74nEfCObCljpO77zz5In_Jpw4as/edit?usp=sharing## Description