12:04:20 RRSAgent has joined #wot 12:04:25 logging to https://www.w3.org/2023/04/26-wot-irc 12:04:35 meeting: WoT-WG/IG 12:05:04 dape has joined #wot 12:05:07 cris_ has joined #wot 12:05:09 present+ Kaz_Ashimura, Sebastian_Kaebisch, Cristiano_Aguzzi, Daniel_Peintner, Ege_Korkan, Kunihiko_Toumura, Michael_McCool, Tomoaki_Mizushima 12:05:39 scribenick: cris_ 12:06:01 topic: guests 12:06:05 seb: no news 12:06:09 topic: minutes 12:06:28 Ege has joined #wot 12:06:31 seb: sadly Lagally mentioned that he cannot act anymore as TF lead 12:06:41 ... then we discussed cancellations 12:06:53 ... and scripting API publication plan 12:07:20 i|sadly|-> https://www.w3.org/2023/04/19-wot-minutes.html Arp-19| 12:07:20 ... TPAC, use cases, and chart discussion 12:07:37 ... questionnaire is almost complete 12:07:39 agenda: https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#26_April_2023 12:08:09 matsuda has joined #wot 12:08:19 seb: we finally did a resolution about Test fest plans 12:08:39 ... no issues with the minutes 12:08:42 ... any comments? 12:08:54 ... ok, minutes approved 12:09:03 topic: quick updates 12:09:33 seb: use cases, profile, and architecture are cancelled in favor of the test fest 12:09:39 i|use|-> https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#Cancellations_and_Schedule_Updates Cancellations| 12:09:51 s/test fest/testfest/ 12:09:54 ... next monday is holiday we will cancel Monday calls 12:10:00 s/Test fest/Teftfest/ 12:10:07 ryuichi has joined #wot 12:10:11 s/Teftfest/Testfest/ 12:10:17 rrsagent, make log public 12:10:21 rrsagent, draft minutes 12:10:22 I have made the request to generate https://www.w3.org/2023/04/26-wot-minutes.html kaz 12:10:29 ... also next week is holyday in Japan 12:10:29 q+ 12:10:35 q? 12:10:41 q+ 12:10:45 ack e 12:10:47 ege: kaz are you available next week? 12:11:10 kaz: I can join if really needed. 12:11:31 ege: ok does this mean that we can do the meeting? 12:11:37 dezell has joined #wot 12:11:42 kaz: it would be better con cancel the calls 12:11:46 present+ David_Ezell 12:12:27 rrsagent, draft minutes 12:12:28 I have made the request to generate https://www.w3.org/2023/04/26-wot-minutes.html kaz 12:12:38 mc: I'm ok of canceling even if there is something to do in profile 12:12:45 present+ Ryuichi_Matsukura, Tetsushi_Matsuda 12:12:54 q+ 12:13:04 ... we can cancel everything but testing calls (without minutes) 12:13:25 ack k 12:13:28 kaz: if needed I can join 12:13:41 q+ 12:13:45 ege: in the TD call we need to decided the TF lead 12:13:55 ... we can have a tentative resolution 12:14:03 seb: I think we can wait 12:14:38 ack e 12:14:40 ack k 12:14:50 chair: Sebastian/McCool 12:14:54 mc: the only critical calls that we need to do is testing 12:15:05 seb: ok for me to cancel all the calls 12:15:05 rrsagent, draft minutes 12:15:07 I have made the request to generate https://www.w3.org/2023/04/26-wot-minutes.html kaz 12:15:44 +1 12:17:17 seb: there is an AC meeting this month 12:17:37 q+ 12:17:42 ... kaz will be not available. 12:18:03 kaz: technically group chairs can join the AC meeting if you want 12:18:30 ... let everybody know if you join that meeting 12:19:02 mc: we need to finalize test result for the 10th 12:19:41 mc: I can go, but only if it doesn't conflict with other calls 12:20:38 q? 12:20:50 ack k 12:20:56 topic: new charter review 12:20:59 seb: no news? 12:21:10 kaz: we got response for internationalization 12:21:17 ... we are waiting for other groups 12:21:40 mc: we have one PR that we should merge 12:21:51 ... just fixing minor issues (broken links) 12:22:04 seb: ok, any complains? 12:22:08 https://github.com/w3c/wot-charter-drafts/pull/116/files 12:22:22 mc: no real content change 12:22:47 q+ 12:22:57 s|https://github.com/w3c/wot-charter-drafts/pull/116/files|-> https://github.com/w3c/wot-charter-drafts/pull/116 wot-charter-drafts PR 116 Remove links to template| 12:23:04 rrsagent, draft minutes 12:23:06 I have made the request to generate https://www.w3.org/2023/04/26-wot-minutes.html kaz 12:23:12 ack cris_ 12:23:12 topic: TPAC 12:23:27 seb: we need an estimate about people going to spain 12:23:44 ... we have to submit the heads count next week 12:23:55 s/other groups/other groups. will talk about this issue during the W3C Strategy Team call next Tuesday./ 12:23:58 rrsagent, draft minutes 12:23:59 I have made the request to generate https://www.w3.org/2023/04/26-wot-minutes.html kaz 12:24:23 ... if you are not sure you can just add the probability 12:24:47 ... please update the list on the wiki 12:24:56 ... we should also start to think about topics 12:25:26 q+ 12:25:32 q+ 12:25:49 i|we need|-> https://www.w3.org/2023/09/TPAC/ TPAC page| 12:25:54 q+ 12:26:07 ege: we talked about this in the TD two weeks ago 12:26:18 i|we need|-> https://www.w3.org/2002/09/wbs/1/GroupsTPAC2023/ TPAC group meeting questionnaire (Member-only)| 12:26:28 ... we got same email in the CG 12:26:41 ... web agents group might organize something 12:27:14 kaz: we need to identify the expected count of the participants for rooms and slots 12:27:32 ... and basic category of meetings 12:27:35 ... please help 12:27:59 i|we need|-> https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf/2023_WoT_TPAC_Agenda TPAC 2023 WoT wiki| 12:28:27 mc: we should discuss things that are difficult to solve remotely 12:28:55 ... we can create v f2f to cover people that are not in good timezone 12:29:52 q+ 12:29:55 ack e 12:29:57 q+ 12:29:59 ack k 12:30:01 ack m 12:30:13 q+ 12:30:26 s/v f2f/virtual F2F/ 12:31:43 s/category of meetings/category of meetings which require us dedicated discussion on complicated or controversial topics./ 12:31:56 s/dedicated/dedicated F2F/ 12:32:12 rrsagent, draft minutes 12:32:13 I have made the request to generate https://www.w3.org/2023/04/26-wot-minutes.html kaz 12:34:02 mc: let's optimize for japan and europe 12:34:03 q? 12:35:34 ack e 12:35:40 ege: do we have an open day in TPac? 12:35:50 mc: Wednesday 12:36:10 kaz: it depends on what we would like to do 12:36:25 ... we don't need to have an open day 12:36:34 ... but if we want we can organize 12:36:37 q+ 12:36:44 ... it is something that should be part of the agenda discussion 12:38:01 mc: let's have a doodle poll 12:38:03 seb: ok 12:38:22 ack k 12:38:23 ack M 12:38:24 action: kaz to generate a doodle poll to find better slots for Thu/Fri 12:39:16 rrsagent, draft minutes 12:39:17 I have made the request to generate https://www.w3.org/2023/04/26-wot-minutes.html kaz 12:39:41 q+ 12:40:02 q+ 12:40:05 topic: schedule 12:40:18 seb: scripting api is planned to be published 12:40:23 ... which is the status? 12:40:28 daniel: we are working on it 12:40:44 kaz: we made the resolution last week 12:40:46 q+ 12:41:04 ... there was some typos 12:41:41 q+ 12:41:42 ... the task force wanted to include that too 12:41:56 ack k 12:42:02 ... plus there were discussion on the scripting api 12:42:14 ... about the charter 12:42:32 ... and how the scripting api was recorded as an informative document 12:42:47 mc: I also made a PR to update 12:43:00 ... the schedule 12:43:06 seb: ok for merging 12:43:10 s/about the charter/some of the Scripting API TF participants are wondering about the possibility of making Scripting API a normative document./ 12:43:42 q+ 12:43:54 ack mc 12:44:04 daniel: scripting api was just minor changes 12:44:24 https://github.com/w3c/wot-scripting-api/pull/469 12:44:56 ack d 12:45:09 daniel: just minor changes as you can see 12:45:18 s|https://github.com/w3c/wot-scripting-api/pull/469|-> https://github.com/w3c/wot-scripting-api/pull/469 wot-scripting-api PR 469 - Align spec with INFRA| 12:47:18 seb: we can even don't do the resolution 12:47:29 kaz: I think we should even if it was just a typo fix 12:47:36 q? 12:47:42 q+ 12:48:00 https://github.com/w3c/wot-scripting-api/pull/469 12:48:10 proposal: The group decided to publish Scripting API note after PR 469 in the scripting has been merged 12:48:25 s/after/after the recently updated/ 12:49:22 proposal: The group decided to publish Scripting API note after the recently updated PR 469 in the scripting has been merged 12:49:44 ack c 12:49:46 ack k 12:50:16 resolution: The group decided to publish Scripting API note after the recently updated PR 469 in the scripting has been merged 12:52:00 s|kaz: I think we should even if it was just a typo fix|kaz: I think we still should make an updated resolution given we made a resolution last week for PR 469 and we've updated the PR 469 itself after the resolution was made. Note that we should not add any updates to the PR after making resolution, but should create a new separate PR for typo fix./ 12:52:14 s|fix./|fix.| 12:52:16 cris: we were also surprised about finding out that scripting API is informative document 12:52:21 q+ 12:52:23 ack d 12:53:09 ... we were planning to have it a Note Rec track 12:53:42 seb: is this the kind of document that is in between informative and rec track? 12:53:58 cris: yes, but in the charter we said it was just informative 12:54:39 kaz: Note reccomantion track is not really safe in regards of patent policy 12:55:39 seb: we are out of time 12:56:12 ... maybe we need another discussion slot 12:56:12 q? 12:56:12 kaz: it would be better to discuss about this offline 12:56:12 ack k 12:57:50 seb: it seems there is not something in between doc 12:57:53 q+ 12:58:37 dape: it seems that note-track is not recommended by w3c it was not clearly stated. 12:58:59 seb: we need a separate meeting 12:59:26 mc: let's discuss this in the next chair call 12:59:33 ... in the meantime we can use emails 13:00:02 kaz: for the record from the beginning I was suggesting to not go for that direction. 13:00:14 topic: testing 13:00:21 seb: discuss this in the testing call 13:00:26 topic: testimonial 13:00:46 seb: please talk about your upper management for testimonials 13:00:53 ... also about press release 13:01:34 topic: societal impact questionare 13:01:52 seb: michael worked hard on the doc, 13:01:58 ... I think it is in good shape 13:02:04 ... we can merge the PR as it is 13:02:11 ... of course we can always improve it 13:02:19 s/Note reccomantion track is not really safe in regards of patent policy/As I've been repeatedly mentioning, there is no "Note REC track" defined within the W3C Process, also making part of a group Note normative would be dangerous from the Patent Policy viewpoint./ 13:02:21 ... but it is fine at it is 13:02:49 rrsagent, draft minutes 13:02:50 I have made the request to generate https://www.w3.org/2023/04/26-wot-minutes.html kaz 13:03:26 q| 13:03:58 proposal: submit the current draft of the societal questionnaire. 13:04:14 https://github.com/w3c/wot-architecture/pull/897 13:04:23 +1 13:04:28 proposal: submit the current draft of the societal questionnaire at https://github.com/w3c/wot-architecture/pull/897 13:04:47 resolution: submit the current draft of the societal questionnaire at https://github.com/w3c/wot-architecture/pull/897 13:05:18 -> https://github.com/w3c/wot-architecture/pull/897 PR 897 - Societal Impact Questionniare 13:05:34 q+ 13:06:23 [adjourned] 13:06:29 rrsagent, draft minutes 13:06:30 I have made the request to generate https://www.w3.org/2023/04/26-wot-minutes.html kaz 13:06:36 q- 13:55:32 Mizushima has left #wot 14:33:27 kaz has joined #wot 15:07:19 Zakim has left #wot