Meeting minutes
<MM drafts the agenda>
Minutes
any objections?
no
approved
TestFest preparation
<MM shows the current folder structure in the testing repo>
<MM shows readme for the December TestFest>
<MM edits the readme with the calender and WebEx details>
McCool: do we need VPN?
Toumura: for this PlugFest
we do not need VPN
… I'm ok with it
McCool: we need a section with information how the results should be submitted
<MM edits such a text in readme>
Lagally: We should be precise where should the developer place the inputs.
<kaz> 2022.07.Online
Lagally: we should provide descriptions for each test context
Ege: I did this for the July PlugFest
Kaz: We should clarify the targets
McCool: We have implementation gaps, target should be to close those gaps for all the 4 normative specs, i.e., Architecture, Profile, TD and Discovery.
Kaz: we should record this kind of decision
Kaz: I'm a bit
concerned about the iterative approach specifically this time
… how to assign people to each specification and
how to organize the testing for each specification would be
complicated. Trying iterative approach again may be fine, but it
would not work to ask you McCool to handle everything and the other
Editors just help you. We need to clarify actual assignment on who
to do what.
McCool: we need to provide more details about profile testing
Lagally: why do we need the this folder 2022.12?
McCool: mainly the
readme
… in the past we put also there the testing
results, however, its better provide everything directly into
data/input_2022
Ege: Propose that the details should be of the seperated TF. So TD test information should provided by TD repo, Profile from Profile repo, etc.
Lagally: agree with this approache
<MM edits this approach in the readme>
Lagally: contributors should also mention company names
Ege: it should be the name of the implementation / tool
McCool: for TD the results are combined, however, results for Profile and Discovery taken from the inputs
<MM edits the new introduction in the readme>
Lagally: there is a PR in the TD call about the implementation overview
https://
Lagally: would be good to merge this one in the TD call
<kaz> [adjourned]