- From: Chris Wilson <cwilso@google.com>
- Date: Tue, 12 Aug 2014 11:50:00 -0700
- To: Marcos Caceres <marcos@marcosc.com>
- Cc: public-openw3c@w3.org, Arthur Barstow <art.barstow@gmail.com>
- Message-ID: <CAJK2wqV8aCFM764hu83x6ADzk8EixBBj-v8i3hpij1++DqFYkA@mail.gmail.com>
Indeed. I spoke with Ian Jacobs about this a week or two ago, and they are working on it, announcing soon I believe. On Aug 12, 2014 11:47 AM, "Marcos Caceres" <marcos@marcosc.com> wrote: > > > > On August 12, 2014 at 2:44:09 PM, Arthur Barstow (art.barstow@gmail.com) > wrote: > > On 8/12/14 1:23 PM, Marcos Caceres wrote: > > > [speaking about "open w3c"...] we probably need to drag in the W3C > team people trying > > to sort this out (I think that's PLH). It would be great to get a status > update on where all > > this is at. I'm worried that we might be doing duplicate work here by > even discussing this > > stuff. > > > > As a reminder, earlier I mentioned this general "/TR graveyard" issue is > > now captured as [Issue-106] for the W3Process group and I still think > > that group is the best venue to discuss it, and I think Consortium staff > > are members of that group. > > > > I don't know if that group has agreed on a `priority` for Issue-106 but > > if you or anyone else considers it a high priority, then please send a > > related e-mail to public-w3process and include the literal "issue-106" > > in the Subject or Body of the email (this will make sure that group's > > issue tracker automagically includes your email in the issue's `paper > > trail`). > > Ok, before we do that tho, it might be good just to get an update from the > W3C. I talked to Jeff on the phone recently and he assured me that the W3C > staff had already done a bunch of work to make this happen. I don't want to > file more bugs, etc. if PLH, Robin, etc. are close to being done. > >
Received on Tuesday, 12 August 2014 18:50:31 UTC