Meeting minutes
Minute Review
<kaz> June-15
McCool: No problem with the mins, we can publish these
Review the Testfest Minutes
<kaz> Day 1
McCool: no problems with day one, we publish
<kaz> Day 2
McCool: no problem with day 2 mins, publishing
McCool: I see a couple of typos, otherwise good. Publishing after fixing typos
McCool: Minutes ok, publishing
McCool: We should specify that we need to consider how to deal with multiple implementations that come from the same organization
Kaz: *updates action note*
<kaz> [[ group to consider how to deal with results from multiple implementations which are based on one specific code base and multiple implementations from one organization (including the results from Ver. 1.0 implementation results)]]
McCool: Other than typos, we can publish
Review PRs
PR 354
<kaz> PR 354 - Add tinyiot test results to input_2022
McCool: This is a simple PR that we can simply merge
… merged
PR 355
<kaz> PR 355 - add todos for action titles and scopes
McCool: This PR is trying to add missing features, so I will merge it and update todo-list
… merged
Next Plugfest/Testfest Logistics
McCool: I am going to add a new directory for the next Plugfest
… It should be during July 18-22
… tentatively same times as last Testfest
McCool: *Creates placeholder README.md*
Implementation Reports
McCool: I have updated some my tools and done some fixes
<kaz> i/topic: Next Testfest (revisited)/
Next Testfest (revisited)
Kaz: I just looked at the calendar and realized at that time probably many japanese members will not be able to join
McCool: Can you remember to bring it up next main call?
Kaz: Sure, sorry for not noticing earlier
<kaz> (Kaz has added that to the main call agenda for June 29.)
Implementation Reports (revisited)
McCool: I just wanted to tell every one that if you want to write something complex in the html of wot thing description, please do it in a div and not in a span
McCool: * Generates updated implementation report*
McCool: We are making some progress, I didn't finish my own volunteered fixes, but I am done with the tooling so I can do it now
… we are mostly missing volunteers for tm-assertions
Lagally: I have the feeling that tm is not ready and not well tested. I am afraid that we put something not fully finished in the spec
McCool: TM is stable, but we can bring the topic up in the next call
Discovery Implementation Report
McCool: There are things that need to be fixed, Farshid is working on that
Kaz: I just wanted to remind you that we should merge the updates with the main branch on github, but let's visit that point again later at the end of this call.
McCool: TD and Discovery Implementation Report are up to date and merged
To Dos
McCool: I will go ahead and make placeholders for implementation descriptions and then ask people to fix them if something is wrong.
… same with testimonials
"Policy" Assertions
McCool: Assertions about security assertions are hard to test
… We assume that they are treated as manual assertions
… but we need to keep in mind that some of the assertions are not really features but policies of usage
Kaz: Can we start to ask implementers to start sending their template.csv and manual.csv? The point is we should clarify who should do what for the next steps.
McCool: I need to look at what is missing from whom. I will do that offline
<kaz> [adjourned]