W3C home > Mailing lists > Public > public-webrtc-editors@w3.org > July 2015

Re: Mistake (mine) when doing priority API PR management

From: Cullen Jennings (fluffy) <fluffy@cisco.com>
Date: Fri, 31 Jul 2015 00:54:19 +0000
To: Harald Tveit Alvestrand <harald@alvestrand.no>
CC: "webrtc-editors@alvestrand.no" <webrtc-editors@alvestrand.no>, "Peter Thatcher" <pthatcher@google.com>
Message-ID: <B48D883F-9C0B-4982-B688-CEC8FCEA3939@cisco.com>

I'm glad this is getting straighten out.. But I'm less worried about this particular thing and more on the general way decisions are made. I think that any time the chairs make a consensus decision, they should send a clear email to the list on a new thread that says what they decided. I never got any notification about this and only found it 2 weeks later when I was trying to figure out why my PR had not been merged yet. 

> On Jul 30, 2015, at 3:04 AM, Harald Alvestrand <harald@alvestrand.no> wrote:
> Hi,
> in conversation with Cullen and Peter in Prague, it turns out I made a
> stupid mistake when picking PRs to merge over the priority API.
> The criterion I used to pick was the list consensus that people wanted a
> "modify all settings" API, not a "change this attribute" API to the
> RTPsender. This part was OK.
> But I completely missed the fact that  Cullen's PR contained all the
> text that defined our four levels of priority and what they should mean
> (including an enum for them), and that Peter's PR contained a simple
> integer - which is *not* consistent with previous discussions.
> Peter promised at the Friday get-together Dan and I had with him to put
> togheter a PR that would make the Right THing happen.
> Mea culpa.
> Harald
> -- 
> Surveillance is pervasive. Go Dark.
Received on Friday, 31 July 2015 00:54:59 UTC

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