Editing specs

MC: was trying to remember what happened with ContentEditable getting dropped off the deliverables

s/ExecCommand/contentEditable

<Yves> http://w3c.github.io/editing/execCommand -> see the warning saying that it won't go past draft status and should be replaced / merged in another spec

MC: if it was because it say "It is predicted that in the future both specs will be replaced by Content Editable and Input Events." And there was not an expectation that execCommand was not going to ever be published.

<tink> Next steps are that we'll leave ExecCommand in the repo with the other Editing specs, and we'll keep it under our wing, but won't add it to the charter because for the moment that feels like paperwork we don't really need to do, to keep the Editing TF work in one central place.

MC: Any other topics to discuss with regards to editing?

LW: not right now.

Companies that need rejoin

MC: we should identify which companies are editing, but haven't joined yet.
... at least... or actively participating.

https://github.com/w3c/webappswg

https://w3c.github.io/webappswg/

<scribe> ACTION: Yves to ping members that are editing, but haven't yet joined.

MC: Apple, Microsoft, Sony mainly

LW: would be nice to have other browser vendor companies also join

XW: we should also ping folks that are attending TPAC
... see if we can get them to join

TPAC

MC: how we with regards to planning the meeting?

<xiaoqian> https://www.w3.org/register/tpac2019/registrants#meeting-93

LW: we had no comments on the prepossessed meeting structure.

MC: the AV all organized, correct?

LW: we have remote dial in capability, multiple whiteboards, and the ability to rearrange tables

MC: we worked the lunch schedule?

LW: yep, that's all sorted out. I sent an email also to the Chairs list to see if any other group wants to meet with us. The deadline for them to respond is 26th of July.
... There are currently around 80 people, right xiaoqian?

XW: there are 44 group participants and around another 40 observers

LW: when we publish our agenda with the breakout sessions, we might see a reduction
... ...in observers
... it's possible that some of the observers might turn into participants when their organizations join

XW: correct
... should we make some suggestion about where observers should sit VS where the participants will sit

?

LW: yes, that's a good suggestion

MC: so it depends on how we organize the seating of the breakout sessions

XW: we should do another status updates before TPAC, as we have done in previous years.

LC: We should ping editors directly beforehand via GitHub, asking if someone will be at TPAC to give an update.

MC: how long do we have?

LW: 2 months ... so we should do that at the beginning of august.
... we could also prod people on any particular sessions they might like to run... or they would like to see run

Check the state of auto-publish

https://github.com/w3c/webappswg/issues

https://github.com/w3c/webappswg/issues/6

Need to check https://github.com/w3c/webappswg/issues/9

https://github.com/w3c/webappswg/issues/6

MC: all specs except UI Events are now on autopublish 🎉

LW: we now have a requirement in charter that specs must have accessibility and internationalization sections. We should check all specs for these sections:

https://github.com/w3c/webappswg/issues/15

MC: Meeting adjourned

"WebApps WG Chairs meeting"

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)

FAILED: s/ExecCommand/contentEditable/
Present: tink marcosc xiaoqian Yves
No ScribeNick specified.  Guessing ScribeNick: marcosc
Inferring Scribes: marcosc

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: yves

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


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