14:12:57 RRSAgent has joined #wot-pf 14:12:57 logging to https://www.w3.org/2022/02/09-wot-pf-irc 14:13:07 meeting: WoT Plugfest/Testing 14:13:10 chair: Fady 14:13:52 present+ Kaz_Ashimura, Fady_Salama, Cristiano_Aguzzi, Ege_Korkan, Jack_Dickinson, Kunihiko_Toumura, Michael_Lagally, Michael_McCool, Tomoaki_Mizushima 14:14:42 cris_ has joined #wot-pf 14:14:44 scribenick: cris_ 14:14:47 topic: Minutes 14:14:52 fady: we discussed a possible test suite for discovery 14:15:06 i/fady:/scribenick: kaz/ 14:15:09 scribenick: cris_ 14:15:10 mc: we still need to finalize it 14:15:20 fady: minutes ok? 14:16:15 topic: Pull Requests 14:16:29 subtopic: PR 207 14:16:51 fady: minor PR just updated the directories and file names to be ready for the next plug fest 14:17:11 q+ 14:17:13 q? 14:17:40 mc: we should discuss the follow up pf 14:17:54 ... in particular about having it in person or virtual 14:18:08 ... and thinking about the schedule 14:18:55 ... we have PR transition in November and a CR transition is due to end of August 14:18:58 i|minor PR|-> https://github.com/w3c/wot-testing/pull/207 PR 207 - update date of next Testfest/Plugfest to 03.2022| 14:19:05 ack mc 14:19:24 https://github.com/w3c/wot/pull/1012 14:20:31 s/https/-> https/ 14:20:40 ... for mid-april we need an implementation report draft 14:20:53 s/1012/1012 wot PR 1012 - Update Plan due to delay in Discovery, TD 1.1, CR/PR typo| 14:21:05 ... for profile we need an implementation report draft for end of August 14:21:15 rrsagent, make log public 14:21:20 rrsagent, draft minutes 14:21:20 I have made the request to generate https://www.w3.org/2022/02/09-wot-pf-minutes.html kaz 14:21:20 ... tpac is scheduled for 12-16 September 14:21:45 ... having an in person PF the week before or the week after 14:21:54 rrsagent, draft minutes 14:21:54 I have made the request to generate https://www.w3.org/2022/02/09-wot-pf-minutes.html kaz 14:22:54 ... another option might be having a PF in July which was the original plan 14:23:14 fady: yes 14:23:41 mc: since we have a TPac in September we could have a third PF 14:24:03 s/typo|/typo/ 14:24:04 rrsagent, draft minutes 14:24:04 I have made the request to generate https://www.w3.org/2022/02/09-wot-pf-minutes.html kaz 14:24:06 q? 14:24:09 q+ Ege 14:24:11 ack e 14:24:18 ege: generally I like having a PF in Tpac 14:24:43 ... if Tpac is phisical I would vote for having one 14:24:46 q+ mlagally 14:24:50 ack ml 14:25:08 ... but I would split PF and TestFest 14:25:10 present+ David_Ezell 14:25:16 rrsagent, draft minutes 14:25:16 I have made the request to generate https://www.w3.org/2022/02/09-wot-pf-minutes.html kaz 14:25:35 ml: I have different opinion, you can optimize time 14:25:59 ege: I'm afraid that we'll lose focus on the Test Report 14:26:06 s/Test/implementation/ 14:26:09 s/Tpac/TPAC/g 14:26:18 s/phisical/physical/ 14:26:32 mc: right, the current plan is to have them mixed now but different sync meetings 14:26:33 q+ 14:26:45 ... doing the same thing for mid july make sense 14:27:30 ... all the testing should be done before September 14:28:22 q? 14:28:32 ml: if it is a physical event it make sense to build demos 14:28:48 mc: I agree but demos are separate activities 14:29:15 ... my plan is to add TPac on the calendar, about PF will see 14:29:43 kaz: It more important to understand who is going to take the lead for each events 14:29:55 s/it more/it is more/ 14:30:44 ... regardless about if the event is going to be physical or virtual 14:30:44 s/It more/From my viewpoint, what is more/ 14:30:46 q? 14:30:50 ack k 14:31:05 s/important/important is/ 14:31:11 topic: Tools 14:31:22 fady: we already have a tool to merge CSV files 14:31:27 s/each events/each event/ 14:31:32 ... and generate a final implementation report 14:31:52 s/regardless about/regardless of/ 14:32:19 ... we also need tools for other specs like discovery and profiles 14:32:20 s/if the/whether/ 14:32:50 ege: we have something for discovery 14:33:01 s/or virtual/or not, we need to clarify who to take the lead, how to organize the events, what kind of repository structure to be used, etc./ 14:33:03 ... probably one test report per discovery implementation 14:33:17 ... farshid has his testing tool 14:33:22 mc: yeah 14:33:30 ... we need to test consumers 14:33:43 s/discovery and profiles/Discovery and Profile/ 14:33:57 s/for discover/for Discovery/ 14:34:07 ... we need two consumer implementations 14:34:20 q+ 14:34:39 ege: why merge? just counting 14:35:18 q? 14:35:40 mc: not may assertions on the consumer side 14:35:53 ack cris 14:36:18 cris: how can we test introductions? 14:36:27 mc: just the one that have assertions 14:38:40 ege: I have a discovery consumer 14:39:24 rrsagent, draft minutes 14:39:24 I have made the request to generate https://www.w3.org/2022/02/09-wot-pf-minutes.html kaz 14:39:41 s/Tpac/TPAC/g 14:39:49 s/TPac/TPAC/g 14:39:52 s/Tpac/TPAC/g 14:39:54 rrsagent, draft minutes 14:39:54 I have made the request to generate https://www.w3.org/2022/02/09-wot-pf-minutes.html kaz 14:40:05 cris: webthings has an implementation for mDNS too 14:40:15 mc: we should get organized 14:40:28 ... also about ThingModels and testing tools 14:40:29 q? 14:40:40 fady: I'm working on it 14:41:07 ... I'm more concerned about other tools 14:41:10 q+ 14:42:46 cris: Is it the thing model process normative? 14:42:51 mc: not sure 14:43:06 ... also do we have two implementations 14:44:08 fady: if I understand correctly we already have two implementations 14:44:16 mc: yeah we have to processors 14:44:30 ... but we also need to have a set of thing models (i.e. examples) 14:44:44 ... from two organizations 14:45:28 q? 14:45:31 ack cris_ 14:45:36 cris: we had some thing models 14:45:47 ... but we didn't cover all the features for sure 14:46:08 ege: tum published Thing Models too 14:46:20 ... but as partial TDs 14:46:57 mc: which is the timeline for having the assertion testing tool? 14:47:03 fady: two weeks from now 14:47:17 mc: then I'll open an issue for having discovery too 14:48:16 s/ tum / TUM / 14:48:36 mc: what about logistics? WebEx? 14:48:42 kaz: we can use zoom as well 14:49:21 mc: I have no strong preference, but if I have to choose webex would be preferred 14:49:34 ege: we can't install zoom client as Siemens 14:49:54 mc: Intel uses Teams 14:50:20 q+ 14:50:46 mc: test fest would be only for wg 14:50:53 ... so we don't have particular requirements 14:51:20 kaz: we can use webex and share the link to everyone interested ( for the plug fest) 14:51:55 s/use webex/allocate a dedicated WebEx call/ 14:52:13 s/everyone interested/all the invited guests/ 14:52:18 q? 14:52:19 ack c 14:52:32 q+ 14:52:49 cris: I think we have to think about what we have to do 14:52:58 ... if we have particular requirements that webex can't do 14:53:14 kaz: there's no particular difference 14:53:20 mc: let's keep it simple 14:53:26 ... and use webex 14:53:27 s/there's/from my viewpoint, there's/ 14:53:39 q? 14:53:42 ack k 14:53:43 kaz: ok I'll allocate the links 14:54:06 fady: no complaints about the schedule 14:54:10 s/the links/WebEx calls based on the currently proposed schedule/ 14:54:18 s/I'll/I can/ 14:54:30 [adjourned] 14:54:32 fady: adjourned 14:54:38 s/[adjourned]// 14:54:42 [adjourned] 14:54:51 rrsagent, draft minutes 14:54:51 I have made the request to generate https://www.w3.org/2022/02/09-wot-pf-minutes.html kaz