12:04:55 <RRSAgent> RRSAgent has joined #wot-uc
12:04:59 <RRSAgent> logging to https://www.w3.org/2025/02/12-wot-uc-irc
12:05:11 <Zakim> Zakim has joined #wot-uc
12:08:15 <jthomas> scribenick: jthomas
12:08:26 <McCool> https://www.w3.org/2022/Talks/0322-tools-ka/#6
12:09:00 <McCool> https://w3c.github.io/scribe2/scribedoc.html
12:09:32 <jthomas> Topic: minutes review
12:10:04 <jthomas> mm: Backlog review and I will be out in May
12:10:13 <jthomas> mm: minutes approved
12:10:30 <jthomas> Topic: Planning
12:11:57 <jthomas> mm: Monthly tasks reviewed, we are in Feb and have 2 more meetings. Review a few more things through the process. Would be nice to not do the HTML conversion by hand. Create a script to convert YAML to HTML. Need access to the YAML to see if we can start this.
12:13:35 <jthomas> ... There is a bunch of old stuff regarding functional requirements, we should not rush things out in March in the reopening the use case
12:15:25 <jthomas> ... It looks like the submitted issue is in Markdown not YAML. Not sure if there is a place to export it as YAML. If we create a template in YAML and Github runs a action, this original YAML is lost.
12:16:29 <jthomas> ktoumura: Kaz has a script that did this. We assume we can convert the markdown to html
12:17:36 <jthomas> mm: We actually want to only use parts of this and extract the certain pieces to html. We can use mustache or other tools. The issue is the user story is a mixture of Github markdown and regular markdown.
12:18:16 <jthomas> ... We need some tool to extract the parts we want and parse them. The original parser converts things and has headers even if the request data is missing.
12:18:48 <Mizushima> s/ktoumura:/Mizushima/
12:19:56 <jthomas> .. .. Found the perl script that does the conversion from YAML to MD
12:20:26 <jthomas> ... Found the perl script that does the conversion from YAML to MD
12:20:40 <EgeKorkan> EgeKorkan has joined #wot-uc
12:21:14 <EgeKorkan> q+
12:21:29 <jthomas> mm: Convert this perl script to parse to JSON then parse it to HTML
12:21:36 <Mizushima> present+ Ege_Korkan
12:21:54 <jthomas> eg: Possibly we copied it from somewhere
12:22:13 <jthomas> s/eg/ek
12:22:21 <EgeKorkan> ack e
12:24:24 <jthomas> Mizushima: Maybe the code is the shell script does something as well
12:24:36 <jthomas> mm: looks like the .sh is just invoking the perl script
12:25:32 <jthomas> ek: Why convert to json when we need just html
12:25:54 <jthomas> mm: the situation is the template might change
12:26:34 <jthomas> ... Any volunteer to convert the script?
12:27:56 <jthomas> mm: this script does not do everything we need. We need to extract the info and then place it in the template.
12:28:23 <jthomas> Mizushima, After converting we need to check the HTML file.
12:29:36 <jthomas> ek: Going from JSON to HTML via Mustache templates
12:30:51 <jthomas> Issue: Convert submitted use cases from its current format to HTML
12:32:06 <jthomas> mm: Next is task prioritization. After HTML conversion then we need to walk through and clean up the documentation.
12:32:57 <jthomas> mm: Are these use cases ready to go?
12:34:10 <jthomas> subtopic: Review of user stories
12:34:43 <jthomas> mm: Discussion lead on github issues 320 and 319.
12:34:53 <McCool> can use this as a test case, but need to update to match updated template: https://github.com/w3c/wot-usecases/issues/320
12:36:12 <jthomas> mm: Taks is to use 320 to match the template so things make sense. We can manually convert the html but would like a tool. The reason to update the titles would be because they change into headers.
12:36:28 <jthomas> s/Taks/Task
12:37:04 <jthomas> mm: Mizushima, are you up to converting this script?
12:37:26 <jthomas> Mizushima: Will look at Kaz's script and then review.
12:37:41 <jthomas> mm: Take a look for a week and let us know we can revisit next week.
12:37:58 <jthomas> Topic: PR Review
12:38:29 <jthomas> mm: review PR 262, Propose closing
12:39:26 <jthomas> Topic: Review Issues
12:42:16 <jthomas> mm: Review of archived csv that mapped use cases to its category. Propose moving this to the top level to close this issue
12:43:02 <jthomas> ... Created PR 327 with this cahnge
12:43:30 <jthomas> s/cahnge/change. this resolves issue 322
12:44:15 <jthomas> ... Any Objections? None raised so created
12:45:49 <jthomas> .. We also have a few things in the archive that might be useful. We have coverage.csv that could be useful. ANy objections to move this out of Archive?
12:46:59 <jthomas> a/ANy/Any
12:49:10 <jthomas> mm: After reviewing the archive some more there does not seem to be anything else to move up.
12:50:09 <McCool> https://github.com/w3c/wot-usecases/issues/315
12:50:09 <jthomas> ... This closes our two issues, Cleanup and Reorganize #315.
12:50:53 <jthomas> s/Cleanup/Cleanup #313
12:51:29 <McCool> https://github.com/w3c/wot-usecases/issues/313
12:51:31 <jthomas> mm:  Any objections? None raised so closing
12:52:35 <jthomas> mm: Reviewing issue on notes.md. This file does not relate to the new section headers so we need to update this otherwise it is confusing.
12:53:57 <jthomas> ... The stakeholder list needs to be normalized to listed once and updated to be consistent
12:57:06 <jthomas> ... Converting the requirements to tasks and assigning the issue to McCool and Mizushima
12:57:50 <jthomas> ... #307 is related to #318. Linking the issues.
12:57:54 <EgeKorkan> q+
12:59:36 <jthomas> ek: reviewed the PR. it was moved several times. if it is fine for other task forces we can use it. #262.
13:00:06 <jthomas> rrsagent, make logs public
13:01:18 <McCool> McCool has joined #wot-uc
13:01:27 <McCool> rrsagent, make log public
13:01:36 <McCool> rrsagent, draft minutes
13:01:37 <RRSAgent> I have made the request to generate https://www.w3.org/2025/02/12-wot-uc-minutes.html McCool