Warning:
This wiki has been archived and is now read-only.

EditorsShenzhen

From HTML WG Wiki
Jump to: navigation, search

Agenda for the Editors' Meeting in Shenzhen

(In no particular order.)

The plan to end the bugs

How do we squash the last CR bugs?

A big bug merger?

Mike and Robin have been talking amongst themselves and with Ian. There is interest in having a single bug product for both the HTML WG and the WHAT WG (tentatively called "HTML"). The reason is that checking on both sides is extra work for everyone, and things are getting either duplicated or lost. Users are confused. Everyone loses.

  • What do people think?
    • SteveF: I am skeptical, but see the utility of it.
  • If we go ahead, how do we handle dissent?
    • SteveF: I am assuming you mean between whatwg/W3C, I suggest that if any editor is in disagreement with a bug resolution, they can clone the bug and resolve as per the process for their respective group. Same goes for any commenter(as per process).
  • What is the best way to make it happen?
    • SteveF: get agreement and do it.
  • What are our requirements?
    • SteveF: all bugs start off as assigned to dave@null.org any editor free to take. If taken and no work done on the bug for a period of time (to be determined, say 1 month) then any editor free to take. (thinking about it some more I am actually OK with bugs filed against the whatwg spec being assigned to Ian, but bugs against the w3c html spec should not be auto assigned and w3c editors get first bite at taking, if no one does then Ian can take. [but keeping rule that if someone takes and the bug stagnates, then another editor can work on it]i.e. reduce blocking).

Normative reference issues

We have standing normative references issues with HTML5 that could prevent us getting out of CR. Go through list, see how we handle them.

Shipping Canvas

Make sure we're aligned on the plan to ship, and see how we can help.

The next heartbeats

Is there anything we need to discuss in terms of what gets published next?

WG Agenda

Anything we need to put on the WG's agenda at TPAC?

Update on testing

There has been quite a fair bit of work in the testing area, editors should be aware of it.

#html-editors

We don't seem to use this channel, we have #html-wg for general-purpose stuff and #html-chairs

Post-mortem on "The Great Cleanup of 2013" commit

As Steve noted, the build script seems to have stalled right after this cherry-pick. Also, some notes on a few normative changes that almost slipped in.

Times

Please indicate what times you can make while at TPAC so we can figure out which is best. If you're not coming please say so as well so we know you've replied. Also, if you'd like us to try to set remote participation up please ask. I can't promise we can get an equivalent to the huge Silvia screen we had last time, but I can try to figure something out.

Robin: Sunday, Monday, Tuesday (pretty much any time)

Rik: Sunday, Monday, Tuesday (pretty much any time)

Eliot: Monday, Tuesday, Wednesday, Thursday, Friday (most times)

Ted: Basically only Wednesday, though depending on WebApps & CSS agendas I might be able to sneak out for a bit on Mon/Tue.

Steve: not attending

Silvia: Sunday, am in TTML, Media Capture, HTML, WebRTC WGs, but will make time whenever