Re: Doc team related stuff in Bugzilla

[Shaun McCance <shaunm gnome org>]

On Sat, 2014-01-25 at 08:19 +0100, Andre Klapper wrote:
> On Thu, 2014-01-23 at 16:44 +0000, Ekaterina Gerasimova wrote:
> > On 23 January 2014 16:35, Andre Klapper <ak-47 gmx net> wrote:
> > > Yo.
> > >
> > > It's hackfest time so I tried to come up with half-useful Bugzilla
> > > queries (though six different component names, Bugzilla's technical
> > > inabilities, our 63 ways to tag something as docs related, plus devel
> > > vs. user docs don't make it easy).
> >
> > I think working on reducing that number would be a good goal for the
> > hackfest. I have found that our oodles of different ways to mark docs
> > bugs as docs is quite confusing for newcomers. Sindhu did a good job
> > of triaging some of the bugs last year, but I think we should make a
> > push to keep them a bit more under control in general.
>
> If we tried to make a Bugzilla query for documentation components easier
> (ignoring the "documentation" keyword), a first step might be to reduce
> the number of different names for the same component.
>
> Below is a quick and dirty list.
> - need to remove those projects where GNOME documentation team does 
>   not maintain the documentation instead of the project developers
>   (sounds like a candidate for quick Etherpad editing at Hackfest)
> - need to remove projects which are dead / unmaintained because we
>   don't care (I might have a script somewhere left for that I think)
> - need guidelines for project maintainers on component naming (though
>   they might be ignored of course) as maintainers can create
>   components themselves in our Bugzilla setup
> - wondering whether something like "Dev Docs" vs "User Docs" might 
>   make sense (but that would mean a large renaming, plus people might
>   search for the term "Doc..." in the component list?)

I gave up trying to standardize bugzilla docs component names a long
time ago, and instead decided to just use components that have a default
assignee or default QA contact of gnome-user-docs-maint gnome bugs or
gnome-devel-docs-maint gnome bugs 

--
Shaun