Meeting minutes
Minutes
<kaz> July-16
Call to approve the previous minutes
Quick items
Any new topics on items or notices?
TPAC Planning
Wiki for WoT F2F and Plugfest during TPAC 2025
Official web page is now up, please review. Registration is now live so please do so ASAP
Lets get an agenda finalized by the end of September.
<kaz> Friday schedule
Sebastian: There was one request about the community group having meetings on Friday, we will try to have a joint meeting with them. Issues with timezones might cause issues with people joining in Europe. 8:30 - 10am CEST
<kaz> 16:30 JST in various timezones
<EgeKorkan> WoT CG's Calendar entry
Kaz: Friday schedule added to IRC to review
<kaz> Friday schedule
Sebastian: There is a spot Saturday for the WoT Interest group, the community group meeting is 8:30 - 10am CEST. We might use this partially for that joint meeting.
Ege: its the only CG spot
Sebastian: lets make more decisions on this in the next few week.
Plugfest
Sebastian: starting plugfest Saturday
… have a slot in the breakout session for the demos
… We are being asked to provided an issue if we need a breakout session, so we plan on making two. One for Smart Cities and the other for Demos.
Kaz: Have been working with the event team on the room for the plugfest. We have not found one yet, so I will check in again.
Sebastian: would be nice if the room is the same room for the whole TPAC. This way we can leave items there etc.
Schedule/Holidays
<kaz> Holidays and Events
Sebastian: Kaz out until the 15. TD call canceled.
… MK Out until the 15th
Cancelations
<kaz> TD / Binding call will be canceled on 31 July 2025
<kaz> all WoT calls will be canceled in week 11-15 August 2025
Publication Schedule
WoT WG
Sebastian: deliverables need to be reviewed. PR's need checked
<kaz> wot PR 1234 - Updates for TD and Binding Registry schedules
Ege: Charter expires Sep 3rd, we should have a consensus in the main call. This is the same for the binding registry. There is no documentation phase, and it goes right to the registry.
Sebastian: The most important dates are the September ones. They are still realistic for publishing the first working draft.
Sebastian: after Candidate we can go to registry
McCool: We work on the draft into a single charter. Other groups do this differently. Is it worthwhile to do it in one charter then recharter to finish.
Kaz: Which version or spec should be published within a period is defined in the charter itself. We can publishing 2.0 WD before September. And then we can work on the rest in the next charter period.
Sebastian: I'm ok with doing with this proposal and suggest merge this PR.
Kaz: This is a good initial point
PR #1234 Merged.
WoT IG
<kaz> wot PR 1235 - Update ig-schedule.md - UCR
McCool: PR 1235, We discussed some updates to the user stores. We need to call for resolution on this next week and give a week for review.Then the document will be done besides formating.
… Draft by mid-august. So do two drafts with 2 week review period. Make changes and 2nd draft if there are changes. 2 week review then publsh.
… Would like to get the UCR done by TPAC
Sebastian: Is it ok to merge today?
McCool: Its ok to merge, but next week expect a CTR for the security review for a week review.
Sebastian: Any objection on the merge or the new dates?
No objections PR 1235 merged.
WoT WG - revisited
<kaz> wot PR 1233 - Update schedule for WoT Profiles
Sebastian: Have a pull request PR 1233 for the profile. There are two entries to have the Notes published July 31 and the Req publication Oct 31.
… I think we should stick with the dates, but I asked if it was realistic as a comment on the PR.
… Any obj to merging this PR?
No objections PR 1233 merged.
Policies
Sebastian: Next up is PR 1229
McCool: I have not have time to work this one. Right now the situation is the process is documented in 2 locations. One is in the readme and the other is this PR. This question is where is the best place to put the req document. The current document has a lot of comments so it needs some review. I focused the UCAR to get it completed. If someone else wants to make suggestions please make a new PR as I was going to start over on this one. This
… document issues is it talks about the process not the reason.
… I think we can close without merging and create a new PR. I do no thing we should not have a policy document. We need one.
Sebastian: I think the policy should be considered in the new charter. And then we can decide what to pull from the current and modify the new one to fill the gaps
McCool: we should talk this at TPAC. I think this would be good to have a draft of what we want. Then from there figure it out from there.
Publication Schedule - revisited
WoT WG - revisited
Sebastian: the discovery is on the schedule and it was not done.
McCool: we should remove it and then revisit as some topics were not covered.
Charter
Sebastian: After vacation we need to have a discussion about the things we want in the new charter
… Hope to have it drafted by middle of Nov and discuss at TPAC and use it for the next period.
Use Case Discussion
Sebastian: meeting took place today.
McCool: disccused a new PR and some User stories. EK pointed out some places we need some edits.
… It needs some restructuring to move user stores up. Making a CFR next week for review. Then the UCR task force can review. Then after 2 weeks we can publish a draft for review. That brings us to mid September. My plan is to get the second draft by end of August.
Kaz: Given we are thinking on the second charter and how the working groups work in there. Instead of discussing the updates please think about the content.
McCool: Detailed requirements should be managed by the TF. We were discussing the def of requirement and how much detail is needed in the user stories. We have been trying to define the terms. There is a place for the UCR in the new process but its not the end of story.
Kaz: it might make sense to have more discussion on the main call. Also discuss during TPAC.
McCool: The only place requirement is mentioned in that document, but we do not want all of our requirements in there.
… The purpose of a use case, is to show the system and how WoT fits in and what the benefits are.
Meetups
WoT CG
Sebastian: CG meetup happened
Ege: Next meeting is TBD
WoT JP CG
Sebastian: JP CG updates?
Mizushima: No news, but would like to announce the plugfest to the members. I need more details for this.
Sebastian: at the moment we can point at the Wiki page, but we probably need to have a place to collect Topics.
Smart Cities
Sebastian: Smartcities Updates?
Kaz: The last meeting was July 7th. No next meeting slot was found so canceled Aug meeting.
Cloud Edge
Sebastian: Cloud Edge Updates
McCool: Driven by China Mobile and no new news
Liaisons
Sebastian: Any updates that need shared with the group?
Ben: Made good progress in the profiles call. Need a lot of work have several PR's and still trying to have something in draft by end July. Can we meet next week during the Plugfest call?
[adjourned]