14:17:38 RRSAgent has joined #wot-pf 14:17:38 logging to https://www.w3.org/2021/11/24-wot-pf-irc 14:17:44 Mizushima has joined #wot-pf 14:17:47 meeting: WoT PlugFest/Testing 14:17:52 chair: Fady 14:18:34 topic: minutes review 14:18:34 present+ Kaz_Ashimura, Fady_Salama, Kunihiko_Toumura, Michael_Lagally, Michael_McCool, Tomoaki_Mizushima 14:18:50 ryuichi has joined #wot-pf 14:18:50 fs: transfer of chairs to Fady 14:19:02 ... also met with McCool to discuss flow, tools, etc. 14:19:07 ... did that offline 14:19:09 i|transfer|-> https://www.w3.org/2021/11/17-wot-pf-minutes.html Nov-17| 14:19:37 ... also looked at PR197, merged even with error, which seems to be in the tool, not the data 14:19:54 fs: no objections to publishing minutes? 14:20:02 .. none, to be published 14:20:30 topic: repo, wiki, and github reorg 14:20:43 fs: there is a lot of old information hanging around 14:21:40 i/transfer/scribenick: McCool/ 14:21:49 ... up till now, TDs put in org's folder; but better if organize by implementation instead 14:21:52 rrsagent, make log public 14:21:56 rrsagent, draft minutes 14:21:56 I have made the request to generate https://www.w3.org/2021/11/24-wot-pf-minutes.html kaz 14:21:56 ... this aligns better with the report 14:26:28 q+ 14:26:34 mm: generally speaking good to align plugfest contributions with test data reorg 14:27:18 ack k 14:28:18 mm: still a few fixes needed to test data; also we need to define what an implementation is 14:28:52 ... I can copy the current text from the IR into a README, make a PR, and we can discuss as part of PR review 14:29:21 fs: as another point, we are discussing plugfest results using issues; but seems like it is a problem to solve 14:29:31 ... and they never get closed 14:29:44 ... was thinking we could migrate to the github wiki instead 14:30:00 ... so instead of issues, we can have wiki pages 14:31:44 mm: think about requirements; we would like to link to results for one project and for all projects for one plugfest 14:32:24 ... also, everyone needs access to wiki 14:33:01 ... or rather, just the group 14:33:51 q+ 14:33:54 ... another option is just have a directory under the plugfest with an md file for each project 14:34:07 fs: going to create an issue then to discuss 14:35:45 kaz: can discuss wiki pages, but only three levels, editor, member, public 14:36:40 mm: concerned that non-members can't document projects using wiki; md files would allow PRs from non-members 14:36:55 ... also suggest that once we have a new system we can copy all the content from the old issues and close them 14:37:11 fs: next topic and I'd like to clean up the wiki 14:38:14 mm: suggest we archive rather delete content 14:39:43 ... should create a sub-page like in main wiki 14:39:43 s/, public/, public by default/ 14:39:56 ... but definitely agree wiki needs to be cleaned up 14:40:19 s/can discuss wiki pages/can discuss permissions for wiki pages and should be able to generate a group-only wiki page/ 14:42:53 topic: Plugfest organization 14:42:59 mm: need a date first 14:43:16 ... but it seems we generally agree on Feb 14:43:26 ... but need a doodle to nail it down 14:43:51 ... then can create basic structure 14:44:05 fs: right, will do that, also set up readme, etc. 14:44:11 topic: profile testing 14:44:54 ml: would like to create profile spec that aligns with plugfest 14:45:51 mm: in general I would say profiles are more restrictive than what is done in plugfest 14:46:51 ... also we need to distinguish experimental vs. testing examples 14:47:29 rrsagent, make log public 14:47:34 rrsagent, draft minutes 14:47:34 I have made the request to generate https://www.w3.org/2021/11/24-wot-pf-minutes.html kaz 14:47:42 ml: also there is a lot of out-of-band communication to resolve how TDs should be interpreted 14:47:56 fs: how do we intend to test profiles? 14:48:01 q+ 14:48:06 ml: first, need a JSON schema or validator 14:48:21 ... that would extend TD testing 14:48:40 ... don't think we need a big machine; maybe some additional assertions 14:51:17 mm: do think the existing tools will work, but we should extend the assertion tester to use different JSONSchemas, which we need anyway for TMs 14:52:03 ... and then we can use manual assertions for corner cases that can't be automatically tested 14:52:28 ml: doing review of TD spec; current information model is not correct for TMs, 5.2 14:52:52 ... for example, forms are mandatory in TDs but not TMs 14:55:31 mm: summary of actions: PR on data directory to add impl desc; doodle for plugfest (kaz); start organizing event dir for Feb (fs); look at requirements for assertion tester to support profiles (fs) 14:55:59 q+ 14:56:23 Fady has joined #wot-pf 14:56:39 q- 14:57:22 kaz: when should we aim to finalize? 14:57:36 mm: probably two weeks from now, otherwise we get into xmas 14:57:50 ... post doodle now, decide in Dec 14 main call 14:57:53 fs: adjourn 14:58:11 rrsagent, draft minutes 14:58:11 I have made the request to generate https://www.w3.org/2021/11/24-wot-pf-minutes.html kaz 15:09:42 Mizushima has left #wot-pf 15:10:40 regrets+ Ege 15:10:41 rrsagent, draft minutes 15:10:41 I have made the request to generate https://www.w3.org/2021/11/24-wot-pf-minutes.html kaz 16:58:53 Zakim has left #wot-pf 17:16:19 kaz has joined #wot-pf