W3C home > Mailing lists > Public > public-audio@w3.org > July to September 2013

Re: Proposed: move web audio spec versioning and issues to Github

From: Ehsan Akhgari <ehsan.akhgari@gmail.com>
Date: Thu, 15 Aug 2013 19:45:35 -0400
Message-ID: <CANTur_6GHpOXk6bqn+tEEbkepnqrnLhycFvErdoRO1sVAc95zQ@mail.gmail.com>
To: Chris Wilson <cwilso@google.com>
Cc: Olivier Thereaux <Olivier.Thereaux@bbc.co.uk>, Audio WG <public-audio@w3.org>
As far as I know Github installs GitZilla as a repository hook.  You can
enter the Bugzilla server address and a username/password which has access
to the bugs, and that's it.  See below which summarizes the help screen
that I see for this in Github:

This service hook posts comments on Bugzilla bugs when commit messages
reference a bug by id number.

Bugs are recognised by the following formats, which are case-insensitive:

   - Ticket 123
   - Bug 123
   - Tracker item 123

Multiple bugs can also be specified by separating them with a comma,
apersand, plus or "and":

   - Bug 123, 124 and 125

If the "Integration Branch" option is filled in, only commits to that branch
will result in bugs being modified. This is useful for disabling premature
closing/comments when working on feature branches.

If "Integration Branch" is not set, commits to *all* branches will be
processed. If you only want to update Bugzilla when you push to your "main"
branch: you probably want to set this to "master".

If the central repository option is enabled and there is a "fix",
"close", or "address" before the bug then that bug is closed.

If a commit has already been mentioned in the bug comments when pushed
by another user then a comment isn't made, unless the central repository
option is enabled. In this case only the first line of the commit message
is included in the bug comment.

This hook requires Bugzilla version >= 3.4 to function correctly
and >= 4.0 to be able to close bugs.

Also note that this gives us more than just email notifications, this hook
can close bugs when somebody pushes a fix for them and actually comments on
the bug with a link to the github commit which is really nice.


On Thu, Aug 15, 2013 at 4:23 PM, Chris Wilson <cwilso@google.com> wrote:

> Does GitZilla work with Github, or just with Git?  I think it needs to be
> installed on the git server, does it not?
> On Thu, Aug 15, 2013 at 12:58 PM, Ehsan Akhgari <ehsan.akhgari@gmail.com>wrote:
>> On the issue of Bugzilla integration, I agree that it's very important to
>> keep that working.  GitZilla <http://www.theoldmonk.net/gitzilla/>
>> provides a bridge between github and bugzilla, so it would probably
>> interesting to explore and see if we can use it.
>> Cheers,
>> --
>> Ehsan
>> <http://ehsanakhgari.org/>
>> On Thu, Aug 15, 2013 at 1:43 PM, Olivier Thereaux <
>> Olivier.Thereaux@bbc.co.uk> wrote:
>>> Dear Audio WG participants,
>>> As discussed at our teleconference today [1], we are considering
>>> tweaking the process by which we manage the evolution of the web audio API
>>> specification to be more "patch-based".
>>> [1] http://www.w3.org/2013/08/15-audio-minutes.html
>>> One proposal to help with this evolution is to migrate the versioning of
>>> Web Audio API drafts, as well as issue tracking, to our group's Github
>>> space [2], as is already the case for the web midi spec [3]
>>> [2] https://github.com/WebAudio/
>>> [3] https://github.com/WebAudio/web-midi-api
>>> During our call, I (and others) raised the concern that there is
>>> presently no working bridge between Github and our mailing-list, and that
>>> the current bridge between Bugzilla and our list is very much appreciated.
>>> This should probably not be seen as a showstopper for the change if there
>>> is consensus in the group about migrating to Github for the web audio api -
>>> we would “just” need to make the mail bridge work.
>>> I invite proponents of the move to describe in more detail how the move
>>> would help us better manage the status of issues and their resolution -
>>> something which was raised as an important feature.
>>> Best,
>>> --
>>> Olivier
>>> -----------------------------
>>> http://www.bbc.co.uk
>>> This e-mail (and any attachments) is confidential and
>>> may contain personal views which are not the views of the BBC unless
>>> specifically stated.
>>> If you have received it in
>>> error, please delete it from your system.
>>> Do not use, copy or disclose the
>>> information in any way nor act in reliance on it and notify the sender
>>> immediately.
>>> Please note that the BBC monitors e-mails
>>> sent or received.
>>> Further communication will signify your consent to
>>> this.
>>> -----------------------------
Received on Thursday, 15 August 2013 23:46:43 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:03:23 UTC