14:10:54 RRSAgent has joined #wot-pf 14:10:54 logging to https://www.w3.org/2022/01/26-wot-pf-irc 14:11:05 meeting: WoT Plugfest/Testing 14:11:13 chair: Fady 14:11:51 present+ Kaz_Ashimura, Cristiano_Aguzzi, David_Ezell, Ege_Korkan, Fady_Salama, Kunihiko_Toumura, Michael_Lagally, Michael_McCool, Tomoaki_Mizushima 14:12:19 scribenick: kaz 14:12:38 agenda: https://www.w3.org/WoT/IG/wiki/PlugFest_WebConf#Agenda_26.01.2022 14:12:53 topic: Agenda 14:13:22 mm: suggest we prioritize the discussion with Lagally for today 14:13:34 kaz: yes, so let's review the previous minutes later 14:13:47 topic: Test/Plugfest scenarios 14:13:54 cris_ has joined #wot-pf 14:14:23 -> https://github.com/w3c/wot-testing/pull/204 PR 204 - Create test/plugfest scenarios.md 14:14:48 q+ 14:15:11 ml: suggesting we clarify scenarios for Testing and Plugfest 14:15:13 q+ 14:15:34 fs: how long do we expect for Testfest/Plugfest? 14:16:12 mm: maybe two weeks? 14:16:22 ... one week before meeting and another week after meeting 14:17:31 ek: this time we have enough experience for Testing 14:17:55 ... TD would require less time 14:18:04 ... but Discovery may require longer 14:18:38 mm: could go for 2-week plan 14:18:50 ml: we do have implementations 14:19:03 ... so don't understand your points, Ege... 14:19:29 q+ 14:19:33 ek: Profile is new 14:19:36 ack e 14:20:33 ml: how do you think we could get implementations for Profile? 14:21:17 ... if some companies say they have implementations, we can work on that. right? 14:22:29 kaz: confused 14:22:53 ... we're talking about not the schedule itself but Lagally's proposed template for Testfest/Plugfest. right? 14:23:13 mm: this is more about Plugfest 14:23:33 ml: why don't we define the scope of the events first? 14:23:36 q? 14:23:38 ack k 14:23:39 ack m 14:23:41 q+ 14:24:05 mm: ok 14:24:29 ... please note we don't need "Test Scenario" but we need "Test Cases" 14:24:34 a? 14:24:39 s/a?/q?/ 14:24:51 s/q?// 14:25:17 q? 14:26:22 kaz: we need some template to describe Plugfest procedure 14:26:43 ... and also need another kind of template to describe Testfest procedure 14:26:48 mm: yes 14:26:55 ... but templates are just part of the procedure 14:26:59 kaz: yeah 14:27:32 (Fady merges PR 204 itself and we'll continue the discussion) 14:27:57 topic: Scope and schedule of the next Testfest 14:28:51 mm: need to define the scope of the Testfest 14:29:02 fs: (creates a GitHub Issue) 14:29:04 q? 14:29:07 ack k 14:29:22 mm: need to ask Lagally and Ege for opinions 14:29:42 ... basically 2 weeks 14:29:54 ... and we need to cancel regular calls during that period 14:32:08 fs: (put several options on the Issue) 14:33:57 q? 14:33:59 q+ 14:35:49 s/options/logistical points/ 14:37:31 kaz: btw, the title of the Issue should say "Schedule and Scope", and we should talk about the scope too 14:37:34 mm: right 14:37:53 fs: (fix the title of the Issue) 14:38:06 now the content of the issue is: 14:38:07 [[ 14:38:32 testfest should b in the week from Feb-28 to Mar-4 14:38:51 combined Testfest/Plugfest in one week with 2 calls per day 14:39:03 8am-9am ET for Testfest 14:39:09 9am-10am ET for Plugfest 14:39:10 ]] 14:39:23 ack k 14:39:31 ca: ok with me 14:39:53 mm: need to have some experience about Profile too 14:40:15 ... will send this issue to the whole group and ask for opinions 14:40:45 -> https://github.com/w3c/wot-testing/issues/206 Issue 206 - Schedule and Scope of the 03.2022 Testfest/Plugfest 14:42:43 topic: PRs 14:42:46 subtopic: PR 205 14:42:59 -> https://github.com/w3c/wot-testing/pull/205 PR 205 - Add template directory for project PRs 14:43:24 q+ 14:43:33 ml: this is about Plugfest. right? 14:43:36 fs: yes 14:44:32 s/ml:/mm:/ 14:44:44 mm: should have separate MD to describe the scenarios 14:45:42 ... also we should have separate areas, one for Plugfest and another for Testfest 14:46:15 q? 14:46:45 ... we may share the same TDs for both of them, though 14:48:09 ... let's look into what's available now 14:48:21 kaz: sorry but kind of confused with PR 205 14:48:37 ... we should not mix up the old results and the actual template within this PR 14:48:52 ... probably we should once list what we should do first 14:49:12 ... and think about the possible template collaboratively with Lagally, because he also proposes some template 14:49:15 mm: yeah 14:50:24 ... also would suggest merge this PR itself and let's continue further discussion 14:51:21 kaz: ok with merging this PR itself, but for the future discussion, please don't too many changes within one PR 14:51:32 mm: let's modify the title of the PR this time 14:51:34 kaz: ok 14:53:29 fs: (modifies the PR description as well) 14:56:13 then merged 14:57:17 fs: (goes through the merged results) 14:57:41 [adjourned] 14:57:45 rrsagent, make log public 14:57:52 rrsagent, draft minutes 14:57:52 I have made the request to generate https://www.w3.org/2022/01/26-wot-pf-minutes.html kaz 14:57:58 Mizushima has left #wot-pf 17:04:46 Zakim has left #wot-pf 18:15:17 sebastian has joined #wot-pf 18:15:46 sebastia_ has joined #wot-pf