Meeting minutes
Housekeeping
<kaz> Apr-12 minutes
Lagally: <Consensus check for notes>
Lagally: approved
Open issues
Lagally: Let's make sure we do not have duplicated issues
Lagally: for the next meeting we should have the Profile-1.0 tagged issue reviewed
Contributions
PR 382
<kaz> PR 382 - webhook properties section
Lagally: Lots of feedbacks from Ben
Lagally: Many fixes and a new section
Lagally: Only a single unsubscribe mechanism
Lagally: The observe mechanism for properties now is the same as the one used for events
Lagally: Is it ok merge?
McCool: Ok
Lagally: A remaining comment from lb
Luca: There is a line that may be omitted
Lagally: Agreed
<mlagally> w3c/
Lagally: Another PR combining the previous past PR
Lagally: All the pr impact the same section, so is better to see all the changes in a single one
Lagally: we can land the split PR or land the combined one
McCool: I'm ok with the approach
Luca: Let's squash-merge the separate PR and see the leftovers if there are
<kaz> related PR 391 - Webhook Profile: Issue 375 - rework notification section
Lagally: <PR 375 squash&merged>
PR 382
<kaz> PR 382 - webhook properties section
Lagally: I adopted the proposals from Ben
Lagally: <Adds suggestion from lb comment>
Lagally: <Resolving merge conflicts>
Lagally: Consensus on merging?
Lagally: <squash & merged>
PR 390
<kaz> PR 390 - Improving Webhook event operations
Lagally: <merge conflict resolution>
Lagally: 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.
PR 392
<kaz> PR 392 - Issue 375+376 combined
Lagally: Consensus on merging?
Lagally: Let's close w/out merging PR 390
PR 381
<kaz> PR 381 - Adding missing member "alternate" to the table
Lagally: Needs more discussion
Other smaller PRs
<kaz> PR 334 - WIP: Provide example in the new introduction section
<kaz> PR 330 - Cloud Events Message Format
Lagally: The remaining ones need more contributions
Testfest preparation
McCool: We'll have a testfest next week
McCool: We'll focus on what is at-risk section in the TD and Discovery first
Lagally: should not always deprioritise Profiles
McCool: We are on a critical path for TD and Discovery, better to get that done and move focus on Profile
Kaz: Before going into the details, we should confirm what is need for testing
… we should clarify what has to be done on this charter period and the next
McCool: We not need testing for now on profile
Lagally: What is needed to test Profiles?
McCool: it is not a requirement to test Profiles now
Kaz: We need to identify what is needed to be done according the current charter and the next for the wot-profile specification
… I do not believe Profile is ready for testing next week
Lagally: We already received feedback from Samsung, Webthings, node-wot
Lagally: If somebody wants to provide results, we can accept their reports
Kaz: we, the wot-profile task force, should clarify the testing schedule
Lagally: We should discuss in the main call who's going to take over the leadership for the task force
Luca: Do we have a tutorial on how to make the testing report?
Lagally: have a short README.md in /testing
Kaz: Regarding the guideline for testing, that's what I've been proposing to the whole group
… we don't have a concrete guideline document yet, but we can still organize a tutoring calls and I can give instructions to the whole group to the group
McCool: We'll discuss further during the testing call
meeting adjourned