Internationalization Working Group Teleconference -- 24 Oct 2019

<addison> trackbot, prepare teleconference

<agendabot> clear agenda

<scribe> scribenick: Bert

Agenda and Minutes

Action Items

<addison> https://www.w3.org/International/track/actions/open

<addison> action-797?

<trackbot> action-797 -- Atsushi Shimono to Start writing weekly summary of new/tracked issues -- due 2019-04-18 -- OPEN

<trackbot> https://www.w3.org/International/track/actions/797

addison: close 797?

<addison> close action-797

<trackbot> Closed action-797.

atsushi: Automate?

r12a: Add to the issues themselves, then it will be accessible to people.

atsushi: I try to follow the email, but...

<r12a> https://lists.w3.org/Archives/Public/public-i18n-core/2019OctDec/0020.html

addison: You'd rather keep the action open?

atsushi: Haven't thought yet about how to work with the new system.

<addison> action-838?

<trackbot> action-838 -- Addison Phillips to Add wai pronunciation docs to radar -- due 2019-10-17 -- OPEN

<trackbot> https://www.w3.org/International/track/actions/838

<addison> close action-838

<trackbot> Closed action-838.

addison: Will do action-839 imminently.
... Need to make a list of open issues.

r12a: ... or set a tag on them, "needs-review".
... A few issues were raised in email and have no github issues.

addison: They are pretty old.
... Making Github issues is more work, though.

Info Share

addison: Need to find a volunteer for that...

RADAR and Active Work Review

<addison> https://github.com/w3c/i18n-activity/projects/1

addison: New review requests. Who can do them?

r12a: Atsushi has more time for i18n now. Able to review devices and sensors?

atsushi: Yes.

r12a: I'll do WAI Pronunciation.

r12 moves those two documents to the column "In review".

What Time is this meeting at?

addison: Europe switches to wintertime this weekend. Do we follow European time?

r12a: WebEx meeting is set to London time. Which next week is same as UTC.

addison: USA changes next week.

If we follow the EU or USA time change the meeting will be an hour later in Asia, either from next week or from the week after.

atsushi has another telcon after this one, but that one shifts, too. He will have i18n at midnight and another meeting at 1am.

(Except next week they may clash, if i18n swithes wih EU time and the other with US time.)

<addison> ACTION: atsushi: find out about potential schedule clash with ttwg and report back if we need to consider a time change

<trackbot> Created ACTION-840 - Find out about potential schedule clash with ttwg and report back if we need to consider a time change [on Atsushi Shimono - due 2019-10-31].

Other people are OK with keeping the time the same in London time.

<addison> ACTION: richard: change the meeting page to ensure it reflects the pending time change

<trackbot> Created ACTION-841 - Change the meeting page to ensure it reflects the pending time change [on Richard Ishida - due 2019-10-31].

r12a: But I need to update the -> meeting info page https://www.w3.org/2017/09/i18n-meeting-info.html

Service Workers issues

r12a: Seems to be urgent, because going to CR.

<r12a> https://lists.w3.org/Archives/Member/member-i18n-core/2019Oct/0023.html

r12a: 519: Seems to work in Safari now, so we close that.

<r12a> https://github.com/w3c/i18n-activity/issues/28

<r12a> https://github.com/w3c/ServiceWorker/issues/1483

r12a: Addison, you looked at this.

addison: [Looking up current spec.]

<addison> https://w3c.github.io/ServiceWorker/v1/#cache-storage-has

addison: Seems they haven't changed anything.
... We are asking them to define string matches.

<addison> https://html.spec.whatwg.org/multipage/infrastructure.html#case-sensitivity-and-string-comparison

addison: I pointed them to HTML as an example.
... (Although I thought HTML was moving these things to the "Infra" spec...)

r12a: Jake Archibald said HTML has case-insensitive as default and that should be enough. But Service Workers is not part of HTML.

addison: "Case-sensitive match" is not enough as a definition.

r12a: You want to continue the discussion with them?

<r12a> https://github.com/w3c/ServiceWorker/issues/1483

addison: Yes, I will. In email, or in the issue?

r12a: In the issue ^^.
... They will see it there, it's their repo.

addison: Do we object to their moving to CR? I suppose not.

r12a: It's less well defined than we'd like, but can be fixed later.
... But don't let them off the hook.

Tracking labels and notification clean-up

<addison> https://lists.w3.org/Archives/Member/member-i18n-core/2019Oct/0016.html

r12a: Philippe (plh) has been doing some work on labels for all repos in W3C.
... But he has difficulty understanding what all labels mean.
... It's true they were named from the i18n perspective.
... So he's asking for better names.
... I'm not sure I like i18n-critical. Not all comments are critical.
... The current i18n-tracking can also be used by others to ask for our attention.

addison: Maybe have just an "i18n" label to get our attention.
... Otherwise seems verbose.

r12a: i18n-requirement, i18n-big-issue...

"i18n-review" may be seen as asking for review. What is good label from POV of other WGs? Maybe we can ask them?

addison: I could write to chairs list.

r12a: I could write to a team list about it first.

<addison> ACTION: richard: write to other HR groups via team list and ask about label patterns in github

<trackbot> Created ACTION-842 - Write to other hr groups via team list and ask about label patterns in github [on Richard Ishida - due 2019-10-31].

Bert: "i18n-wg" for the tracking one?

r12a: How would that work for other Horizontal Groups?
... The autocompletion issue is similar to some others. May need a write-up.

AOB?

r12a: And we need to clean up references to JSON-LD in some places.

- DRAFT -

Internationalization Working Group Teleconference

24 Oct 2019

Attendees

Contents