Re: Documentation bugs

[Aaron Weber <aaron ximian com>]

One idea:    In the XImian bugzilla we have a "documentation" keyword, used to indicate that a particular bug is going to change something that needs to be reflected in documentation. We don't really use it much, but it's there...

I do agree with John, however, that leaving the documentation issues in with their individual apps makes sense. It might be more helpful just to make more use of default CC or assignment to the doc maintainers or authors (i.e. all bugs filed under evolution -->User documentation are automatically assigned to me, maybe doc bugs could be assigned by default to "gnome-doc-maintainers" or some such?)

a.

On Thu, 2003-02-13 at 14:22, John Fleck wrote:
> On Thu, 2003-02-13 at 11:57, Andrew Sobala wrote:
> > Bugs about documentation get filed in bugzilla (by users). In
> > control-center, they get put in the "docs" component - which isn't
> > terribly useful, since the doc team doesn't (AFAICT) look at it.
> > 
> > Would a documentation product be worth it? Has this idea been thrashed
> > to death in the past? To a certain extent, even if not terribly useful
> > to the doc team, it might be nice to have it so we can clear
> > documentation bugs into it (since most maintainers can't do anything
> > about doc bugs anyway).
>
> I think it's best leaving them where they are, with individual apps. The
> app maintainer should be doing the necessary cc'ing and flogging to make
> sure the appropriate doc writer is aware of the bug. If there isn't
> communication between maintainer and docs person we have bigger
> problems.
>
> Cheers,
> John