Morn.
One year ago I brought up "make it easier to find documentation tickets
in Bugzilla" [1] on gnome-doc-list@.
And gave up because it was a mess. But expecting folks (not: reporters
who might not know) to manually set the assignee to default QA contact
of [email protected] or [email protected]
isn't convincing either.
When it comes to developer AND user documentation in Bugzilla's
{Bindings, Core, Platform, Applications} classifications, those products
that have dedicated components show this variety of component names:
* doc (1 product)
* documentation (36)
* Documentation (16)
* docs (22)
* API documentation (1)
* Developer documentation (1)
* user-docs (1)
* user docs (1)
* User docs (1)
* User documentation (1)
* User Documentation (1)
* User Guide (1)
Does the Doc team know if some products have both dev and user doc
tickets in the very same component?
I'm still wondering whether it makes sense to standardize the name. I'm
happy to push this and bring it upon d-d-l, but this will take a while
and need help, because: MUST identify for each Bugzilla product if the
component is about dev or user docs before renaming. Or if it's both,
someone needs to triage those items first (potentially needs help).
Intentionally not covered in this posting: That Bugzilla keyword called
"documentation".
Cheers,
andre
[1] https://mail.gnome.org/archives/gnome-doc-list/2014-January/msg00003.html
--
Andre Klapper | [email protected]
http://blogs.gnome.org/aklapper/
_______________________________________________
gnome-doc-list mailing list
[email protected]
https://mail.gnome.org/mailman/listinfo/gnome-doc-list
