11:01:47 RRSAgent has joined #wot-uc 11:01:51 logging to https://www.w3.org/2024/05/08-wot-uc-irc 11:01:53 meeting: WoT Use Cases 11:02:21 present+ Kaz_Ashimura, Tomoaki_Mizushima, Luca_Barbato, Michael_McCool 11:02:28 chair: Mizushima 11:03:08 mm has joined #wot-uc 11:03:56 Ege has joined #wot-uc 11:04:50 https://github.com/w3c/wot-usecases/blob/main/TODO/20240508.md -> Agenda 11:04:58 present+ Ege_Korkan 11:06:09 scribenick: mm 11:06:24 topic: logistics 11:06:53 mz: will be unavailable end of may 13-june 5, so would like to cancel june 5 call 11:06:59 topic: plan 11:07:34 mz: review previous plan, but luca proposed using github issue template using yaml 11:07:58 ... that discussion was not finished... would like to discuss further today 11:08:26 ... then, if time, initial discussion on req template including security categories 11:09:00 rrsagent, make log public 11:09:05 rrsagent, draft minutes 11:09:06 I have made the request to generate https://www.w3.org/2024/05/08-wot-uc-minutes.html kaz 11:09:13 mz: and, actually, functional and technical req templates fix by may 22-29 and june 12-19 11:09:20 topic: minutes review 11:09:25 -> https://www.w3.org/2024/04/24-wot-uc-minutes.html Apr-24 11:09:42 mz: (walks through minute from 4-24) 11:10:17 ... made resolution to use github issues to submit use cases, at which point luca made the proposal to use yaml for the template 11:10:41 ... not github issues will allow non-members to submit use cases 11:10:46 s/not/note/ 11:11:02 mz: no objections, minutes approved 11:11:16 topic: Github issue template using yaml 11:11:37 mz: generated an example template, based on markdown template 11:11:51 -> https://github.com/w3c/wot-usecases/blob/main/USE-CASES/use-case-template-2024.md MD-based 11:12:00 -> https://github.com/w3c/wot-usecases/issues/new?assignees=&labels=UC&projects=&template=subsection-test.yml&title=Add+new+use+case%3A+%3Ctitle%3E YAML-based 11:12:25 q+ 11:12:27 -> https://github.com/w3c/wot-usecases/blob/main/.github/ISSUE_TEMPLATE/subsection-test.yml actual YAML code 11:12:35 q+ 11:13:17 +1 11:13:36 ack mm 11:13:47 mm: suggest wording of "about" be changed to 11:13:57 [[ 11:13:58 Use this issue template to suggest a new use case to be added to the WoT standards. 11:13:58 ]] 11:14:29 s/changed to/changed/ 11:14:39 mm: "Use this issue template to suggest a new use case to be considered for driving requirements for the WoT specifications." 11:16:31 s/"Use/to "Use/ 11:16:51 q+ 11:17:49 q- later 11:19:09 mm: also, may be multiple submitters, suggest updating instructions to say separate multiple names with comments. First person is the contact person. Should also ask for an email but somehow not make it public. 11:19:10 q+ 11:19:20 ege: not sure the email is required, a lot of trouble 11:19:41 mm: I do feel it's important; we constantly have problems contacting people who submit use cases 11:19:46 ack Tomo 11:20:12 ack e 11:20:53 kaz: personally ok with publishing emails, since already public, but too much for other people. 11:20:55 q+ 11:22:03 JKRhb has joined #wot-uc 11:22:16 ack k 11:22:27 kaz: but first person should be contact 11:22:32 ack m 11:23:06 q+ 11:23:08 mm: we should get the id automatically for submitter; should warn people names may get published and associated with github id. 11:23:58 present+ Jan_Romann 11:24:00 ege: would be useful to get emails of submitters, but not make it public 11:24:25 q+ 11:24:26 mm: right. lots of people just use github occasionally and may not respond to notifications 11:24:29 ack e 11:26:26 mm: if we can't capture the email with the form, we will have to contact them out of band 11:27:01 kaz: we can hold the issue until we get an email; but we can start with github id 11:27:41 mm: right, just consider it part of the process; can't proceed with publication unless we have their email 11:28:06 ack k 11:29:07 mz: if contact person is same as submitter, and has github id, then they don't need email 11:29:24 q? 11:29:26 q+ mm 11:29:42 ack mm 11:29:43 q+ 11:29:56 I agree with mm, we should be more strict with this 11:30:11 s/I agree/Ege: I agree/ 11:32:11 +1 to mm 11:33:20 mm has joined #wot-uc 11:34:36 proposal: 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:35:26 ack k 11:35:51 rrsagent, draft minutes 11:35:52 I have made the request to generate https://www.w3.org/2024/05/08-wot-uc-minutes.html kaz 11:35:58 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:36:18 q+ 11:36:53 mm: the "What to be done" should be specifically about WoT (and say that); Stackholder -> Stakeholder 11:37:11 ack k 11:38:06 rrsagent, draft minutes 11:38:08 I have made the request to generate https://www.w3.org/2024/05/08-wot-uc-minutes.html JKRhb 11:38:28 i/suggest working/subtopic: About/ 11:38:45 i/also, may/subtopic: Submitter/ 11:38:56 rrsagent, draft minutes 11:38:58 I have made the request to generate https://www.w3.org/2024/05/08-wot-uc-minutes.html kaz 11:39:20 mm: suggest moving "gap" up, and changing "what to be done" to "summary" 11:39:30 i/suggest wording/subtopic: About/ 11:39:45 s/What to be done/subtopic: What to be done/ 11:39:47 rrsagent, draft minutes 11:39:48 I have made the request to generate https://www.w3.org/2024/05/08-wot-uc-minutes.html kaz 11:39:54 q+ mm 11:40:08 q+ 11:40:35 rrsagent, draft minutes 11:40:36 I have made the request to generate https://www.w3.org/2024/05/08-wot-uc-minutes.html kaz 11:41:53 subtopic: Target users 11:42:27 mm: target user list should have checkboxes; should make this list consistent across docs (e.g. see list in security, arch as well - different! Need to consolidate) 11:42:49 s/subtopic: What to be done/What to be done/ 11:43:00 ... should allow multiple answers 11:43:07 i|should be specifi|subtopic: What to be done| 11:43:09 rrsagent, draft minutes 11:43:11 I have made the request to generate https://www.w3.org/2024/05/08-wot-uc-minutes.html kaz 11:43:17 q+ 11:43:19 ack m 11:43:20 ack k 11:43:30 q+ 11:44:31 mm: later on, I think security and privacy categories should also use checkboxes, e.g. "Manages personal information", etc. 11:45:31 q- 11:45:33 qq+ 11:45:50 mz: we had previously discussed the content of the template, btw 11:46:07 mm: yes, sorry to reopen things, I am just noticing these issues now that I see it as a form 11:46:56 mm: although I did previously state that we need to consolidate the stakeholder list, for example. 11:48:13 kaz: suggest we update both the MD and YAML templates and make them consistent 11:48:32 ack k 11:48:32 kaz, you wanted to react to kaz 11:49:11 ege: agree with kaz that first agree this is the direction we want to take; I do agree with the YAML direction 11:49:26 ... second point is how to move further; using PRs? 11:49:28 q+ 11:50:43 s/update both the MD and YAML templates and make them consistent/once confirm the YAML-based template includes all the content from the MD-based template. Also the additional notes from the old template are also included in the YAML-based template. Then we can stat actual review (like McCool already started :)/ 11:50:50 rrsagent, draft minutes 11:50:51 I have made the request to generate https://www.w3.org/2024/05/08-wot-uc-minutes.html kaz 11:51:02 ack e 11:51:06 ack m 11:51:07 q+ 11:51:23 mm: would prefer issues or PRs; would be better to have one representation as master; may need to file issues instead of PRs. YAML has some things that are not in markdown. 11:52:24 mz: if we use yaml, then we ??? 11:52:40 (mz - please type what you mean...) 11:53:10 ack k 11:53:37 mm: we need a way to look at the YAML template, then we can file issues against it 11:54:07 +q 11:54:11 kaz: mm is talking about how to raise issues against the template itself 11:54:42 https://github.com/w3c/wot-usecases/blob/main/.github/ISSUE_TEMPLATE/subsection-test.yml 11:55:01 (thanks - remembered it was mentioned earlier) 11:55:15 kaz: mz should first update to match the MD file 11:55:20 https://github.com/w3c/wot-usecases/blob/main/USE-CASES/use-case-template-2024.md 11:55:45 s|https://github.com/w3c/wot-usecases/blob/main/.github/ISSUE_TEMPLATE/subsection-test.yml|-> https://github.com/w3c/wot-usecases/blob/main/.github/ISSUE_TEMPLATE/subsection-test.yml YAML-based template| 11:56:07 s|https://github.com/w3c/wot-usecases/blob/main/USE-CASES/use-case-template-2024.md|-> https://github.com/w3c/wot-usecases/blob/main/USE-CASES/use-case-template-2024.md MD-based template| 11:56:25 q? 11:56:28 mm: step 1, make sure yaml has everything in md; 2. archive md file; 3. use issues to suggest improvements to the yaml template 11:56:57 luca: I am fine with the current template, but do have some minor changes 11:57:19 ... note though there are ways to generate md from the yaml if we want it 11:58:06 mm: but in summary, you are ok with the yaml template being the master, right? 11:58:08 i/luca:/kaz: I've quickly skimmed both the YAML and MD, and think both have the same content. However, it seems Mizushima-san is kind of confused, so let's simply ask people to review the YAML-based template and give comments and suggestions using GitHub Issues and PRs/ 11:58:09 luca: yes 11:59:26 mz: ok, please review the templates and provide issues of PRs 11:59:51 q? 12:00:09 luca: agreed that we should just use the yaml as the master 12:00:27 mahda has joined #wot-uc 12:00:40 s/please review the templates and provide issues of PRs/please review the YAML-based template and provide Issues and PRs. 12:01:11 -> https://github.com/w3c/wot-usecases/blob/main/.github/ISSUE_TEMPLATE/subsection-test.yml YAML-based template to be reviewed 12:01:16 [adjourned] 12:01:20 rrsagent, draft minutes 12:01:21 I have made the request to generate https://www.w3.org/2024/05/08-wot-uc-minutes.html kaz 12:02:16 i|I've quickly|scribenick: kaz| 12:02:24 i/I am fine wi/scribenick: mm/ 12:02:25 rrsagent, draft minutes 12:02:27 I have made the request to generate https://www.w3.org/2024/05/08-wot-uc-minutes.html kaz 12:08:14 dape has joined #wot-uc 12:11:44 dape has joined #wot-uc 12:14:06 Ege has joined #wot-uc 12:19:24 mahda has joined #wot-uc 14:02:45 dape has joined #wot-uc 14:06:17 JKRhb has joined #wot-uc 14:13:10 dape has joined #wot-uc 14:28:07 Zakim has left #wot-uc 15:04:08 kilz has joined #wot-uc 15:05:11 kilz has left #wot-uc