Meeting minutes
IRC usage
Minutes review
McCool: Backlog review and I will be out in May
McCool: minutes approved
Planning
McCool: 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.
… There is a bunch of old stuff regarding functional requirements, we should not rush things out in March in the reopening the use case
… 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.
Mizushima: Kaz has a script that did this. We assume we can convert the markdown to html
McCool: 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.
… 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.
… .. Found the perl script that does the conversion from YAML to MD
… Found the perl script that does the conversion from YAML to MD
McCool: Convert this perl script to parse to JSON then parse it to HTML
Ege: Possibly we copied it from somewhere
Mizushima: Maybe the code is the shell script does something as well
McCool: looks like the .sh is just invoking the perl script
Ege: Why convert to json when we need just html
McCool: the situation is the template might change
… Any volunteer to convert the script?
McCool: this script does not do everything we need. We need to extract the info and then place it in the template.
Mizushima, After converting we need to check the HTML file.
Ege: Going from JSON to HTML via Mustache templates
ISSUE: Convert submitted use cases from its current format to HTML
McCool: Next is task prioritization. After HTML conversion then we need to walk through and clean up the documentation.
McCool: Are these use cases ready to go?
Review of user stories
McCool: Discussion lead on github issues 320 and 319.
<McCool> can use this as a test case, but need to update to match updated template: w3c/
McCool: Task 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.
McCool: Mizushima, are you up to converting this script?
Mizushima: Will look at Kaz's script and then review.
McCool: Take a look for a week and let us know we can revisit next week.
PR Review
<McCool> w3c/
McCool: review PR 262, Propose closing
Review Issues
McCool: Review of archived csv that mapped use cases to its category. Propose moving this to the top level to close this issue
<McCool> w3c/
<McCool> w3c/
McCool: Created PR 327 with this change. this resolves issue 322
… Any Objections? None raised so created
… 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?
McCool: After reviewing the archive some more there does not seem to be anything else to move up.
<McCool> w3c/
McCool: This closes our two issues, Cleanup #313 and Reorganize #315.
<McCool> w3c/
McCool: Any objections? None raised so closing
McCool: 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.
… The stakeholder list needs to be normalized to listed once and updated to be consistent
… Converting the requirements to tasks and assigning the issue to McCool and Mizushima
… #307 is related to #318. Linking the issues.
Ege: reviewed the PR. it was moved several times. if it is fine for other task forces we can use it. #262.