trackbot, prepare teleconference
<agendabot> clear agenda
<scribe> scribenick: addison
<JcK> WebEx has been badly overloaded this week, and I'm seeing symptoms -- been waiting several minutes for it to actually start
<JcK> What means "phone"? :-( Will give it another minute, then try that.
https://www.w3.org/International/track/actions/open
action-871?
<trackbot> action-871 -- Addison Phillips to Ask css why they didn't use our process to request a pre-cr review -- due 2020-03-26 -- OPEN
<trackbot> https://www.w3.org/International/track/actions/871
close action-871
<trackbot> Closed action-871.
actino-873?
action-873?
<trackbot> action-873 -- Addison Phillips to Create a pr on string-search pointing to find-text issues and the need to resolve or comment on issues and requirements -- due 2020-03-26 -- OPEN
<trackbot> https://www.w3.org/International/track/actions/873
close action-873
<trackbot> Closed action-873.
https://github.com/w3c/string-search/pull/7
https://raw.githack.com/aphillips/string-search/gh-pages/index.html
action-874?
<trackbot> action-874 -- Fuqiao Xue to Ask after the status of dpub's css-priorities doc in reference to our issue 195 -- due 2020-03-26 -- OPEN
<trackbot> https://www.w3.org/International/track/actions/874
xfq: thought this doc should be closed; work should be taken up by new CGs
close action-874
<trackbot> Closed action-874.
https://github.com/w3c/i18n-activity/issues/195
<scribe> ACTION: xfq: refile issue 195 against the new community group after CG is created (depends on epub3 charter)
<trackbot> Created ACTION-878 - Refile issue 195 against the new community group after cg is created (depends on epub3 charter) [on Fuqiao Xue - due 2020-04-02].
action-875?
<trackbot> action-875 -- Atsushi Shimono to Find out actual status of webvtt documents from issue 15 etc. -- due 2020-03-26 -- OPEN
<trackbot> https://www.w3.org/International/track/actions/875
atsushi: sent email to member
list; that spec was developed in CG and trasitioned to the
WG
... so active
close action-875
<trackbot> Closed action-875.
action-876?
<trackbot> action-876 -- Addison Phillips to Research webvtt horizontal review request and contact plh if there appears to be a gap -- due 2020-03-26 -- OPEN
<trackbot> https://www.w3.org/International/track/actions/876
close action-876
<trackbot> Closed action-876.
action-877?
<trackbot> action-877 -- Richard Ishida to Update the webvtt issues with correct labels -- due 2020-03-26 -- OPEN
<trackbot> https://www.w3.org/International/track/actions/877
close action-877
<trackbot> Closed action-877.
<r12a> Rules for Simple Placement of Ruby
richard: florian contacted me saying "should we do something with Rules for Simple Placement of Ruby"
<r12a> https://w3c.github.io/jlreq/docs/simple-ruby/index.html
https://github.com/w3c/i18n-request/projects/1
<r12a> https://w3c.github.io/jlreq/docs/simple-ruby/index.html
richard: this small document is
potentially useful
... doesn't cover ruby in dramatic depth such as JLReq
... jsut the salient bits
... here's one way of doing that
... there have been some editorial comments twice
... one thing I feel strongly about
... section at end
... things I am not sure I agree with
... doesn't fit with overall doc
... was maybe an afterthought?
... there is a lot more to say about ruby and a11y
... good to have written up
... and not add here
... would suggest that when published, publish without section
4 on accessibility
... and maybe make a new doc for that
<atsushi> +1
addison: need to know disposition?
richard: florian recommends that
we publish as a note
... think I agree
... it's nicely done in respec and could have japanese in
it
addison: would want wide review?
richard: suggest we review for next week and decide what next steps should be
<scribe> ACTION: addison: remind WG to review rules for simple placement of ruby for next week's telecon
<trackbot> Created ACTION-879 - Remind wg to review rules for simple placement of ruby for next week's telecon [on Addison Phillips - due 2020-04-02].
atsushi: murata-san is getting
updated requirements from JP point of view, esp.
publishing
... including accessibility
... interviewed many people, gained insight
... support to separate accessibility section
... another point; after publishing (inaudible) PDF doc
... many updated but not motivation to update document
... update just english version for now?
richard: can we change the japanese version anyway?
atsushi: one concern; updating
japanese version would be reverse translation into japanese
doc
... not sure how specifically
richard: little change would be needed? fuqiao already produced interleaved version
atsushi: in discussion of jlreq
group, not supported for combined document
... just english
addison: where would be put removed a11y material?
atsushi: murata/makoto-san doing
research
... such kind of update could be put in that section
... it's on-goign activity
... splitting doc into two
addison: new doc "requirements for ruby accessibility"?
richard: just make a doc for it in the repo
<r12a> https://github.com/w3c/jlreq/issues?q=is%3Aissue+is%3Aopen+label%3Asimple-ruby
<scribe> ACTION: richard: ask florian about splitting the accessibility material from "rules for simple..." in prep for taking doc to Note
<trackbot> Created ACTION-880 - Ask florian about splitting the accessibility material from "rules for simple..." in prep for taking doc to note [on Richard Ishida - due 2020-04-02].
richard: there are open issues at
link
... one practical thing
... if you follow links, the commit history points to wrong doc
and similarly PRs
<scribe> ACTION: richard: set up simple-ruby repo
<trackbot> Created ACTION-881 - Set up simple-ruby repo [on Richard Ishida - due 2020-04-02].
https://lists.w3.org/Archives/Member/member-i18n-core/2020Mar/0004.html
<xfq_> https://github.com/w3c/i18n-activity/issues/8
<xfq_> https://github.com/w3c/webvtt/pull/256/files
<scribe> ACTION: addison: reply to webvtt issue 256 (our issue 8)
<trackbot> Created ACTION-882 - Reply to webvtt issue 256 (our issue 8) [on Addison Phillips - due 2020-04-02].
<xfq_> https://github.com/w3c/i18n-activity/issues/40
<xfq_> https://github.com/w3c/csswg-drafts/issues/4452
<xfq_> https://drafts.csswg.org/css-variables/#custom-property
<xfq_> https://github.com/w3c/i18n-activity/issues/79
addison: can't close 40 pending change to whatwg
<xfq_> https://github.com/w3c/i18n-activity/issues/842
xfq: bert also raised similar
issue
... haven't copied to them
... seems that these two issues can be merged
... raised against different specs
... doing in email in 2015
addison: media streams is published I think?
xfq: not a rec yet, CR currently
<xfq_> https://github.com/w3c/mediacapture-screen-share/issues/135#issuecomment-579713729
<xfq_> ^ Dom's reply
<scribe> ACTION: addison: open issue 79 against media-streams noting that we're just housekeeping the previous issue
<trackbot> Created ACTION-883 - Open issue 79 against media-streams noting that we're just housekeeping the previous issue [on Addison Phillips - due 2020-04-02].
<xfq_> https://github.com/w3c/i18n-activity/issues/189
<r12a> https://github.com/w3c/dwbp/commit/889f7a688145cf441a16e9faaa1936d466117c38
fsasaki: raising awareness comment might help long term?
richard: looking at above
link
... can we close based on that?
<fsasaki> +1
<xfq_> +1
+1
<atsushi> +1
RESOLUTION: close issue 189
<JcK> +1 (trying to fix clearly more effort than it would be worth)
<JcK> I have to leave too... so, next week.
This is scribe.perl Revision: 1.154 of Date: 2018/09/25 16:35:56 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/rules.../Rules for Simple Placement of Ruby/ Succeeded: s/WD currently/CR currently/ Succeeded: s/req/rec/ Default Present: addison, Fuqiao, atsushi, richard, Bert, fsasaki, JcK Present: addison Fuqiao atsushi richard Bert fsasaki JcK Found ScribeNick: addison Inferring Scribes: addison Agenda: https://lists.w3.org/Archives/Member/member-i18n-core/2020Mar/0010.html Found Date: 26 Mar 2020 People with action items: addison remind reply richard wg xfq 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.)[End of scribe.perl diagnostic output]