10:58:52 RRSAgent has joined #wot-uc 10:58:57 logging to https://www.w3.org/2024/05/15-wot-uc-irc 10:58:58 meeting: WoT Use Cases 10:59:10 present+ Kaz_Ashimura, Tomoaki_Mizushima, Luca_Barbatos 10:59:14 chair: Mizushima 11:02:04 agenda: https://github.com/w3c/wot-usecases/blob/main/TODO/20240515.md 11:05:21 q+ 11:05:41 q- 11:05:48 scribenick: luca_barbato 11:06:05 topic: Minutes 11:06:38 regrets+ Ege 11:08:06 present+ Michael_McCool 11:08:47 s/Minutes/Logistics 11:09:04 mm has joined #wot-uc 11:09:24 miz: I'd cancel the 5th June call, since I'll be in vacation 11:10:17 [[[ 11:10:21 [No changes from the previous plan on 8 May 2024 11:10:21 May-15: Fix Github Issue template using YAML and Initial discussion on Requirements Template 11:10:21 May-22 and May-29: Fix basic Functional Requirements Template 11:10:21 June-12 and June-19: Fix basic Technical Requirements Template 11:10:24 ]]] 11:10:40 miz: Any objection for the next meeting plans? 11:11:09 11:11:30 topic: Minutes 11:11:38 -> https://www.w3.org/2024/05/08-wot-uc-minutes.html May-9 11:11:42 s/9/8/ 11:14:12 miz: Anything to change for the past minutes? 11:14:21 11:14:31 subtopic: Discussion point 11:14:48 [[[ 11:14:55 Github issue template using YAML 11:14:56 confirmed the YAML-based template includes all the content from the MD-based template. 11:14:56 additional notes from old template are also included in YAML-based template. 11:14:56 further improvement for the YAML template to be done using GitHub Issues and PRs 11:14:57 Question about the need for submitter's email address (discussion to be continued) 11:14:57 RESOLUTION: While not required for submission of a use case for consideration, the email of the submitter should be requested and recorded before a use case is published in case followup is necessary. These emails will be kept private and only used for communication on the use case. 11:15:01 ]]] 11:15:23 miz: Anybody wants to add additional discussion points for today? 11:15:57 11:16:37 topic: Fix YAML-based issue template 11:17:09 subtopic: Issue #281 11:17:25 q+ 11:18:04 lb: the issue is closed because the new issue template addresses it? 11:18:08 miz: Yes 11:18:17 i|the issue|-> https://github.com/w3c/wot-usecases/issues/281 Issue 281 - Mention Possibility of External Submissions via Issues| 11:18:23 rrsagent, make log public 11:18:26 rrsagent, draft minutes 11:18:28 I have made the request to generate https://www.w3.org/2024/05/15-wot-uc-minutes.html kaz 11:18:35 ack lu 11:18:40 subtopic: Issue #288 11:18:56 miz: mm found some typos 11:19:48 miz: I fixed them with the PR #292 11:19:53 https://github.com/w3c/wot-usecases/pull/292 11:20:37 miz: is it ok to merge? 11:20:47 11:21:19 q+ 11:23:09 lb: Would be good to always use rebase-and-merge so we keep the history linear 11:23:16 mm: No objection 11:23:37 q+ 11:23:58 ack lu 11:25:18 kaz: I'm all also ok with rebase-merge 11:25:43 ... We should suggest and make it a policy 11:26:06 mm: We can discuss it in the main call, but we can use it on the UC task force for now 11:26:45 subtopic: Issue #289 11:26:54 https://github.com/w3c/wot-usecases/issues/289 11:27:11 s/rebase-merge/rebase-merge, but also ok with ordinary merge for this PR since it's not problematic/ 11:27:27 miz: I agree we have multiple lists of stakeholders and we should keep a single list 11:28:13 mm: The security TF has the most developed list, but the current usecases is using the other list, so if we pick the Security one we need to update the names in them 11:28:26 s/We should suggest and make it a policy/If we want to use rebase instead of merge, probably we should discuss that during the main call and suggest we use rebase for clearer log as our policy./ 11:28:47 miz: Iuca created a PR to address the UI concern 11:28:53 s/Iuca/Luca/ 11:29:19 mm: Would be nice to link to the Security guideline with the description of the other stakeholders 11:29:29 s|https://github.com/w3c/wot-usecases/issues/289|-> https://github.com/w3c/wot-usecases/issues/289 Issue 289 - [UC Template] Stakeholders| 11:29:31 ... let's compare the two lists 11:32:10 -> https://www.w3.org/TR/wot-security/#wot-threat-model-stakeholders WoT Security Note - 3.2.1 WoT Primary Stakeholders 11:32:11 q+ 11:32:39 ack k 11:32:50 mm: 11:33:05 q+ 11:33:26 https://github.com/w3c/wot-usecases/issues/new?assignees=&labels=UC&projects=&template=sample-usecase-template.yml&title=Add+new+use+case%3A+%3Ctitle%3E 11:33:46 https://github.com/lu-zero/wot-usecases/issues/new?assignees=&labels=UC&projects=&template=subsection-test.yml&title=Add+new+use+case%3A+%3Ctitle%3E 11:34:02 mm: Can we see a preview 11:34:37 s|https://github.com/w3c/wot-usecases/issues/new?assignees=&labels=UC&projects=&template=sample-usecase-template.yml&title=Add+new+use+case%3A+%3Ctitle%3E|-> https://github.com/w3c/wot-usecases/issues/new?assignees=&labels=UC&projects=&template=sample-usecase-template.yml&title=Add+new+use+case%3A+%3Ctitle%3E Preview| 11:34:40 rrsagent, draft minutes 11:34:41 I have made the request to generate https://www.w3.org/2024/05/15-wot-uc-minutes.html kaz 11:34:55 q+ 11:36:42 q? 11:36:50 mm: I'd rather have a checklist with a link for each item to their description 11:37:07 lb: Ok, can be done 11:37:43 kaz: We should try checkboxes we can try it, for the link to the definitions we can do that later 11:40:02 lb: Checkboxes can be implemented via https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema#checkboxes 11:40:46 s/We should try checkboxes we can try it/Given McCool suggested we use checkboxes within his original Issue, we should try checkboxes as the style/ 11:41:00 rrsagent, draft minutes 11:41:01 I have made the request to generate https://www.w3.org/2024/05/15-wot-uc-minutes.html kaz 11:42:28 q? 11:42:30 ack k 11:42:46 lb: I'll update the PR later today 11:44:21 rrsagent, draft minutes 11:44:23 I have made the request to generate https://www.w3.org/2024/05/15-wot-uc-minutes.html kaz 11:44:29 miz: Luca will change the PR while Michael will provide the links with the definitions and the up to date list 11:46:17 subtopic: Issue 286 11:46:29 -> https://github.com/w3c/wot-usecases/issues/286 Issue 286 - [UC Template] "Submitter" should indicate Real Name(s) 11:46:46 q+ 11:47:14 ack k 11:47:48 q+ 11:48:51 kaz: Since Ege is unavailable we can discuss the PR next week 11:49:05 ack k 11:49:18 ... and We can address the problem with emails and Real Names separately 11:49:33 mm: Agreed 11:49:48 q+ 11:50:18 ack k 11:50:58 mm: I can comment on Ege PR right now 11:51:16 i/I can/kaz: how to proceed with this issue?/ 11:51:23 i/how to/scribenick: kaz/ 11:51:31 subtopic: Issue #287 11:51:34 i/I can/scribenick: luca_barbato/ 11:51:54 miz: I agree with Michael opinion 11:52:15 i|I agree|-> https://github.com/w3c/wot-usecases/issues/287 Issue 287 - [UC Template] "What to be done?" is ambiguous| 11:53:24 q+ 11:54:04 ack k 11:54:07 mm: I'm updating the order in the issue 11:54:39 kaz: If everybody is ok with that, we'll use that order 11:55:18 lb: Since we all agree, I'd go with that order. 11:55:45 i|If eve|-> https://github.com/w3c/wot-usecases/issues/287#issuecomment-2112328535 McCool's comment| 11:55:49 11:55:57 [[ Summary, Why WoT, Gaps, Description ]] 11:55:57 1. sumarry 2. Why WoT 3.Gaps 4.Description 11:56:04 s/[[ Summary, Why WoT, Gaps, Description ]]// 11:56:26 miz: I'd close this meeting 11:57:03 11:57:27 s/1. sumarry 2. Why WoT 3.Gaps 4.Description/1. summary, 2. Why WoT, 3.Gaps, 4.Description/ 11:57:35 rrsagent, draft minutes 11:57:36 I have made the request to generate https://www.w3.org/2024/05/15-wot-uc-minutes.html kaz 12:08:38 dape has joined #wot-uc 12:24:06 Ege has joined #wot-uc 12:36:31 Ege has joined #wot-uc 13:22:54 kaz has joined #wot-uc 13:34:00 JKRhb has joined #wot-uc 13:34:12 JKRhb has joined #wot-uc 13:34:12 Ege has joined #wot-uc 13:34:12 ktoumura has joined #wot-uc 13:34:12 benfrancis has joined #wot-uc 13:37:41 JKRhb has joined #wot-uc 13:37:41 Ege has joined #wot-uc 13:37:41 ktoumura has joined #wot-uc 13:37:41 benfrancis has joined #wot-uc 13:59:47 Zakim has left #wot-uc 14:04:33 dape has joined #wot-uc