Using Bugzilla. RE: G2 Lessons Learned

[Phillip Shelton <shelton usq edu au>]

Instead of using an existing Bugzilla, could you start your own Bugzilla
tree? (I am guessing that Bugzilla is something like CVS and you have access
to some machine to put it onto.)

Thus using an exising tool to keep the data and an independent Doc Managment
system?

Phill

-----Original Message-----
Subject: Re: G2 Lessons Learned


On Mon, 2002-07-01 at 21:20, Kevin Breit wrote:
> Hey guys,
<snip/>
> ... I propose that we abolish the DocTable and replace it with
> more fine grained tasks in Bugzilla.  We can point a new user to Bugzilla
> and say "Find a project that has open bugs for documentation".  This is,
if
> nothing else, more precise than the DocTable can get (without reinventing
> the wheel again).  It would also serve as a task management system, to
help
> organize each developer, and the entire GDP as a whole.

The main problem with using bugzilla is that not all the apps we write
documentation for are in bugzilla.  Also some of the core GNOME apps
started out as third party apps and with a lot of developer work and
good docs they became a core GNOME app.  I'm mainly thinking of gedit
here.  

<snip/>

I think it makes sense to have an independent documentation management
system.  This way we can track any docs the GDP writes.  The system
would also be a good place to suggest third party apps which need docs. 
We can easily check the status and authors of docs for any apps.  I just
feel bugzilla will not let new contributors see which apps need
documenting, editing, maintaining, etc.

Eric Baudais
_______________________________________________
gnome-doc-list mailing list
gnome-doc-list gnome org
http://mail.gnome.org/mailman/listinfo/gnome-doc-list