Maintainership of GNOME Settings | triage examples | howto

[ilikelinux]

Continuing the discussion from Maintainership of GNOME Settings:

@gbsneto

Confusion with the source of bugs: due to the very nature of GNOME Settings - a hub of many, many parts of the desktop - oftentimes people report bugs on our issue tracker that are not actually bugs in Settings’ codebase. Say, for the sake of argument, that Mutter has a certain bug applying the new position of a monitor; this will most likely be reported against Settings, because that’s the user facing part of monitor configuration. These issues need to be moved to the appropriate repository, so that the appropriate people can look at the appropriate part of the codebase.

Recently I started the settings like :

gnome-control-center -v in terminal

to get additional information on what gets on behind the curtains.

If there is a (output) pattern who helps to separate issues, to identify if it belongs to settings or not, it might would help to make a better triage. Mutter has been mentioned, maybe an example with it would be helpful.

Probably there are other simple tools who help with triage? I propose to make the first request here as a wiki,
so members could list tools, patterns or even links to make a fast access to such information. And underneath we discuss if it makes sens to list it.