Re: bridge between Github and public-audio list suspended (Was: [web-audio-api] (OscillatorTypes): Oscillator types are not defined (#104))

On Mon, Oct 28, 2013 at 3:18 PM, Olivier Thereaux <
Olivier.Thereaux@bbc.co.uk> wrote:

> All,
>
> In the past few days, we have seen the bridge between our GitHub
> repositories and this mailing-list misused in a number of ways:
>
> * Replies to the mailing-list without any kind of signature, which would
> therefore appear as coming from, and being authored by the WG. e.g:
> https://github.com/WebAudio/web-audio-api/issues/104#issuecomment-27260032


Ooops.


>
>
> * Spam - see
> https://github.com/WebAudio/web-audio-api/issues/104#issuecomment-27174608
>
> These are very difficult to avoid, and in my opinion neither spam nor
> unwillingly anonymised contributions are acceptable. As a result, I have
> suspended notifications to this mailing-list address of activity on the
> WebAudio repositories.
>

+1


>
> I have contacted GitHub, in hope that they may know a better way around
> the problem. In the meantime, I strongly suggest that members and
> participants of this WG go and create an account on Github, and watch our
> repositories over at https://github.com/WebAudio
>
>
So, if we want to discuss issues they should be done using the issue
tracker on github? Or this mailing list?

I'm a bit confused now on the exact process.

Ray


> If for some reason you are unable or unwilling to do so, please get in
> touch and we will look into the situation. I understand that the need for
> W3C participant to create and use an account on a separate, commercial
> platform may be disturbing to some. I hope we can continue using what
> generally seems to be a useful tool.
>
> Best,
> Olivier
>
>
> On 28 Oct 2013, at 21:45, W3C Audio Working Group Notifications <
> notifications@github.com> wrote:
>
> > On Wed, Sep 11, 2013 at 7:29 AM, Olivier Thereaux
> > <notifications@github.com>wrote:
> >
> > > Original comment <
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=17366#0>by Ralph Giles on
> W3C Bugzilla. Mon, 12 Aug 2013 20:44:31 GMT
> > >
> > > I noticed that Chrome's implementation has a number of oddities, like
> > > ducking the square wave to avoid clipping, and the triangle wave
> starting
> > > at a different phase than the others.
> > >
> >
> > Could we simplify this and say that all of the waveforms are odd
> functions?
> > All of the waveforms are currently odd functions except the triangle
> wave,
> > which is defined to be even in Chrome.
>
>
>
>
>
> -----------------------------
> 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.
> -----------------------------
>
>