W3C home > Mailing lists > Public > public-browser-tools-testing@w3.org > January to March 2013

Re: Use of W3 Bugzilla on WebDriver Spec - Should we?

From: Simon Stewart <simon.m.stewart@gmail.com>
Date: Tue, 29 Jan 2013 09:34:56 +0000
Message-ID: <CAOrAhYGaprRz7P-yoiOAvNYTT2yw1xKg0HnuLnCLiM9=qQCHXQ@mail.gmail.com>
To: David Burns <dburns@mozilla.com>
Cc: public-browser-tools-testing <public-browser-tools-testing@w3.org>

The W3C bugzilla seems like a good idea as the hg repo is hosted there. One
thing to consider is who we're expecting to see bug reports and patches to
the specs/tests from. If it's browser vendors alone, then this will be
fine. If we're thinking of community involvement, then it might also be
good to allow patches/bugs to be reported on a site such as Google Code,
BitBucket or even GitHub (though the lack of mercurial there doesn't weigh
in its favour)


On Mon, Jan 28, 2013 at 11:20 AM, David Burns <dburns@mozilla.com> wrote:

> Hi,
> I have been wondering if we should start using the W3 Bugzilla to keep
> track of outstanding tasks. At the moment a lot of the todos for the spec
> are either written into the spec or on notes either Simon and I have or
> just in our heads.
> I am proposing we setup a component for WebDriver so that we can keep
> track of outstanding issues with the spec. This would bring us in line with
> how a number of the other specs do things. It will also mean that if people
> are interested in what we are doing they can use bugzilla to subscribe to
> that component and any changes to those bugs.
> We can also get bugs to send emails to the mailing list, like other specs
> do, when things change. This means that we are hopefully increasing the
> visibility of changes to all that might be concerned and if people have any
> concerns that we are just keeping things in our head we can hopefully
> alleviate them.
> Thoughts?
> David
Received on Tuesday, 29 January 2013 09:35:23 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 12 February 2015 15:39:01 UTC