14:04:06 RRSAgent has joined #wot-pf 14:04:10 logging to https://www.w3.org/2023/02/01-wot-pf-irc 14:11:01 MIzushima has joined #wot-pf 14:11:49 for the agenda: https://github.com/thingweb/thingweb-playground/pull/443 14:14:43 topic: Minutes Review 14:15:04 mm: minutes are fine 14:16:00 mm: any objections? 14:16:04 mm: minutes are approved 14:16:54 McCool_ has joined #wot-pf 14:16:58 https://github.com/thingweb/thingweb-playground/pull/443 14:17:11 meeting: WoT Plugfest/Testing 14:17:51 i|minutes are|-> https://www.w3.org/2023/01/25-wot-pf-minutes.html Jan-25| 14:18:23 i/443/topic: Playground fix/ 14:18:29 s/https/-> https/ 14:18:55 s/443/443 thingweb-playground PR 443 - implement json spell checker/ 14:19:05 rrsagent, make log public 14:19:09 rrsagent, draft minutes 14:19:10 I have made the request to generate https://www.w3.org/2023/02/01-wot-pf-minutes.html kaz 14:19:28 present+ Kaz_Ashimura, Michael_McCool, Ege_Korkan, Tomoaki_Mizushima 14:20:43 present+ Kaz_Ashimura, Michael_McCool, Ege_Korkan, Tomoaki_Mizushima 14:20:49 chair: McCool 14:21:07 i/for the agenda/scribenick: Ege/ 14:21:10 rrsagent, draft minutes 14:21:11 I have made the request to generate https://www.w3.org/2023/02/01-wot-pf-minutes.html kaz 14:24:20 -> https://github.com/w3c/wot-testing/pull/531 PR 531 - Remove authorization key from client flow 14:24:22 merged 14:24:50 i/https/topic: PRs/ 14:25:06 (GitHub got stuck, and PR review postponed) 14:25:19 topic: Plan At-Risk Walkthroughs 14:27:47 -> https://github.com/w3c/wot/blob/main/charters/wg-2021-extension-plan.md updated schedule 14:28:00 q| 14:28:06 s/q|// 14:28:08 q+ 14:30:19 (discussion on when/how to organize the event) 14:31:20 kaz: we could have the walkthrough event as an event of the WoT CG and the WoT-JP CG. However, we WoT WG ourselves are responsible to clarify what we meant by each assertion 14:31:26 mm: right 14:32:29 kaz: so the third point on the agenda wiki, "Need clear policy for what it means to "pass" each at-risk assertion", should be the most important and need to be done before the event 14:32:32 mm: right 14:33:26 ... (put tentative proposed date as "week of March 20") 14:33:43 ... (and JP version "week of March 27") 14:34:18 (discussion on necessary prework) 14:34:41 mm: MD files, presentation explaining at-risk items 14:35:16 (resources to be put under wot-testing/events/devmtg-03-2023) 14:35:38 mm: let's create a directory there 14:36:27 ... also need to decide the date 14:36:40 ... we're looking some time in March 14:36:49 rrsagent, make log public 14:36:53 rrsagent, draft minutes 14:36:54 I have made the request to generate https://www.w3.org/2023/02/01-wot-pf-minutes.html kaz 14:37:25 i/merged/scribennick: kaz/ 14:37:31 rrsagent, draft minutes 14:37:32 I have made the request to generate https://www.w3.org/2023/02/01-wot-pf-minutes.html kaz 14:37:57 s/scribenn/scriben/ 14:37:59 rrsagent, draft minutes 14:38:00 I have made the request to generate https://www.w3.org/2023/02/01-wot-pf-minutes.html kaz 14:38:25 q+ 14:38:56 ek: some people have problem to make PRs for wot-testing repo 14:40:59 kaz: wot-testing repo is marked as "homepage", which is informative 14:41:16 ... so we should be able to merge all the proposed PRs safely if needed 14:41:19 ek: ok 14:42:15 -> https://github.com/w3c/wot-testing/blob/main/w3c.json w3c.json on wot-testing 14:42:53 mm: just created an area for the Dev Meeting 14:43:01 -> https://github.com/w3c/wot-testing/tree/main/events/2023.03.DevMtg 2023.03.DevMtg 14:43:42 mm: we can have subdirectories for necessary resources 14:43:48 ... e.g., TD 14:44:17 s|TD|TD/atrisk-explanations.md| 14:44:25 rrsagent, draft minutes 14:44:27 I have made the request to generate https://www.w3.org/2023/02/01-wot-pf-minutes.html kaz 14:49:11 q+ 14:50:25 (generates the initial version at-risk list) 14:50:27 ack k 14:50:36 kaz: OK with starting with this initial list 14:51:51 ... but each spec TF should help us clarify the meaning of each assertion 14:51:51 ek: TD should be OK 14:51:51 q+ 14:51:51 ... but need clarification for Architecture 14:52:01 kaz: right. that's why we need to ask each TF for help 14:52:02 q? 14:52:13 mm: ok 14:52:27 ... will generate similar list for Discovery as well 14:52:37 ack m 14:52:59 mizu: do you know who have implementations for at-risk features? 14:53:07 ... who to get contacted? 14:53:23 mm: I'm already aware of one implementation 14:53:30 ... and need a second one 14:53:42 ... would expect the list to be short 14:53:46 q? 14:53:46 q+ 14:54:07 ack k 14:54:22 kaz: probably Mizushima-san's point is who to be invited to the Dev meetup 14:54:53 ... meaning those invitees might have additional implementations which would cover the at-risk features 14:54:57 mm: yeah 14:55:14 ... probably, Takenak, Bosch, etc. 14:55:27 ... should send invitations to the CG participants as well 14:56:13 kaz: have Bosch, etc., joined the CGs? 14:56:21 ... if not, we should invite them separately 14:57:19 mm: would use MLs for the invitation 14:57:51 kaz: if some of the implementers have not joined CGs yet, we can create another ML, group-wot-implementers 14:57:54 mm: sounds good 14:58:14 ... will bring this question to the Architecture call tomorrow 14:58:46 ... regarding Profile, let's talk about how to deal with that with Lagally next week 14:58:49 [adjourned] 14:58:56 rrsagent, draft minutes 14:58:57 I have made the request to generate https://www.w3.org/2023/02/01-wot-pf-minutes.html kaz 16:58:38 Zakim has left #wot-pf