W3C

– DRAFT –
WoT Plugfest/Testing

19 January 2022

Attendees

Present
Cristiano_Aguzzi, David_Ezell, Ege_Korkan, Fady_Salama, Kaz_Ashimura, Kunihiko_Toumura, Michael_McCool, Tomoaki_Mizushima
Regrets
-
Chair
Fady
Scribe
cris

Meeting minutes

PlugFest schedule

Fady: are all the features frozen?

McCool: no, we are delaying feature freeze cause there still some normative changes that need to happen

Fady: therefore should we postpone the PF ?

McCool: it depends do we see value of having it on February? or would it be better to move it in March?
… plus we are also deferring CR transition which needs a TestFest

Fady: I don't see any problem to move it
… any objections?

McCool: we could have also a second pf around June
… there we can test also Discovery and other stuff that we couldn't test this February
… probably it would be better to do a PF in June regardless to what we are deciding for this PF
… to have webhooks implemented it might be better to wait until March
… I would vote to have this PF in March
… also there are some security issues that need to be tested

Fady: I'm feeling that we should decide the date in Main call

McCool: true, let's assume for now that we are keeping February
… I'll update the PR
… where we can discuss this new schedule

Fady: aob?

Ege: there's a PR

PRs

Fady: I created a project readme template

<kaz> PR 203 - add Project readme template

McCool: where does this go?

Ege: we can also describe the workflow

McCool: agree
… there's a before and after phase in each PF

Ege: if this is an issue template
… we could leverage on Github issues templates

Fady: we thought to use issues
… and then when PF is finished I move issue content in the md file

McCool: we could use the template as an issue template

cris: we could use the discussions feature of github

McCool: or we could use PRs
… cause it would save some work from our side

Fady: yeah maybe

McCool: I would suggest to propose a workflow and then we can discuss it

Kaz: I also would like to see a concrete workflow; having a concrete md file inside the Project directory (rather than a GitHub issue) would make sense given each project has description on the project and then result from the project. note that we should add links from the summary.md file to each project's result under RESULTS subdirectory.

McCool: maybe in the sammary we could link to project md files
… the current document content is a bad example
… let's do it properly next time
… it would beneficial to indicate which projects were successful

Fady: should I merge PR 203?

McCool: ok and then have another one that describe the process

Fady: aob?

AOB

McCool: I'm trying to integrate WoT with HomeAssistant
… if people are interested in that ping me

Fady: what should be the topic about the next PF? testing Tds? or random wot projects?

McCool: we can do two events -> one for testing and one for interesting projects

<kaz> [adjourned]

Minutes manually created (not a transcript), formatted by scribe.perl version 185 (Thu Dec 2 18:51:55 2021 UTC).