W3C

– DRAFT –
WoT Plugfest/Testing

13 July 2022

Attendees

Present
Ege_Korkan, Fady_Salama, Jan_Romann, Kaz_Ashimura, Kunihiko_Toumura, Michael_Lagally, Michael_McCool, Philipp_Blum, Ryuichi_Matsukura, Tomoaki_Mizushima
Regrets
-
Chair
McCool
Scribe
citrullin

Meeting minutes

Minutes

<kaz> July-6

McCool: Not sure if the json pointer is solved, but I think Ege is on it.

McCool: We should record it somewhere that Ege will not be able to make the plugfest in August.

McCool: We discussed if the CG meeting should be a plugfest in August, but Ege will not be there.

McCool: Any objections publishing it? No objections. Publish.

July testfest logistics

McCool: Any objections to make the July one to a pure testfest? No objections.

McCool: The August one is going to be a plugfest.

McCool: We should confirm the time and dates. At this point we have to. Any objections confirming them? No objections.

Lagally: 2am is not a time anyone in Japan would like to work.

McCool: That's true. Kaz, do we want to move this time? We can't have a early meeting, since it conflicts with architecture.

Lagally: Wendsday is conflicting with profiles.

McCool: Let's call it tentative again and ask people for conflicts.

Kaz: Earlier would be possible, but this is 10pm in Japan. Not impossible.

(Some discussions about the timeslot details)

McCool: Next thing we should do is organizing it.

July 2022 Testfest

McCool: Let's get the timing for the July testfest and we just use the same times for the Plugfest.

Implementation reports

McCool: I haven't gotten to this part yet.

<Ege> Uncounted data schema terms

Ege: There is something about the schema. Something with the validator tool. I don't see what is really happening there.

McCool: We want to know if some assertion fails for a specific file. That is not given yet.

(Some discussion about the details of failures, how to report them back etc.)

McCool: Failures are not too bad in comparison to gaps in the validations.

<Ege> https://github.com/w3c/wot-testing/issues/360

Ege: When you validate it on the playground it shows it as implemented.

mm testing the behaviour

Philipp: I would like to know how we organize the demo on the TPAC. Should we move it into the CG?

McCool: We have to find a timeslot as well.

Kaz: We can create a md file in the github events and collect ideas/projects.

McCool: Problem is just it's not really testing or plugfest. We could create a wiki entry or on github under marketing.

Philipp: I think kaz is right here and github is the better place. So, marketing I guess.

Kaz: What is the difference between plugfest and demo?

McCool: Demos are more polished, and not as experimental.

Kaz: We have shown demos on the plugfest as well.

McCool: Not always.

Kaz: My only concern is. Do we want to discuss this on the marketing call or plugfest call? If so, that would be complicated.

McCool: Let me create an issue for this.

McCool: I was thinking about having 4 demos, 15 minutes each. We can record them, for the remote participants.

Ege: I could show a demo or the sorting line.

McCool: Who should request the slot? Me and Kaz can discuss this.

Kaz: Interoperability is the more important here. It would be nicer to have an interoperability use-case.

+1 on this from me.

McCool: I think we should start and find opportunities to connenct it.

<kaz> [adjourned]

Minutes manually created (not a transcript), formatted by scribe.perl version 192 (Tue Jun 28 16:55:30 2022 UTC).