Re: use some kind of issue tracking tool to manage spec changes?

Hi Glenn and all,

I setup: 
	https://www.w3.org/Bugs/Public/describecomponents.cgi?product=Speech%20API

I took some liberty with it, as you have to create a component when you create the product, so I just did "Speech API" and "Documents of the Speech API Community Group" again.  It also required a default assignee, which right now I set to you Glen :)  I think that's editable without any team access, but if it's not I'll change it to whomever we want.

-M

On Sep 12, 2012, at 11:08 AM, Glen Shires <gshires@google.com> wrote:

> Matt,
> How do we setup "Speech API" as a product under bugzilla, with the description "Documents of the Speech API Community Group" ?
> 
> /Glen Shires
> 
> 
> On Wed, Sep 12, 2012 at 6:53 AM, Deborah Dahl <dahl@conversational-technologies.com> wrote:
> I think bugzilla would also work. I have more experience with Tracker, but I
> know a lot of groups have been satisfied with bugzilla.
> 
> > -----Original Message-----
> > From: Olli Pettay [mailto:Olli.Pettay@helsinki.fi]
> > Sent: Wednesday, September 12, 2012 9:51 AM
> > To: Deborah Dahl
> > Cc: public-speech-api@w3.org
> > Subject: Re: use some kind of issue tracking tool to manage spec changes?
> >
> > On 09/12/2012 03:44 PM, Deborah Dahl wrote:
> > > I think it's hard to follow all the discussion on this list just by
> using the
> > mailing list archive. I propose that we use some sort of tracking/issue
> > > tool. Personally, I think the W3C Tracker tool would be fine.
> > >
> >
> > I agree using a bug tracker for resolving issues could be nice.
> >
> > W3C has bugzilla, which is way more nicer for issue tracking than Tracker,
> and
> > it lets also non-group-members to file bugs.
> > WebApps, HTML, etc use bugzilla.
> > https://www.w3.org/Bugs/Public/
> >
> >
> >
> >
> >
> > -Olli
> 
> 
>

Received on Thursday, 13 September 2012 14:17:56 UTC