<scribe> scribe: chaals

WD published...

[Thanks Xiaoqian, team, ...]

WD update

LJW: Thanks for publishing.
... I noticed there were not as many entries in changelog as I expected, only 2...
... can everyone please check that the channgelog is accurately reflecting the work they have done?
... Also, in issue breakdown for the current milestone, most people have a couple of issues, and chaals has a few more.
... maybe we should rebalance that...

[WfM]

CMN: I'll look at them, and see how to reassign by begging someone else to take them, or release, or whatever. There are a couple like Ruby where I have been doing work and expect to get stuff done.

LJW: OK. Anyone else have questions about current milestone?

Milestone progress

LJW: We are 2% done on this milestone.

WHATWG triage

<tink> https://github.com/whatwg/html/pulls?q=is%3Apr+closed%3A%3E2018-06-22

LJW: We made good progress on triaging commits from WHATWG over the last year for compatibility. Doing that more often would be good, so we can keep up more easily.
... suggest we should look through the commits on these calls to get a quick sense.

<tink> https://github.com/whatwg/html/pull/3791

<Scott_O> i'll try to hunt it down

LJW: We should check that one, it is fixinga typo. Can someone look at this?

PA: Wasn't a typo, they seem to have reverted this...

<pati-gallardo> https://github.com/whatwg/html/commit/4e9c466713c4ce8e07a55effaf2a6f4bfd42669c

<tink> https://github.com/whatwg/html/pull/3785

CMN: 3785 not relevant to us.

<Scott_O> will do

labeling commits/PRs

LJW: putting "editorial" in commit title is helpful. Using labels has been patchy, and this is important. So propose we request people actually say "editorial: ..." in comit titles.

[+1]

<Scott_O> agreed.

PA: +1

<xiaoqian_> +1

WHATWG triage

F2F minutes

LJW: A couple of people requested updates to mintes from last week. Xiaoqian, can you please make the changes?

XW: Sure. Please send me requests.

LJW: Will do

programmer3000 issues

XW: PLH as the content in email logs, how should we handle them - re-raise them?

LJW: Think we should have individual issues for each one...

[+1]

<pati-gallardo> [+]

<pati-gallardo> [+1]

XW: Will ask PLH to send us those issues

CMN: What does that mean specifically?

LJW: If you forward it all to me I will create the issues again.

[We'lll get it on team-editors list, and deal with it]

Any other business?

XW: We are the only ones who seems to have a webex problem. Maybe we can just create a new one.

LJW: sure.

CSS going funny

XW: Raised a biekshed issue, Tab is working on it. Seems only a few WG have this problem.

LJW: OK.

[adjourned]

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 Sco/present+ Scott_O/
Succeeded: s/rrsagennt, draft minutes/rrsagent, draft minutes/
Succeeded: s/ott_Ott/ott/
Present: Léonie Scott_O xiaoqian chaals patricia
Regrets: Sangwhan Terence Shwetank
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: 

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.)