<scribe> scribe: chaals

<scribe> scribe: chaals

milestone progress

Milestone Progress: still the same 17 open.

CMN: Anyone think they will miss their milestones?

SOH: I should be fine.

CMN: Believe I will, but that might mean working on the weekend.

XW: Have a PR for #227, will get the other one this week...

SD: Looked at #194, would like some more feedback on what others think. Made a small testcase where you can see how browsers behave.
... it would help me to get some opinions. This one should make it, but not sure I will get my other one done.

<shwetank> https://github.com/w3c/html/issues/194

SM: Have to wrap up a patch, to wrap up one. Have been looking at image changes in wwg, #1101
... have not spent too much time on this.
... so hope to get #906 in. #1101 unlikely
... I don't know what #564 wants.

CMN: I will have a look...

SM: Wait, I get it now...
... needs testing.

CMN: [bumps milestone to WD 3]

LJW: That is the last milestone before we request wide review...

CUstom elements

CMN: Spoke to Bruce last Friday, we started triaging custom elements stuff. It's listed for that mmilestone although a couple of simple things should manage to get into this one with luck

LJW: Are editors familiar with Wide review?

Wide review and the road to Rec

LJW: We send the spec after April milestone asking for review - in particular Horizontal groups like accessibility, i18n, TAG, etc, plus the rest of W3C and the universe.
... will be out for 4 weeks, we need to follow up issues raised that matter to groups. That is a pre-requisite for Candidate Rec. We are hopng to get there mid-late May.
... From there we can only make editorial changes, and we need to put together the implementation report - show each feature introduced has implementations or we are justified in removing it.
... and from there it goes to Proposed Recommendation, the W3C members advise the director about the spec, and then to Rec, all things being great.

CMN: Are we going to branch when we are in CR, or wait until PR?

So, please get all significant changes in by April milestone.

face to face

CMN: anyone confirmed as attending or not?

SOH: Definitely not

CMN: :(

SD: I may have a commitment, if I can get out of it I will make it.

CMN: Will be there

LJW: Expect to be there.

HTML URLs and multipage

SM: Microsoft refer people to the HTML sppec, and in changing the /TR/html* things, their links got broken.
... because multipage made new filenames for e.g. ../semantics-*.html
... W3C could fix this by redirecting with 301s as required.

CMN: Agree, and agree that playing with symlinks is a bad idea...

<scribe> ACTION: CMN talk to tripu

<xiaoqian> https://github.com/w3c/html-tools

So another thing I noticed is that at some point, the multipage was not picking up the first chapter of the semantics stuff.

i.e. /TR/semantics.html is empty, where it should include the HTML element...

SM: Can take a look...

<xiaoqian> https://github.com/w3c/html/tree/gh-pages

http://w3c.github.io/html/semantics.html#semantics

(The content is in the WD...)

XW: I will follow up...

<scribe> Meeting: HTML

This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: s/^^//
Present: xiaoqian Scott_O chaals sangwhan shwetank Léonie
Found Scribe: chaals
Inferring ScribeNick: chaals
Found Scribe: chaals
Inferring ScribeNick: chaals

WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

People with action items: cmn talk

WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)