GNOME Bugzilla – Bug 338663
Make the job easier for the docs team
Last modified: 2018-06-16 13:29:10 UTC
From email (from Olav to Shaun with bugmaster cc'ed):
"Saw the thread on d-d-l about docs and bugzilla
You are the docs person. Why bother asking maintainers to create
components, etc? I'm sure if you asked any bugmaster it will be done
(I would). I currently cannot easily only give you the ability to
add/change all products (only if I'd give you all bugmaster rights on
bgo), but otherwise you would have it.
Having a uichange keyword on bugs is broken. Just clone the bug and
file it under the documentation component. Cloning will automatically
depend the docs bug on the original bug.
To have an easy overview of documentation bugs I think having a
browse.cgi special product page that switches components and products
around.. e.g. it shows an overview of all bugs within the 'docs'
component. Currently on browse.cgi you see a list of components. That
should list products instead.
Oh and the various ways to have a docs component is not good. They
should all be named the same ('docs'/ 'documentation'/ ...)."
This bug might need to be split, but I'm going to file it so that we don't forget it. cc'ing shaun so he can clarify any needs.
mysql> select components.name, count(*) from components where components.name like 'doc%' group by components.name;
| name | count(*) |
| doc | 1 |
| docbook | 1 |
| docbook xslt | 1 |
| docklet | 1 |
| docs | 51 |
| document | 1 |
| Document Types | 1 |
| Documentation | 34 |
| Documents | 1 |
9 rows in set (0.01 sec)
Need to rename some of them..
simple-bug-guide has some magic to try to get the component right when you're filing a documentation bug - I think it goes for "docs", with a fallback on the default component.
Some products in bugzilla regroup several apps, and each app has a separate manual. Having a single docs component in these cases leads to problems: see bug 339173.
For aggregate modules (gnome-applets, gnome-utils, etc.), we could encourage them to use something like "docs: gweather". Then we could get a listing with something like:
select components.name from components where components.name
like 'docs: %' or components.name = 'docs';
I tried to work on this in 01/2014 (didn't know about this ticket) but the first conflict to solve was actually "Is a docs component actually about user docs or about developer docs". Ain't easy.
After https://wiki.gnome.org/Initiatives/DevelopmentInfrastructure , GNOME is moving its task tracking from Bugzilla to GitLab at https://gitlab.gnome.org/ as previously announced in https://mail.gnome.org/archives/desktop-devel-list/2018-May/msg00026.html . See https://wiki.gnome.org/GitLab for more information.
Hence closing this ticket as WONTFIX: There are no plans to work on Bugzilla.