13:03:15 RRSAgent has joined #wot 13:03:19 logging to https://www.w3.org/2023/02/22-wot-irc 13:03:20 meeting: WoT-IG/WG 13:03:40 present+ Kaz_Ashimura, Ege_Korkan, Kunihiko_Toumura, Luca_Barbato, Michael_Koster 13:04:02 present+ Michael_McCool 13:04:09 McCool_ has joined #wot 13:04:37 present+ Daniel_Peintner 13:04:42 rrsagent, make log public 13:04:46 rrsagent, draft minutes 13:04:47 I have made the request to generate https://www.w3.org/2023/02/22-wot-minutes.html kaz 13:04:54 agenda: https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#22_February_2023 13:05:32 chair: McCool 13:05:53 regrets+ Sebastian 13:06:24 dape has joined #wot 13:07:44 matsuda has joined #wot 13:08:40 topic: Minutes 13:08:53 mm: any objections to minutes? 13:08:58 mm: hearing none, published 13:09:08 i|any|-> https://www.w3.org/2023/02/08-wot-minutes.html Feb-8| 13:09:27 mm: We should table the use cases call for now since we should work on the charter 13:09:40 ... since we can use the use cases call 13:10:09 rrsagent, draft minutes 13:10:10 I have made the request to generate https://www.w3.org/2023/02/22-wot-minutes.html kaz 13:10:32 mm: ege can you send a reminder about the marketing call? 13:10:34 present+ Tetsushi_Matsuda, Tomoaki_Mizushima 13:10:55 i/any objec/scribenick: Ege/ 13:10:55 rrsagent, draft minutes 13:10:57 I have made the request to generate https://www.w3.org/2023/02/22-wot-minutes.html kaz 13:11:03 ek: yes, the chairs and staff can be present in that meeting 13:12:08 q+ 13:12:09 topic: Developer meeting 13:12:20 mm: we have talked about having a developer meeting 13:12:44 mm: they should be in the week of march 27 13:13:35 mm: let's do the rest of the discussion in the testing call 13:13:53 q+ 13:14:04 mm: there is also a binding meetup at the JP CG 13:14:27 kaz: I have put it in the agenda. I thought we have two events, one binding meetup and one testing 13:15:19 mm: what is the purpose of the binding meetup? 13:15:40 kaz: chairs and some other participants will handle the topic for japanese stakeholders 13:16:48 mm: I think we should focus on one deliverable 13:17:06 kaz: that is why I want to split them 13:17:57 kaz: we can take the feedback of the JP CG in the form of a report 13:18:18 q? 13:18:20 ack k 13:18:26 q+ 13:18:38 topic: Publication Schedule 13:18:59 mm: we have missed the deadline for charter draft submission 13:19:06 q+ 13:19:45 rrsagent, draft minutes 13:19:47 I have made the request to generate https://www.w3.org/2023/02/22-wot-minutes.html kaz 13:20:08 i/We should table/topic: Planning/ 13:20:10 rrsagent, draft minutes 13:20:11 I have made the request to generate https://www.w3.org/2023/02/22-wot-minutes.html kaz 13:20:50 q+ 13:21:13 ek: there is a PR for update from Scripting API 13:21:19 ... also mine for Binding Templates 13:21:22 ack e 13:21:26 mm: we can change the date 13:21:36 i/there/scribenick: kaz/ 13:21:41 i/we can/scribenick: Ege/ 13:22:17 subtopic: PR 1074 13:22:28 dp: yes so one for review and then the publication date 13:22:38 mm: I would like to merge it, any objections? 13:22:53 subtopic: PR 1075 13:22:58 mm: no conflicts. 13:23:01 ... any objections? 13:23:36 mm: now march 1 is the deadline for the charter draft 13:23:45 mm: we should revisit the profile schedule 13:24:01 i|no con|-> https://github.com/w3c/wot/pull/1075 wot PR 1075 - Update wg-2021-extension-plan.md - charter 13:24:31 i|yes so|-> https://github.com/w3c/wot/pull/1074 wot PR 1074 - Update wg-2021-extension-plan.md Scripting publication| 13:24:41 rrsagent, draft minutes 13:24:42 I have made the request to generate https://www.w3.org/2023/02/22-wot-minutes.html kaz 13:25:02 mm: I will update discovery deadline and bring to the discovery cal 13:25:13 s/ cal/ call/ 13:25:49 https://github.com/w3c/wot/pull/1076 13:25:53 q? 13:26:31 kaz: we should talk with michael lagally for using the UC call 13:26:44 s/we should/BTW, we should/ 13:27:03 s/UC call/UC call and Architecture call for the Charter discussion/ 13:27:22 mm: I want to postpone the minutes review 13:28:12 mm: let's check the minutes quickly because he might have agreed 13:28:23 ... it is not there though but I am sure we discussed it 13:29:23 s/not there though/not clearly recorded within the minutes from yesterday's meeting,/ 13:29:28 q+ 13:29:31 ack k 13:30:22 kaz: yeah, however, the discussion went messy in the end, and that proposal was not explicitly recorded. So I'd suggest we check with 13:30:51 s/with/with Lagally, and also confirm during this call as well around when to have the Charter discussion./ 13:31:00 ack e 13:31:10 i/yeah/scribenick: kaz/ 13:31:19 ek: about the previous topic, could we look at the PR on binding templates 13:31:26 i/scribenick: Ege// 13:31:26 subtopic: PR 1071 13:31:49 s/subtopic: PR 1071// 13:31:50 mm: not hearing any objections and it is an update 13:31:57 i/about/subtopic: PR 1071/ 13:31:58 https://github.com/w3c/wot/pull/1071 13:32:00 merged 13:32:11 topic: Charter Logistics 13:32:43 s/https/-> https/ 13:32:52 mm: we are taking more than last time which was 4h 13:33:03 s/1071/1071 wot PR 1071 - Add Binding Templates to publication plan/ 13:33:21 rrsagent, draft minutes 13:33:22 I have made the request to generate https://www.w3.org/2023/02/22-wot-minutes.html kaz 13:33:28 q? 13:33:59 mm: I do not want to steal UC call 13:34:13 s/call/call given Lagally is not here./ 13:34:16 rrsagent, draft minutes 13:34:17 I have made the request to generate https://www.w3.org/2023/02/22-wot-minutes.html kaz 13:34:23 mm: how about the discovery ? 13:34:28 mm: hearing no objections 13:34:41 s/discovery ?/Discovery call on Feb-27?/ 13:34:50 rrsagent, draft minutes 13:35:21 I have made the request to generate https://www.w3.org/2023/02/22-wot-minutes.html kaz 13:35:28 cris_ has joined #wot 13:36:17 s/because he/because Lagally/ 13:36:27 mm: then we can have a final draft on the march 1st 13:36:40 q+ 13:37:07 i/about the previous/scribenick: ek/ 13:37:12 rrsagent, draft minutes 13:37:13 I have made the request to generate https://www.w3.org/2023/02/22-wot-minutes.html kaz 13:37:19 q+ 13:37:19 ack e 13:37:48 i/about the previous/scribenick: Ege/ 13:37:50 rrsagent, draft minutes 13:37:52 I have made the request to generate https://www.w3.org/2023/02/22-wot-minutes.html kaz 13:38:16 s/Charter Logistics/Charter meeting logistics - revisited/ 13:38:28 q? 13:38:44 ek: should we have the details document ready as well? 13:38:53 mm: maybe but it is not a must 13:38:57 ek: how about the policy? 13:39:05 mm: not for now, it is an internal decision 13:39:13 ack k 13:39:22 mlagally_ has joined #wot 13:39:43 i/BTW/topic: Charter meeting logistics/ 13:40:12 q? 13:40:12 mm: we do not even need work items 13:40:21 mm: it is good for planning purposes 13:40:28 q+ 13:40:34 s|BTW|BTW, you mentioned reusing the UC/Architecture calls for the Charter discussion, but/ 13:40:43 present+ Michael_Lagally 13:41:03 present+ Cristiano_Aguzzi 13:41:09 mm: I believe we have decided to use arch call for charter, are you ok with that? 13:41:12 rrsagent, draft minutes 13:41:13 I have made the request to generate https://www.w3.org/2023/02/22-wot-minutes.html kaz 13:41:32 mm: also we have agreed to use the discovery call for charter discussion 13:41:57 i/I believe/(Lagally joins)/ 13:42:02 ml: if we can use the use cases call for charter discussion 13:42:06 ... it would be better 13:42:15 s/also/also, during this call/ 13:42:19 mm: let's use discovery and if not enough, let's use the use cases 13:42:24 rrsagent, draft minutes 13:42:25 I have made the request to generate https://www.w3.org/2023/02/22-wot-minutes.html kaz 13:42:43 s/the use cases/the use cases call too/ 13:42:54 rrsagent, draft minutes 13:42:55 I have made the request to generate https://www.w3.org/2023/02/22-wot-minutes.html kaz 13:43:01 ml: I am missing the big picture for the next charter 13:43:14 ml: especially for the TD, I see no breaking changes 13:43:30 i/subtopic: PR 1071/topic: Publication Schedule - revisited/ 13:43:31 rrsagent, draft minutes 13:43:33 I have made the request to generate https://www.w3.org/2023/02/22-wot-minutes.html kaz 13:43:45 ml: what is the high level purpose of the work for the next 2-3 years 13:43:57 q+ 13:44:00 ack ml 13:44:21 mm: for td 2.0, we have a long list of waiting features 13:44:26 ack k 13:44:28 kaz: I agree 13:44:33 mm: let's have more discussion tomorrow 13:45:41 mm: I havent had time to think about testing in a while 13:45:46 s/breaking changes/major proposed new features that justify a major version upgrade./ 13:46:09 mm: I have been playing with cameras and found way to cover gaps 13:46:15 i/Lagally joins/kaz: I agree. If the detailed descriptions were ready for the AC review, we could add links to those resources. However, that's not the case. So we should concentrate on the high-level descriptions within the Charter./ 13:46:28 i/If the detailed/scribenick: kaz/ 13:46:36 i/I believe we/scribenick: Ege/ 13:46:39 rrsagent, draft minutes 13:46:41 I have made the request to generate https://www.w3.org/2023/02/22-wot-minutes.html kaz 13:46:58 q+ 13:47:21 topic: Liaisons 13:47:22 mm: any comments about liaisons 13:47:30 kaz: PLH is happy to help us about liaisons 13:48:10 mm: we should invite PLH to review the charter 13:48:31 s/liaisons/liaisons, so we should invite him to the Charter meeting when we talk about liaisons (as he himself also proposed)./ 13:48:48 mm: we should have a reviewable draft 13:49:26 rrsagent, draft minutes 13:49:28 I have made the request to generate https://www.w3.org/2023/02/22-wot-minutes.html kaz 13:50:07 s/reviewable draft/reviewable draft. Let's talk about when to invite PLH tomorrow./ 13:50:17 topic: CG liaison 13:50:22 https://www.w3.org/events/meetings/d29a941e-0bc3-4a2c-abaa-1f711a0ea9a2 13:50:34 i/https/subtopic: WoT CG/ 13:50:58 ek: will have a meetup tomorrow on Feb 23 13:51:19 mm: I cannot attend but please attend if you are interested in the topic 13:51:42 s/23/23. Information available within the calendar above./ 13:51:47 https://github.com/w3c/wot-charter-drafts/pull/41 13:52:25 s/https/-> https/ 13:52:47 s/41/41 wot-charter-drafts PR 41 - Expand WoT CG collaboration 13:52:56 rrsagent, draft minutes 13:52:58 I have made the request to generate https://www.w3.org/2023/02/22-wot-minutes.html kaz 13:53:04 q+ 13:53:17 topic: CG Collab PR 13:53:20 q+ 13:53:25 https://github.com/w3c/wot-charter-drafts/pull/41 13:53:58 mm: the md document is just for us internally, it will not go into the charter 13:54:03 q? 13:54:38 ack k 13:54:48 q+ 13:55:18 ml: There is another PR about the role about the IG 13:56:12 ml: IG collab should not be limited to use cases 13:56:45 i/There/kaz: this PR 41 for the Charter document is fine. However, we still need to elaborate the policy about CG collaboration, and that should be done separately from the Charter work itself./ 13:56:57 s/role about/role of/ 13:57:27 q+ 13:57:33 mm: please use the suggestion button 13:57:44 ack m 13:57:44 ack ml 13:58:30 ek: where should the detailed policy should go? 13:58:44 kaz: we should work on the detailed policy at some point, it can be done after 13:59:11 s/it can be done after/but that's not required now./ 13:59:16 ack e 13:59:18 ack k 13:59:24 rrsagent, draft minutes 13:59:25 I have made the request to generate https://www.w3.org/2023/02/22-wot-minutes.html kaz 13:59:35 mm: we can work on that md document 14:00:01 i/subtopic: WoT CG/ 14:00:03 mm: let's start at 10 past 14:00:11 s/CG liaison/WoT CG collaboration/ 14:00:32 i/9a2/subtopic: Meetup on Feb 23/ 14:00:40 i/tomorrow/scribenick: kaz/ 14:00:48 i/cannot/scribenick: Ege/ 14:01:11 s/topic: CG Collab PR/subtopic: CG collaboration text for the WG Charter/ 14:01:14 rrsagent, draft minutes 14:01:16 I have made the request to generate https://www.w3.org/2023/02/22-wot-minutes.html kaz 14:01:32 i/this PR/scribenick:kaz/ 14:01:42 i/There is another/scribenick: Ege/ 14:01:43 rrsagent, draft minutes 14:01:45 I have made the request to generate https://www.w3.org/2023/02/22-wot-minutes.html kaz 14:02:00 [adjourned] 14:02:02 rrsagent, draft minutes 14:02:03 I have made the request to generate https://www.w3.org/2023/02/22-wot-minutes.html kaz 16:27:18 Zakim has left #wot 18:09:52 kaz has joined #wot