10:58:39 RRSAgent has joined #wot-profile 10:58:43 logging to https://www.w3.org/2023/04/19-wot-profile-irc 10:59:07 luca_barbato has joined #wot-profile 10:59:53 meeting: WoT Profile 11:02:34 present+ Kaz_Ashimura, Luca_Barbato, Michael_McCool 11:03:33 Mizushima has joined #wot-profile 11:05:45 present+ Tomoaki_Mizushima 11:06:31 present+ Michael_Lagally 11:06:36 chair: Lagally 11:07:40 mlagally has joined #wot-profile 11:08:45 scribenick: luca_barbato 11:09:11 topic: Housekeeping 11:10:10 q+ 11:10:15 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Profile_WebConf#Profile_-_April_19th.2C_2023 11:12:16 ml: 11:12:22 ml: approved 11:12:26 i|Con|-> https://www.w3.org/2023/04/12-wot-profile-minutes.html Apr-12 minutes| 11:12:31 ack k 11:12:35 rrsagent, make log public 11:12:41 rrsagent, draft minutes 11:12:42 I have made the request to generate https://www.w3.org/2023/04/19-wot-profile-minutes.html kaz 11:12:56 topic: Open issues 11:13:10 ml: Let's make sure we do not have duplicated issues 11:14:43 ml: for the next meeting we should have the Profile-1.0 tagged issue reviewed 11:14:59 topic: Contributions 11:15:26 https://github.com/w3c/wot-profile/pull/382 11:15:34 subtopic: PR 382 11:15:45 s|https://github.com/w3c/wot-profile/pull/382|| 11:15:56 ml: Lots of feedbacks from Ben 11:16:18 i|Lots|-> https://github.com/w3c/wot-profile/pull/382 PR 382 - webhook properties section| 11:16:30 ml: Many fixes and a new section 11:17:05 ml: Only a single unsubscribe mechanism 11:18:31 ml: The observe mechanism for properties now is the same as the one used for events 11:19:28 ml: Is it ok merge? 11:19:32 mm: Ok 11:19:49 ml: A remaining comment from lb 11:20:06 lb: There is a line that may be omitted 11:20:10 ml: Agreed 11:21:40 https://github.com/w3c/wot-profile/pull/390 11:21:41 ml: Another PR combining the previous past PR 11:22:17 ml: All the pr impact the same section, so is better to see all the changes in a single one 11:23:47 ml: we can land the split PR or land the combined one 11:24:28 mm: I'm ok with the approach 11:24:39 q+ 11:25:46 lb: Let's squash-merge the separate PR and see the leftovers if there are 11:27:21 -> https://github.com/w3c/wot-profile/pull/391 related PR 391 - Webhook Profile: Issue 375 - rework notification section 11:27:22 ml: 11:27:56 subtopic: PR 382 11:28:11 ml: I adopted the proposals from Ben 11:28:23 i|I ad|-> https://github.com/w3c/wot-profile/pull/382 PR 382 - webhook properties section| 11:28:58 ml: 11:30:07 ml: 11:31:14 ml: Consensus on merging? 11:32:06 ml: 11:32:16 subtopic: PR 390 11:32:25 ml: 11:35:07 ml: The rebase may take more time to be allotted now, let's see if we can manage in the next 5 minutes to resolve it. 11:35:49 i|conf|-> https://github.com/w3c/wot-profile/pull/390 PR 390 - Improving Webhook event operations| 11:40:43 subtopic: PR 392 11:40:45 ml: Consensu on merging? 11:41:02 s/ensu/ensus 11:41:16 i|Con|-> https://github.com/w3c/wot-profile/pull/392 PR 392 - Issue 375+376 combined| 11:42:23 ml: Let's close w/out merging PR 390 11:42:58 subtopic: PR 381 11:43:07 ml: Needs more discussion 11:43:16 subtopic: PR 334 11:43:21 i|Need|-> https://github.com/w3c/wot-profile/pull/381 PR 381 - Adding missing member "alternate" to the table| 11:44:17 q+ 11:44:22 ack l 11:45:35 s/PR 334/Other smaller PRs/ 11:46:10 -> https://github.com/w3c/wot-profile/pull/334 PR 334 - WIP: Provide example in the new introduction section 11:46:32 ml: The remaining ones need more contributions 11:46:40 i|The rema|-> https://github.com/w3c/wot-profile/pull/330 PR 330 - Cloud Events Message Format| 11:46:43 topic: Testfest preparation 11:47:14 mm: We'll have a testfest next week 11:48:29 mm: We'll focus on what is at-risk section in the TD first 11:48:49 s/TD/TD and Discovery/ 11:49:32 ml: should not always deprioritise Profiles 11:50:04 mm: We are on a critical path for TD and Discovery, better to get that done and move focus on Profile 11:50:11 q+ 11:51:08 q+ 11:52:22 kaz: Before going into the details, we should confirm what is need for testing 11:52:44 .. we should clarify what has to be done on this charter period and the next 11:53:10 mm: We not need testing for now on profile 11:53:18 ml: What is needed to test Profiles? 11:53:34 mm: it is not a requirement to test Profiles now 11:54:24 kaz: We need to identify what is needed to be done according the current charter and the next for the wot-profile specification 11:54:36 .. I do not believe Profile is ready for testing next week 11:55:48 ml: We already received feedback from Samsung, Webthings, node-wot 11:56:08 q+ 11:57:36 ml: If somebody wants to provide results, we can accept their reports 11:58:00 kaz: we, the wot-profile task force, should clarify the testing schedule 11:58:45 ml: We should discuss in the main call who's going to take over the leadership for the task force 11:59:35 lb: Do we have a tutorial on how to make the testing report? 12:00:23 ml: have a short README.md in /testing 12:00:28 q+ 12:00:32 ack k 12:00:33 ack l 12:00:34 q+ 12:01:04 kaz: Regarding the guideline for testing, that's what I was proposing for the whole group 12:01:28 .. we can organize a tutoring calls and I can give instructions to the whole group to the team 12:01:43 s/I was/I've been/ 12:01:51 mm: We'll discuss futher for the testing call 12:01:51 s/for the whole/to the whole/ 12:02:24 s/we can or/we don't have a concrete guideline document yet, but we can still or/ 12:02:33 s/to the team/to the group/ 12:02:47 s/futher/further/ 12:02:54 s/for the te/during the te/ 12:03:01 meeting adjourned 12:03:02 [adjourned] 12:03:07 luca_barbato has left #wot-profile 12:03:11 s/[adjourned]// 12:03:15 rrsagent, make log public 12:03:18 rrsagent, draft minutes 12:03:20 I have made the request to generate https://www.w3.org/2023/04/19-wot-profile-minutes.html kaz 13:12:29 Mizushima has left #wot-profile 14:01:52 Zakim has left #wot-profile