14:13:34 RRSAgent has joined #wot-pf 14:13:34 logging to https://www.w3.org/2022/11/30-wot-pf-irc 14:14:28 Mizushima has joined #wot-pf 14:16:16 ktoumura has joined #wot-pf 14:16:36 cris___ has joined #wot-pf 14:17:25 sebastian has joined #wot-pf 14:17:56 14:18:03 topic: Minutes 14:18:04 meeting: WoT Testing/Plugfest 14:18:31 -> https://www.w3.org/2022/11/16-wot-pf-minutes.html 14:19:59 mlagally has joined #wot-pf 14:20:16 any objections? 14:20:21 no 14:20:28 approved 14:20:48 topic: TestFest preparation 14:21:08 14:21:47 14:21:49 s/html/html Nov-16/ 14:21:49 -> https://github.com/w3c/wot-testing/tree/main/events/2022.12.Online 14:22:08 s/Online/Online 2022.12.Online/ 14:22:15 rrsagent, make log public 14:22:19 rrsagent, draft minutes 14:22:19 I have made the request to generate https://www.w3.org/2022/11/30-wot-pf-minutes.html kaz 14:23:16 present+ Kaz_Ashimura, Michael_McCool, Cristiano_Aguzzi, Ege_Korkan, Kunihiko_Toumura, Michael_Lagally, Ryuichi_Matsukura, Sebastian_Kaebisch, Tomoaki_Mizushima 14:23:24 14:23:52 MM: do we need VPN? 14:24:24 KT: for this PlugFest we do not need VPN 14:24:56 ... I'm ok with it 14:26:10 q+ 14:26:51 MM: we need a section with information how the results should be submitted 14:27:18 14:30:17 ML: We should be precise where should the developer place the inputs. 14:30:37 q+ 14:31:20 ack ml 14:32:23 -> https://github.com/w3c/wot-testing/tree/main/events/2022.07.Online 2022.07.Online 14:33:27 ... we should provide descriptions for each test context 14:33:58 EK: I did this for the July PlugFest 14:34:17 q? 14:35:06 Kaz: We should clearify the targets 14:35:21 s/clearify/clarify/ 14:36:34 MM: We have implementation gaps, target should be to close those gaps 14:37:07 Kaz: we should record this kind of decision 14:37:52 q+ 14:38:02 ack k 14:38:33 brb 14:39:30 kaz: I'm a bit concerned about the iterative approach specifically this time 14:39:53 ... how to assign people to each specification and how to organize the testing for each specification would be complicated 14:40:12 back 14:40:19 i/I'm a bit/scribenick: kaz/ 14:40:30 scribenick: sebastian 14:40:59 MM: we need to provide more details about profile testing 14:41:33 s/those gaps/those gaps for all the 4 normative specs, i.e., Architecture, Profile, TD and Discovery./ 14:41:35 ML: why do we need the this folder 2022.12? 14:41:44 MM: mainly the readme 14:43:05 ... in the past we put also there the testing results, however, its better provide everything directly into data/input_2022 14:45:22 s/complicated/complicated. Trying iterative approach again may be fine, but it would not work to ask you McCool to handle everything and the other Editors just help you. We need to clarify actual assignment on who to do what./ 14:45:38 EK: Propose that the details should be the seperated TF. So TD test information should provided by TD repo, Profile from Profile repo, etc. 14:45:45 ML: agree with this approache 14:46:08 14:49:33 ML: contributors should also mention company names 14:49:56 EK: it should be the name of the implementation / tool 14:52:16 MM: for TD the results are combined, however, results for Profile and Discovery from the inputs 14:52:29 q+ 14:52:48 s/from/taken from 14:54:55 14:55:51 q+ 14:55:53 q- 14:56:45 s/the seperated TF/of the seperated TF 14:59:55 ML: there is a PR in the TD call about the implementation overview 15:00:17 -> https://github.com/w3c/wot-thing-description/pull/1733 15:00:34 ML: would be good to merge this one in the TD call 15:00:34 [adjourned] 15:00:41 rrsagent, make log public 15:00:46 rrsagent, draft minutes 15:00:48 I have made the request to generate https://www.w3.org/2022/11/30-wot-pf-minutes.html kaz 17:00:55 Zakim has left #wot-pf