13:04:47 RRSAgent has joined #wot-pf 13:04:52 logging to https://www.w3.org/2023/03/22-wot-pf-irc 13:04:56 meeting: WoT Testing/Plugfest 13:10:36 agenda: https://www.w3.org/WoT/IG/wiki/PlugFest_WebConf#Agenda_22.03.2023 13:10:41 chair: Ege 13:10:46 regrets+ McCool 13:11:12 present+ Kaz_Ashimura, Ege_Korkan, Cristiano_Aguzzi, Luca_Barbato, Michael_Koster, Tomoaki_Mizushima 13:11:52 cris__ has joined #wot-pf 13:11:59 topic: minutes 13:12:19 ege: there is a typo in the second section 13:12:35 scribenick: cris__ 13:12:48 ege: then the initials are not correct 13:12:56 ... we will review PRs also today 13:13:14 ... I had an action item but I forgot 13:13:23 ... we defined the date for dev meeting 13:14:05 ... then we discussed about slides (which I did) 13:14:12 ... but the minutes look short 13:14:20 kaz: it was a short meeting 13:14:40 ege: any problems? 13:14:41 ... ok 13:14:48 ... minutes accepted 13:14:53 topic: Quick updates 13:14:56 i|there is a|-> https://www.w3.org/2023/03/15-wot-pf-minutes.html Mar-15| 13:14:58 ege: any updates? 13:15:08 rrsagent, make log public 13:15:39 rrsagent, draft minute 13:15:39 I'm logging. I don't understand 'draft minute', kaz. Try /msg RRSAgent help 13:15:39 topic: Pull requests 13:15:39 subtopic: PR 536 13:16:03 ege: there was a problem with the CI script 13:16:07 https://github.com/w3c/wot-testing/pull/536 13:16:09 s/rrsagent, draft minute/ 13:16:11 rrsagent, draft minutes 13:16:12 I have made the request to generate https://www.w3.org/2023/03/22-wot-pf-minutes.html kaz 13:16:19 ... but the PR should fix it 13:16:22 ... I like the rendering 13:16:29 cris: +1 13:16:42 ege: we should use it for arch and td as well 13:17:01 ... we can ask Toumura-san 13:17:21 s|https://github.com/w3c/wot-testing/pull/536|-> https://github.com/w3c/wot-testing/pull/536 PR 536 - Use Job summary instead of PR Comment for discovery-coverage-report| 13:17:52 rrsagent, draft minutes 13:17:53 I have made the request to generate https://www.w3.org/2023/03/22-wot-pf-minutes.html kaz 13:17:59 ege: ok let's merge this PR 13:18:05 q+ 13:18:36 kaz: is there any additional configuration needed from the support team? 13:18:43 ege: no it is happening inside github 13:18:59 kaz: do we want to apply this configuration to other repositories? 13:19:09 ege: I think is just for testing 13:19:22 ... it would be nice to have 13:19:31 kaz: we can mention this change in the main call 13:19:39 ... and ask what task force leaders 13:19:54 ege: it would be nice to have it before dev test 13:20:17 kaz: it would be nicer to mention this in the main call 13:20:45 ege: just to clarify this change will only focus on testing repository 13:21:25 subtopic: PR 533 13:21:29 ege: seems a draft 13:21:42 ... not really relevant anymore after presentation 13:22:33 ... propose closing 13:22:36 ... any comments? 13:22:52 topic: issues 13:22:59 ege: no new issues 13:23:08 topic: Developer meeting 13:23:17 ege: we started writing the readme 13:23:38 ... it would be better to name the meeting to At-Risk Assertion Resolution Meeting 13:23:51 ... developer meeting feels more open to newcomers 13:23:56 ... renaming 13:24:15 ... main work to do is to update the readme 13:24:24 ... we will try to invite CG people too 13:24:44 13:24:59 ege: they are review by McCool 13:25:24 ... there is also a deck for Architecture but they are not reviewed by McCool 13:25:28 i/PR 533/kaz: If everybody is reading each Issue and PR of the wot-testing repository in detail, we don't need to explain this. However, it's not the case, so it would be nicer to mention this mechanism to everybody./ 13:25:30 q+ 13:26:45 kaz: it's ok to think TD and Architecture as seperated collections. but we need more explaination about the goal of the event and the intentions of the assertion authoer. 13:26:54 s/authoer/author/ 13:27:06 rrsagent, draft minutes 13:27:07 I have made the request to generate https://www.w3.org/2023/03/22-wot-pf-minutes.html kaz 13:27:13 ege: some of this aspects are already done 13:27:24 ... but we can do a initial introduction to both slides 13:27:45 kaz: we need to mention the w3c process required us to do that 13:30:00 ege: I'll add it 13:30:48 ege: it would be nice to have a concrete deadline 13:31:01 ... which are the new plan? 13:31:56 kaz: it is up to us, if we want to move ahead even if not all the features are resolved 13:32:33 ... we want to update the text after the transition we have to start all over again 13:33:53 ... basically all depends with the implementation status. 13:34:17 s/do that/do that. The main purpose is not checking if the implementations are validly implemented, but if the specification is implementable. Also to see the interoperability of the spec./ 13:35:14 ege: I noticed a problem with the dealine set in the slides and the one noted in the charter wg-extension-plan 13:35:51 kaz: everything should be done by the end of May 13:36:02 ... we have still the option to remove the unimplemented features 13:36:44 ... or to update the draft if we have correctly identified the at-risk features. 13:37:41 ege: what is in the slides is correct? 13:37:47 kaz: yes that is what I proposed 13:38:11 ege: it just to provide a deadline 13:39:40 kaz: but we need to take in consideration developers avaiability 13:40:11 ... the goal should be clearly explained 13:41:28 kaz: maybe it is better to use proposed deadline 13:41:29 ege: ok 13:41:41 s/use/say/ 13:41:55 s/proposed deadline/"proposed deadline"/ 13:42:23 13:43:47 q+ 13:43:59 ack k 13:44:55 ack cris__ 13:45:07 q+q+ 13:45:17 q-q- 13:45:36 cris: resolution is a little bit misleading 13:45:49 ege: what about takeways or developer guides 13:47:20 kaz: In my understanding today we should work on the goals, intention and supplement additional information to the specification text 13:47:34 ... Architecture is more difficult to understand 13:49:05 ege: I agree with the suggested structure 13:49:12 ... but I would add link to context 13:49:18 kaz: link is right 13:49:24 ... implementation report has already links 13:49:31 ... we can use it 13:51:19 Mizushima has joined #wot-pf 13:52:11 ege: I don't think I can update the slides in time with the suggestions 13:52:25 kaz: we can use architecture call and td call 13:52:40 ... we could clarify methods and goals 13:52:54 ege: is somebody willing to help ? 13:53:05 kaz: I not asking you directly 13:53:46 ege: lot of stuff to do 13:54:46 kaz: we can share the workload between each other 13:55:18 q+ 13:55:28 q- q+ 13:56:11 kaz: maybe it is better to not use slides 13:56:21 ...but better the report itself 13:57:42 ... we can consolidate existing text 13:58:35 ege: I don't have really time to finish up 13:59:58 kaz: not asking to refactor the whole google slideset 14:00:16 ... but rather how to share the editorial work 14:01:00 kaz: what if people cannot work on the document? 14:01:13 ege: everbody should do what he can 14:01:22 ack q 14:01:54 ack cris__ 14:02:14 [adjourned] 14:02:34 rrsagent, draft minutes 14:02:36 I have made the request to generate https://www.w3.org/2023/03/22-wot-pf-minutes.html kaz 14:04:58 Mizushima has left #wot-pf 16:04:15 Zakim has left #wot-pf