W3C home > Mailing lists > Public > public-script-coord@w3.org > April to June 2013

Re: Coordination (was: ES6 Modules)

From: Alex Russell <slightlyoff@google.com>
Date: Fri, 12 Apr 2013 15:41:52 +0100
Message-ID: <CANr5HFUYAo-q7Q_gPB4W=fA7gKJy5ayb0d54nOfotiu6fBho8w@mail.gmail.com>
To: Rick Waldron <waldron.rick@gmail.com>
Cc: Robin Berjon <robin@w3.org>, Brendan Eich <brendan@mozilla.com>, "public-script-coord@w3.org" <public-script-coord@w3.org>, Erik Arvidsson <erik.arvidsson@gmail.com>, es-discuss <es-discuss@mozilla.org>
On Friday, April 12, 2013, Rick Waldron wrote:

> On Fri, Apr 12, 2013 at 8:10 AM, Alex Russell <slightlyoff@google.com<javascript:_e({}, 'cvml', 'slightlyoff@google.com');>
> > wrote:
>> On Thu, Apr 11, 2013 at 1:51 PM, Robin Berjon <robin@w3.org<javascript:_e({}, 'cvml', 'robin@w3.org');>
>> > wrote:
>>> On 09/04/2013 16:51 , Brendan Eich wrote:
>>>> First, this cuts both ways. Do you really want to get into the times
>>>> even in the modern era, even in the last three years, when a W3C/WHATWG
>>>> (the two are diverging again) piece of spec-work was done without
>>>> consulting with es-discuss or any such group, resulting in a less than
>>>> ideal JS API? I am not going to throw that stone, it's not my point. I'm
>>>> asking you to refrain as well.
>>> It most certainly cuts both ways. What I'd be interested in though is if
>>> there's anything we can do to make it not cut at all.
>>> You mention reviewing JS APIs; we're working on quite a few of those 
>>> and we really want all the feedback we can get.
>>> Is there a simple, lightweight process that would ensure everyone's
>>> aware of ongoing work?
>> From the DOM side, I don't know that there's enough F2F contact to say
>> that "DOM authors need to be aware of X" from the TC39 side will ever fly
>> without some big checkbox in their lifecycle that says "has been reviewed
>> for idomatic API practice [yes|no]".
>> From the TC39 side, it wouldn't be hard to have a quick breifing at the
>> front of every-other meeting to bring people up to date on the specs that
>> are going through the process, need eyes, etc. No review in the meeting,
>> but just a heads up that now's the time to weigh in on X, Y, and Z.
> The "DOM side" should all be subscribed to es-discuss and read it on a
> regular basis.

I think that's totally fair and something the W3C needs to get people to do
more reflexively than is done today. Indeed, I'd be shocked if most of the
folks who are designing DOM APIs are subscribed today.

> Additionally, our f2f meeting notes are a great way for them to keep up to
> date, as well as providing a good jump off for questions and concerns.
> Rick
Received on Friday, 12 April 2013 14:42:20 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:12 UTC