14:11:18 RRSAgent has joined #wot-pf 14:11:22 logging to https://www.w3.org/2023/02/08-wot-pf-irc 14:11:29 meeting: WoT Plugfest/Testing 14:11:47 topic: Agenda 14:12:02 present+ Kaz_Ashimura, Michael_McCool, Cristiano_Aguzzi, Ege_Korkan, Kunihiko_Toumura, Luca_Barbato, Michael_Koster, Tomoaki_Mizushima 14:12:04 mm: minutes, dev meeting and finally testfest logistics 14:12:08 topic: Minutes 14:12:14 i/minutes/scribenick: cris__/ 14:12:26 mm: mentioned playground fixes and new features 14:12:35 i|mention|-> https://www.w3.org/2023/02/01-wot-pf-minutes.html Feb-1| 14:13:15 ... we talked about developer meeting for a lot of time 14:13:20 .... created some directories 14:13:37 ... we have some work to do 14:13:47 chair: McCool 14:13:47 ... no other comments 14:14:15 ... just one minor thing: can you use mailing list instead of ML 14:14:23 ... makes things clearer 14:14:44 ... Takenak is spelled wrong 14:15:28 topic: developer meeting 14:15:36 mc: do we have a doodle pool? 14:15:38 kaz: not yet 14:16:07 agenda: https://www.w3.org/WoT/IG/wiki/PlugFest_WebConf#Agenda_08.02.2023 14:16:20 rrsagent, make log public 14:16:22 mm: any date in mind? 14:16:26 rrsagent, draft minutes 14:16:27 I have made the request to generate https://www.w3.org/2023/02/08-wot-pf-minutes.html kaz 14:16:34 q+ 14:17:10 ack e 14:17:47 mc: let start from a concrete proposal and then we can tune it 14:18:15 ... Monday at 9-10 ? with an evening slot in US (which is morning slot in JP) 14:18:32 i|do we have|-> https://github.com/w3c/wot-testing/tree/main/events/2023.03.DevMtg 2023.03.DevMtg 14:18:38 rrsagent, draft minutes 14:18:39 I have made the request to generate https://www.w3.org/2023/02/08-wot-pf-minutes.html kaz 14:18:47 ... testfests is more for active WoT members 14:19:08 ... dev call is more about read manual assertions and get feedback 14:19:17 q+ 14:19:38 ... 9-10 for west cost is not that great 14:19:53 ... we can do at 10 AM on Thursday 14:20:12 ... good for east-cost and europe but not that great for japan 14:20:20 ... but we have a dedicated event for that 14:20:52 kaz: are we ok with cancelling the ordinary calls during that week? 14:20:59 mc: we can 14:21:29 ... I'm worried for the low attendance from US 14:21:38 ... maybe we should find better slots 14:22:08 kaz: if we cancel regular calls we are flexible and generate two doodle pools 14:22:23 mc: we can sacrifice discovery and security 14:22:56 q+ 14:23:02 ack k 14:23:13 mc: do we people for china? 14:23:14 ack e 14:23:17 ege: actually yes 14:24:04 mc: let's keep the japan time slot resonable for Asia 14:26:56 mc: any conflict for the week of 27th ? 14:27:14 kaz: do we need testfest for profile? 14:27:35 mc: we still need to resolve a bunch of at risk items 14:27:45 ... I have some implementations that could fill some of the gaps 14:28:00 ... testfest helps to focus people on the implementation work 14:28:16 kaz: we really need to organize a test event for a whole week? 14:28:34 mc: is the testfest the best way to cover the implementation report? 14:29:52 present+ Ryuichi_Matsukura 14:30:49 kaz: we were very busy with checking the data itself during the testfest more than implementation 14:31:03 ... and dubugging the tools 14:31:17 q+ 14:31:29 ... maybe it is better to have an async phase where people prepare stuff for the testfest 14:31:46 mc: the more work people do before the testfest the better 14:31:49 Mizushima has joined #wot-pf 14:32:11 ack e 14:32:14 ege: it should clear how to submit data 14:32:21 ... and also create dealines 14:32:34 s/dealines/deadlines/ 14:32:37 s/should/should be/ 14:32:56 ... maybe for the next charter I prefer to do less testfests 14:33:20 mc: it could be a argument for not doing this one, but we need to cover the gaps 14:33:28 s/to do/doing/ 14:33:32 ege: no I mean less testfests but more productive 14:33:40 q+ 14:34:22 kaz: we should focus on how to better organize the work 14:34:25 mc: I agree 14:34:47 ... also for the next charter I won't have that much bandwidth 14:35:09 +1 to find a dedicated person 14:35:30 I would also volunteer but I will not have bandwidth in the next charter either 14:36:47 mc: let's try to set the Developer meeting for the week of the 27th 14:37:17 kaz: if possible it is better to have the Developer meeting first and then test fest 14:37:45 mc: ok it's an alternative proposal but it would overlaps with the Japanese Developer meeting 14:37:52 ... but it is only one day 14:38:11 kaz: in any case let's propose it in the doodle pool 14:40:34 mc: we got some contribution from Michael lagally, just a draft but it needs clean up 14:40:41 ... we have something from TD too 14:40:43 q+ 14:40:46 ... no new results 14:41:06 ... will create a folder for Discovery 14:41:15 kaz: we can use the md file to clarify the intention 14:41:41 ack k 14:41:42 ... but for the developer meeting the goal is to explain the intentions of each assertions. 14:42:00 mc: the result we are looking for is to resolve al many at risk items as possible 14:42:10 ... we don't have implementers or reporting to some of them 14:42:23 s/or/that are/ 14:43:53 ege: I can work on the Thing Description 14:44:05 s/intentions of each assertions./intentions of each assertions. So we should concentrate on that clarification./ 14:46:02 rrsagent, draft minutes 14:46:03 I have made the request to generate https://www.w3.org/2023/02/08-wot-pf-minutes.html kaz 14:46:49 s/test fest/testfest/ 14:48:00 s/we can use the md file to clarify the intention/We can use the content of the DRAFT-atrisk-explanations.md file as the starting point/ 14:48:18 topic: AoB? 14:48:32 ege: just a small thing we push a new version of the TD playground 14:48:43 ... it should be stable for the upcoming testfests 14:48:53 mc: I have a PR that I need to fix 14:49:40 ... I see no new pr 14:49:45 s/for the developer meeting the goal/the goal of the developer meeting/ 14:49:48 rrsagent, draft minutes 14:49:49 I have made the request to generate https://www.w3.org/2023/02/08-wot-pf-minutes.html kaz 14:49:55 ... but you can add your results 14:50:14 ege: small thing we added TM based validation to the playground 14:50:30 ... you may see some errors if your using a fake TM 14:50:43 ... in that case you should enable a flag 14:50:55 mc: can you add some explanation in a readme? 14:51:14 https://github.com/thingweb/thingweb-playground/blob/master/packages/cli/index.js#L45 14:52:56 q+ 14:53:43 https://github.com/w3c/wot-thing-description/pull/1758 14:54:47 it is now applied to the batchValidation instead of a readme 14:55:07 (McCool has added clarification as a comment to the batchValidation.sh) 14:55:27 [adjourned] 14:55:36 rrsagent, draft minutes 14:55:37 I have made the request to generate https://www.w3.org/2023/02/08-wot-pf-minutes.html kaz 14:57:42 Mizushima has left #wot-pf 17:02:22 Zakim has left #wot-pf