Meeting minutes
Agenda
Lagally: (goes through the agenda)
Housekeeping
Minutes
Lagally: (goes though the minutes)
minutes approved
New Profile wiki page
Lagally: we now have a separate wiki page for WoT Profile as above
McCool: added a link from the WoT main wiki to this wiki too
Schedule
Lagally: just a reminder
CR draft: End February (4-6 weeks for wrap-up)
2 months review
wide review
PR End May (at the latest)
McCool: we've agreed to ask for wide reviews based on the WD version
Lagally: right
Explainer
PR 362 - Finalize Explainer.md
Lagally: (goes through the "Files changed")
… removed the requirements section
… renamed "Baseline Profile" as "Basic Profile"
… removed the detail on error processing
McCool: ok
… note that there is a specific template for Explainers
… did you see the template?
Lagally: no, just copied the content from another Explainer
McCool: ok
… would suggest we make a resolution after reviews
… e.g., next week
Lagally: yeah, would get group-wide reviews
McCool: looks pretty reasonable to me
Kaz: given there are kind of big changes, would suggest we merge this PR itself now
… then ask people for review
… then if no complaints, we can move ahead
Lagally: ok
McCool: "a set of languages supported by the environments" is actually a big set of languages
Lagally: right
McCool: what about the "Security Considerations"?
Lagally: not much there
… can refer to the section "12. Security Considerations"
McCool: would agree with Kaz
… we can merge this PR itself
Luca: regarding I18N
… we could refactor it
… what if an implementer choose another language?
… local market might want to support additional languages
… we should keep the possibility
McCool: we haven't talked about our models
… someone from the developers can develop a model
… might pick a default language to support
… what would be the human-readable information is another question
… we need to clarify that point as well
Lagally: we might want to add some note
Luca: we should try to keep the requirements as minimum
… what if some developer would use a device with limited resources?
Lagally: think we're on the same page around this point
Kaz: for Explainer, it would be nice to add some supplementary note
… on our original intention for the WoT Profile spec
… then should explain device-specific limitation as described by the WoT Profile spec
McCool: intersection of common runtimes to be supported
… languages are facilitated for human UIs
… not directly impact interoperability issues on the device level
Luca: sounds fair
Lagally: ok
… can we merge this PR then?
Luca: seems there is enough agreement
merged
Wide reviews
Kaz: Security to be mentioned within the first comment as well as the second comment in the Issue 358
Lagally: done
McCool: there is specific procedure on how to handle the GitHub issues for wide reviews
Kaz: if you want, I can give you a tutorial on the procedure again :)
Lagally: will read the guide first, but your help appreciated
Kaz: note that there is a section saying "Common mistakes when making a transition request"
… please read that section even more carefully :)
Lagally: ok
McCool: for example, please be careful about *-needs-resolution label
… you can't use that label yourself
… those labels are intended to be used by the horizontal groups
Lagally: may I ask you for help on Privacy and Security, McCool?
McCool: yeah, there are many issues around Security and Privacy
AOB?
Lagally: what/how to proceed?
… there are 7 open PRs
McCool: related issues to be addressed
Lagally: will clean up the Profile/Architecture wiki too
Kaz: the upper part on each TF should be edited
… but the latter part on the history can be kept asis
Lagally: ok
[adjourned]