- From: Paul Adenot <padenot@mozilla.com>
- Date: Thu, 23 Oct 2014 12:41:43 -0700 (PDT)
- To: Chris Wilson <cwilso@google.com>
- Cc: Joseph Berkovitz <joe@noteflight.com>, Paul Adenot <paul@paul.cx>, Audio WG <public-audio@w3.org>
ok. Paul. ----- Original Message ----- > From: "Chris Wilson" <cwilso@google.com> > To: "Joseph Berkovitz" <joe@noteflight.com> > Cc: "Paul Adenot" <paul@paul.cx>, "Audio WG" <public-audio@w3.org> > Sent: Thursday, October 23, 2014 7:20:11 PM > Subject: Re: "Edit-readiness" of TPAC items > > sure. > > On Thu, Oct 23, 2014 at 10:18 AM, Joseph Berkovitz <joe@noteflight.com> > wrote: > > > Hi Chris, Paul, > > > > There are lots and lots of editorial issues with the spec, as we’ve all > > noted. Many of these are not difficult or contentious. To expedite > > discussion at TPAC, I would like to propose that the two of you go over all > > of the “Editorial/Documentation” issues flagged for TPAC 2014 and label all > > such issues that propose a straightforward and obvious resolution with the > > “Ready for Editing” label. > > > > The meaning of this label at TPAC is that Matt and I will merely ask for > > objections to committing the proposed resolution of each such labeled > > issue. The hope is that generally there won’t be any, and we’ll just move > > on immediately to the next issue. > > > > Of course, for this to work, issues tagged this way need to contain an > > obvious disposition preferably noted in the final comment or few. (And if > > you disagree about the edit-readiness of an issue, that should become > > evident at the meeting :-) > > > > Does this sound OK? > > > > . . . . . ...Joe > > > > *Joe Berkovitz* > > President > > > > *Noteflight LLC* > > Boston, Mass. > > phone: +1 978 314 6271 > > www.noteflight.com > > "Your music, everywhere" > > > > >
Received on Thursday, 23 October 2014 19:42:12 UTC