12:03:20 <RRSAgent> RRSAgent has joined #wot
12:03:25 <RRSAgent> logging to https://www.w3.org/2023/06/20-wot-irc
12:03:41 <kaz> meeting: WoT Next Charter Detailed Planning Session
12:03:56 <sebastian> sebastian has joined #wot
12:04:22 <McCool> McCool has joined #wot
12:04:31 <mjk> mjk has joined #wot
12:04:49 <kaz> present+ Kaz_Ashimura, Sebastian_Kaebisch, Ege_Korkan, Michael_McCool, Kunihiko_Toumura, Michael_Koster, Tomoaki_Mizushima
12:05:52 <kaz> s/Session/Session - Day 1/
12:06:00 <kaz> present+ Ben_Francis
12:06:06 <kaz> agenda: https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf/2023_WoT_Next_Charter_Detailed_Planning
12:07:39 <kaz> q+
12:09:23 <kaz> topic: Agenda outline
12:09:39 <kaz> kaz: what do you mean by "PR Clean-up"?
12:09:55 <kaz> ... we can quickly skim the remaining PRs to see which to be discussed
12:09:56 <ktoumura> ktoumura has joined #wot
12:10:07 <kaz> ... but should not dive into the technical details as the starting point
12:10:10 <kaz> sk: agree
12:10:30 <McCool> topic: agenda planning
12:10:35 <kaz> scribenick: McCool
12:10:44 <McCool> kaz: suggest defer PR merging and discussion
12:10:48 <kaz> i/what do/scribenick: kaz/
12:11:05 <McCool> seb: agree, let's try to avoid deep diving on technical matters
12:11:31 <McCool> seb: also we need to arrange the agenda so topics are scheduled when people are available
12:11:33 <sebastian> https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf/2023_WoT_Next_Charter_Detailed_Planning
12:11:36 <kaz> s/topic: Agenda outline//
12:11:50 <kaz> s/kaz: what do you mean by "PR Clean-up"?//
12:12:00 <kaz> s/... we can quickly skim the remaining PRs to see which to be discussed//
12:12:00 <McCool> ege: also want to mention we have been working on some slides for some topics, see: https://docs.google.com/presentation/d/1Ko1mLp4LHAXuWJuIF6oG8IG8wBZto2F1_UIGZFpznDc/edit?usp=sharing
12:12:20 <kaz> s/... but should not dive into the technical details as the starting point//
12:12:27 <kaz> s/sk: agree//
12:12:34 <kaz> rrsagent, make log public
12:12:37 <McCool> mm: suggest we should not be shy about giving people homework if necessary also
12:12:39 <kaz> rrsagent, draft minutes
12:12:40 <RRSAgent> I have made the request to generate https://www.w3.org/2023/06/20-wot-minutes.html kaz
12:12:47 <McCool> seb: (shows first draft of agenda)
12:13:50 <McCool> ... today, at least scan PRs; talk about "working mode" and timeline; wed, versioning, TD topics, Bindings; Thurs, discovery, liaisons; Friday, profile
12:13:53 <McCool> q+
12:13:59 <kaz> ack k
12:14:02 <luca_barbato> luca_barbato has joined #wot
12:14:06 <kaz> present+ Luca_Barbato
12:14:09 <kaz> rrsagent, draft minutes
12:14:10 <RRSAgent> I have made the request to generate https://www.w3.org/2023/06/20-wot-minutes.html kaz
12:14:16 <Ege> q+
12:14:35 <kaz> chair: Sebastian/McCool
12:15:16 <kaz> i|shows first|(Sebastian's slides tbd@@@)|
12:15:17 <kaz> rrsagent, draft minutes
12:15:18 <RRSAgent> I have made the request to generate https://www.w3.org/2023/06/20-wot-minutes.html kaz
12:15:32 <kaz> q+
12:15:37 <kaz> ack mc
12:15:42 <McCool> ack m
12:15:52 <McCool> mm: suggest adding policy discussion
12:16:00 <McCool> ege: want to understand goal of this week
12:16:13 <McCool> ... is the goal to edit the details doc, or something else?
12:16:29 <kaz> ack e
12:16:40 <McCool> seb: goal is to decide how the group will run during the new charter
12:17:02 <McCool> ... for example, how many meetings, what task forces and which topics in each, and so forth
12:17:10 <McCool> ... would like to optimize our work
12:17:26 <McCool> ... would like to improve the process itself
12:17:45 <McCool> ... for example, are proposals to use github more for decisions
12:18:01 <McCool> ... also, we have a long list of topics and features, we need to prioritize
12:18:05 <McCool> q?
12:18:29 <McCool> ... also need to work on policy of who makes decisions, who merges PRs, etc.
12:19:11 <McCool> kaz: basically agree, but working mode and timeline can be discussed at the conclusion of this meeting
12:19:24 <McCool> ... think that should be moved to Friday as "next steps"
12:19:41 <McCool> ... also, policy discussion is very important
12:19:43 <McCool> q+
12:19:46 <McCool> ack k
12:20:46 <kaz> q+
12:20:57 <McCool> mm: also think we need to discuss how to deal with requirements and use cases
12:21:26 <kaz> ack m
12:21:27 <McCool> kaz: use cases might be easier than policies, so suggest doing that first
12:21:28 <kaz> ack k
12:21:52 <McCool> seb: so enough for today, let's get started
12:25:04 <McCool> mm: for policies, suggest wot versioning, async decision making, public communication, as a start
12:25:18 <McCool> seb: how much time will TD and binding take?
12:25:38 <McCool> ege: are a number of topics in slides and work items
12:25:59 <McCool> ... two hours should be enough if we avoid deep diving and look at priorities
12:26:22 <McCool> seb: would give an overview of intended features, and possibly amount of effort, and prioritize
12:26:48 <McCool> q?
12:26:51 <McCool> q+
12:27:35 <McCool> mm: working on requirements will help us prioritize
12:28:21 <McCool> seb: so think two hours is enough for TD/Binding; some discussion may have to wait until Friday, e.g. interaction of Profile and TD via defaults
12:29:25 <kaz> q+
12:29:35 <kaz> ack m
12:30:19 <McCool> mm: think we do Liaisons first on Thursday
12:31:02 <McCool> kaz: liaisons should be focused on need for W3C; probably need at least 1h
12:31:14 <McCool> seb: any topics to share?
12:31:49 <McCool> kaz: yes, digital twin interest group being launched, we need to also talk about other W3C groups we need to work with
12:31:53 <kaz> q+
12:32:04 <McCool> q?
12:32:05 <McCool> ack k
12:32:21 <McCool> kaz: don't we need to talk about Arch?
12:32:50 <McCool> seb: let's do that on Friday
12:33:29 <McCool> seb: ben, you prepared some slides for profile, how much time do you need?
12:33:33 <McCool> ... and for arch?
12:33:40 <McCool> mm: I can do; 30m enough
12:33:55 <sebastian> q?
12:35:24 <McCool> topic: Charter PR cleanup
12:35:47 <McCool> q+
12:35:53 <McCool> seb: we still have 14 open
12:36:07 <McCool> ... some belong to profile discussion
12:36:54 <kaz> i|we still|-> https://github.com/w3c/wot-charter-drafts/pulls Remaining PRs on wot-charter-drafts
12:37:01 <kaz> rrsagent, draft minute
12:37:01 <RRSAgent> I'm logging. I don't understand 'draft minute', kaz.  Try /msg RRSAgent help
12:37:09 <kaz> s/rrsagent, draft minute//
12:37:12 <kaz> rrsagent, draft minutes
12:37:13 <RRSAgent> I have made the request to generate https://www.w3.org/2023/06/20-wot-minutes.html kaz
12:37:34 <McCool> mm: suggest we just call out the ones that need more discussion and merge the rest
12:38:06 <McCool> ... and 92 and 93 are two options, so need to pick
12:39:00 <kaz> q?
12:39:02 <kaz> ack m
12:40:52 <McCool> mm: I was talking about PR numbers
12:41:17 <kaz> -> https://github.com/w3c/wot-charter-drafts/pull/94 PR 94 - Diagram of high-level relationships between WoT documents
12:41:26 <McCool> seb: ok, let's go through them to make sure
12:41:32 <benfrancis> q+
12:41:44 <kaz> s|-> https://github.com/w3c/wot-charter-drafts/pull/94 PR 94 - Diagram of high-level relationships between WoT documents||
12:41:45 <kaz> -> https://github.com/w3c/wot-charter-drafts/pull/94 PR 94 - Diagram of high-level relationships between WoT documents
12:41:48 <McCool> seb: PR 94 is nice chart
12:42:01 <kaz> i|https|subtopic: PR 94|
12:42:31 <McCool> ... ok to merge?
12:43:01 <McCool> mm: yes, and let's not get too hung up on small issues, this is only a first draft, and also work items are only provisional
12:43:05 <McCool> seb: merged
12:43:11 <McCool> seb: PR 90
12:43:25 <kaz> i|seb: PR 90|subtopic: PR 90|
12:43:26 <McCool> ben: probably superceded by 92 and 93
12:43:38 <McCool> seb: ok, let's discuss it when we discuss those
12:43:45 <McCool> seb: PR 86
12:43:49 <kaz> i|prob|-> https://github.com/w3c/wot-charter-drafts/pull/90 PR 90 - Reword updated profiling mechanism details|
12:44:01 <McCool> ... is typo, removed mention of normative deliverable for binding
12:44:15 <sebastian> https://github.com/w3c/wot-charter-drafts/pull/86
12:44:16 <kaz> i|PR 86|subtopic: PR 86|
12:44:32 <McCool> seb: merged
12:44:36 <McCool> seb: PR 78
12:44:52 <kaz> i|PR 86|-> https://github.com/w3c/wot-charter-drafts/pull/86 PR 86 - Remove normative deliverable mention from bindings|
12:45:14 <McCool> ... just additional detail on streaming and RTSP
12:45:25 <kaz> i|PR 78|subtopic: PR 78|
12:45:28 <luca_barbato> q+
12:45:33 <McCool> mm: is provisional, but suggests RTSP as a place to start for streaming
12:45:38 <kaz> i|PR 78|-> https://github.com/w3c/wot-charter-drafts/pull/78 PR 78 - Define Streaming and RTSP work items in Details|
12:45:44 <McCool> seb: and discussion?
12:45:45 <benfrancis> q?
12:45:45 <McCool> q?
12:45:50 <McCool> ack b
12:45:51 <benfrancis> q-
12:45:56 <benfrancis> q?
12:46:27 <McCool> luca: like idea, but word of warning, RTSP is a big rabbit hole
12:47:13 <McCool> mm: streaming generally, or just RTSP?
12:47:35 <McCool> luca: streaming generally, WebRTC raises similar problems
12:48:27 <McCool> ... concern is that it will take a lot of time
12:49:04 <McCool> mm: think we want to do the minimal amount to support
12:49:25 <kaz> q+
12:49:28 <kaz> ack lu
12:50:24 <McCool> luca: problem is there is a distinction between control and data plan
12:50:56 <McCool> mm: suggest we merge but later on figure out how much time it will take and the priority, and include the time needed in our planning
12:51:22 <McCool> kaz: PR itself is ok, but we should not talk about specifics today
12:51:31 <McCool> ... should think about specific use cases
12:51:35 <McCool> ... later
12:52:28 <McCool> seb: PR 77
12:52:42 <McCool> mm: this was expanding the definition of onboarding, as requested
12:52:57 <McCool> ... think we need to defer discussion of where it goes
12:53:02 <McCool> seb: PR 18
12:53:23 <McCool> ... this was a typo fix, Modbus mentioned by accident under CoAP (cut-and-paste error)
12:53:27 <McCool> ... merged
12:53:50 <kaz> i/PR 77/subtopic: PR 77/
12:54:27 <kaz> i|PR 77|-> https://github.com/w3c/wot-charter-drafts/pull/77 PR 77 - Expand description of Onboarding in Details|
12:54:33 <McCool> seb: should we look at issues?
12:54:45 <McCool> mm: should we move to new repo first?
12:54:58 <kaz> i/PR 18/subtopic: PR 18
12:55:21 <kaz> i|PR 18|-> https://github.com/w3c/wot-charter-drafts/pull/18 PR 18 - Replace "Modbus" in CoAP Protocol Binding section|
12:56:08 <kaz> rrsagent, draft minutes
12:56:09 <RRSAgent> I have made the request to generate https://www.w3.org/2023/06/20-wot-minutes.html kaz
12:56:20 <kaz> i/should we/topic: Issues/
12:57:14 <Ege> q+
12:57:18 <kaz> ack k
12:57:44 <McCool> mm: some of these also related to specific deliverables, e.g. TD, so we can discussion
12:57:45 <kaz> i|should we move|subtopic: Issue 115|
12:57:58 <kaz> i|should we move|-> https://github.com/w3c/wot-charter-drafts/issues/115 Issue 115 - Move Detailed planning to wot repo|
12:58:05 <kaz> ack e
12:58:25 <McCool> ... suggest Ege goes through these in TD session
12:58:32 <McCool> seb: what about security?
12:58:52 <kaz> i|some of|subtopic: Other issues|
12:58:55 <McCool> mm: let's do security during Arch session, since it is related (e.g. where to put normative security content)
12:59:04 <sebastian> https://github.com/w3c/wot-charter-drafts/issues/14
12:59:19 <benfrancis> q+
13:00:02 <McCool> mm: agree protocol binding terminology is confusing
13:00:22 <McCool> ben: are two proposals on the table right now, but won't be able to attend, so will comment now
13:00:25 <kaz> q+
13:00:28 <kaz> ack b
13:00:53 <McCool> ... depending on which direction we take, may need to rename some documents, also relates to how profiles and bindings relate to each other
13:01:06 <McCool> seb: one proposal was to merge bindings into TD doc as well
13:01:18 <McCool> ... but I think Ege will discuss tomorrow
13:01:44 <kaz> q?
13:01:49 <McCool> seb: that seems to be all the issues
13:02:22 <McCool> kaz: suggest we add levels to the issues, e.g. cross-referencing to agenda
13:02:28 <McCool> seb: will do after meeting
13:02:58 <McCool> ... issue 14 can be discussed later during regular TD call
13:04:35 <kaz> kaz: suggest we quickly categorize all the remaining issues and record it here on the minutes then (so that you can add labels later easily :)
13:04:44 <kaz> i/suggest/scribenick: kaz/
13:04:55 <kaz> (McCool quickly categorize the issues)
13:05:41 <McCool> kaz: 115 - org; 114 - org; 112 - org; 80 - Profile; 59 - TD; 57 - TD; 25 - Liaison/org; 15 - Arch; 14 - Bindings
13:05:53 <kaz> s/kaz:/mm:/
13:06:05 <kaz> i/115/scribenick: McCool/
13:06:14 <kaz> rrsagent, draft minutes
13:06:15 <RRSAgent> I have made the request to generate https://www.w3.org/2023/06/20-wot-minutes.html kaz
13:07:09 <mjk> topic: use casees and requirements
13:08:12 <kaz> s/use/Use/
13:08:13 <benfrancis> q+
13:08:17 <kaz> ack k
13:08:17 <mjk> mm: there are 2 choices, top-down or bottom-up, suggest bottom-up approach with each work item
13:08:48 <ktoumura> ktoumura has joined #wot
13:09:02 <mjk> mm: we need to be able to say how the requirements were satisfied by the work items
13:10:15 <Ege> q+
13:10:24 <kaz> q?
13:10:25 <kaz> q+
13:10:26 <mjk> mm: we need to justify each work item
13:11:09 <mjk> ben: suggest that each specification have a requirements document
13:11:32 <mjk> ... to make the scope and contents clear for each spec
13:11:42 <mjk> ... these should be living documents
13:11:51 <kaz> ack m
13:12:16 <mjk> ... the existing UCR is too high level and broad
13:12:24 <sebastian> ack b
13:12:44 <mjk> ege: second Ben's points
13:13:30 <McCool> q+
13:13:37 <McCool> ack e
13:14:36 <mjk> ... there is an issue of document management and an issue of how to satisfy the requirements in the document
13:14:53 <kaz> q- later
13:14:56 <kaz> ack m
13:15:12 <mjk> mm: second the idea of requirements for each document
13:15:50 <mjk> ... we could separate use case as a general document and have requirements for each specification
13:16:04 <sebastian> q?
13:16:24 <sebastian> q+
13:16:25 <mjk> ... for example, we need to add use cases for streaming
13:16:45 <mjk> ... agree that it needs to be a living document that adds PRs as needed
13:17:20 <mjk> ... we have some obvious use cases that aren't documented
13:17:59 <mjk> kaz: agree with these points, but remember that the use case should reflect the industry needs
13:18:10 <McCool> q+
13:18:13 <McCool> ack k
13:18:49 <mjk> ... it should describe the industry scenarios and what is needed across industry
13:19:30 <mjk> ... then technical requirements should be extracted
13:20:03 <mjk> mm: bottom-up doesn't mean leading with features, but keeping them in context of use cases
13:20:35 <mjk> ... we should have justification for each feature
13:20:54 <mjk> kaz: we should be very clear about the policy
13:21:31 <kaz> a/policy/policy and procedure/
13:21:41 <kaz> q+
13:21:58 <mjk> seb: the use case document is more targeted to management, but not where we justify features
13:22:53 <kaz> ack s
13:23:53 <luca_barbato> q+
13:23:55 <mjk> mm: use cases should be base on scenarios and not predict features
13:24:19 <mjk> ... a use case may need a set of many features
13:24:26 <kaz> ack m
13:24:27 <kaz> ack k
13:24:27 <mjk> kaz: agree
13:25:00 <McCool> q+
13:25:34 <kaz> ack l
13:25:47 <mjk> luca: we should go through the full cycle including test cases to insure we don't diverge from the target
13:26:11 <mjk> mm: we should restart the use case meeting and focus on the process
13:26:41 <mjk> ... let's work on one requirements as a prototype of the process
13:27:02 <mjk> ... maybe some of us who are free this summer could work on this
13:27:48 <mjk> seb: do we continue the current mode and update the current document?
13:27:55 <kaz> q+
13:27:57 <mjk> mm: we need more discussion
13:27:58 <kaz> ack m
13:28:26 <mjk> ... and come back to the main call
13:28:36 <kaz> ack k
13:28:55 <mjk> kaz: we have some consensus and can proceed during the use case call
13:29:10 <mjk> mm: we could start at the beginning of the new charter
13:29:21 <kaz> q+
13:29:47 <mjk> kaz: we will need someone to moderate these calls
13:29:57 <kaz> ack k
13:30:05 <mjk> mm: can do the first, and discuss who can take over
13:30:15 <mjk> seb: can also discuss on Friday
13:30:40 <mjk> topic: policy discussion
13:31:00 <mjk> mm: let's first brainstorm which policies to discuss
13:31:26 <mjk> ... there is a document we can review
13:32:08 <mjk> ... starting with the roles of the proposed 3 chairs and has a list of policies
13:32:23 <mjk> ... one item is the decision process
13:33:14 <mjk> ... there is a proposal in the document for the decision process with 3 chairs
13:33:37 <mjk> ... another item is how to choose editors
13:33:39 <kaz> q+
13:33:55 <mjk> ... can a chair be an editor?
13:34:59 <mjk> kaz: for today, we should think about the broader whole group policies
13:35:23 <mjk> ... for example, how and when to bring CG proposals to the use case document
13:35:54 <mjk> mm: which decisions require group decisions vs. chairs
13:36:14 <kaz> ack k
13:36:42 <mjk> ... we could make a list of things the chairs could decide without group involvement
13:38:17 <mjk> ... policies for choosing chairs and for resolutions
13:38:37 <mjk> ... need to be reviewed in the discussion
13:39:22 <mjk> seb: which point should we discuss today?
13:39:39 <Ege> https://github.com/w3c/wot/pull/1005
13:39:41 <mjk> mm: let's start with the async decision process
13:39:47 <kaz> q?
13:39:52 <mjk> ... since Ben is here to discuss
13:40:35 <McCool> q+
13:40:41 <kaz> i/1005/subtopic: Asynchronous Review Process/
13:40:50 <mjk> bf: I have a proposal for how to use github t oget to merging PRs without requiring group consensus in face to face meetings
13:41:01 <mjk> ... except for controversial PRs
13:41:13 <mjk> mm: how do we decide what is controversial?
13:41:16 <kaz> s|https://github.com/w3c/wot/pull/1005|-> https://github.com/w3c/wot/pull/1005 wot PR 1005 - Asynchronous Review Process for Specification Changes|
13:41:23 <kaz> q+
13:41:28 <mjk> bf: we can use the code review tools on github
13:41:54 <mjk> mm: if there are no objections, we could merge PRs
13:42:21 <mjk> bf: also for non-normative changes we could have an editor approval
13:42:47 <Ege> q+
13:42:50 <mjk> ... subject to allowing anyone to object, which would trigger a group discussion
13:42:58 <kaz> ack mc
13:43:35 <mjk> mm: normative changes are those that include assertions, which is difficult to automate
13:43:36 <sebastian> q+
13:43:49 <mjk> ... we could have a flat 2 week waiting period policy
13:44:16 <McCool> q+
13:44:49 <mjk> kaz: concerned that some of the participants could have a problem with a completely offline process. We need some discussion in the calls
13:45:10 <mjk> mm: they could file an objection to trigger the discussion
13:45:25 <mjk> ... it should be easier for those in different time zones
13:46:01 <mjk> kaz: there could be a comment indicating that a particular PR needs more discussion
13:46:41 <mjk> mm:there could be a policy requiring objectors to attend the discussion in person
13:47:12 <kaz> ack k
13:47:21 <McCool> ack m
13:47:29 <McCool> ack s
13:47:50 <Mizushima> q+
13:48:00 <mjk> seb: agree with Kaz concern, but we could have more explanation in writing that gives people more time to study the PR
13:48:24 <McCool> q+
13:48:32 <kaz> q+
13:48:33 <mjk> ... it should be fair to everyone
13:49:16 <mjk> mizushima: it is important to preserve the consensus process
13:49:46 <mjk> mm: we need a concrete policy that we can discuss
13:49:48 <kaz> rrsagent, draft minutes
13:49:50 <RRSAgent> I have made the request to generate https://www.w3.org/2023/06/20-wot-minutes.html kaz
13:50:23 <benfrancis> https://github.com/w3c/wot/pull/1005
13:50:24 <mjk> ... also need a leader to drive the policy discussion
13:50:41 <kaz> i/there are 2 cho/scribenick: mjk/
13:50:43 <kaz> rrsagent, draft minutes
13:50:44 <RRSAgent> I have made the request to generate https://www.w3.org/2023/06/20-wot-minutes.html kaz
13:50:58 <kaz> q?
13:51:00 <kaz> ack mi
13:51:03 <kaz> ack e
13:51:06 <kaz> ack mc
13:51:15 <McCool> q+
13:51:20 <mjk> ege: will there be one policy for all documents
13:51:39 <kaz> q- later
13:51:53 <mjk> ... maybe people still disagree on what the problem is, so we should document the problem
13:52:27 <mjk> mm: there should be a consistent policy for all TF unless there is a really good reason
13:52:50 <mjk> ege: there could be issues with a complex document like TD
13:53:08 <mjk> mm: there may be some special cases
13:53:14 <kaz> ack k
13:53:38 <McCool> ack m
13:54:11 <mjk> seb: next steps? the chairs could prepare policy proposals
13:54:37 <kaz> s/casees/cases/
13:54:42 <kaz> rrsagent, draft minutes
13:54:43 <RRSAgent> I have made the request to generate https://www.w3.org/2023/06/20-wot-minutes.html kaz
13:54:59 <mjk> mm: we already have Ben's proposal for the async process, and can have chairs drive the others
13:55:34 <mjk> q?
13:55:34 <Ege> regarding public communications, there is some in marketing https://www.w3.org/WoT/IG/wiki/Marketing_WebConf
13:55:46 <kaz> i/next steps?/subtopic: Next steps/
13:55:48 <kaz> rrsagent, draft minutes
13:55:49 <RRSAgent> I have made the request to generate https://www.w3.org/2023/06/20-wot-minutes.html kaz
13:56:31 <mjk> mm: we should clarify this before the new charter starts
13:56:58 <kaz> q?
13:56:59 <mjk> seb: available for the next 2 weeks
13:57:17 <mjk> mm: we have a document to guide this process
13:57:34 <kaz> q+
13:57:35 <mjk> seb: agenda check, we are done with today's topics
13:57:39 <benfrancis> q+
13:57:57 <kaz> i/agenda/topic: Agenda check/
13:58:27 <mjk> seb: next meeting tomorrow we will focus on TD and bindings
13:58:40 <McCool> q+
13:58:49 <kaz> ack k
13:59:00 <mjk> kaz: please capture the agenda topics to the wiki and publish these slides
13:59:23 <mjk> bf: want to point out that there are no good time slots for everyone
14:00:08 <mjk> ... volunteer to chair the profile meetings and can discuss on Friday
14:00:35 <mjk> mm: tomorrow we plan to have a main call, do we need resolutions?
14:00:45 <mjk> kaz: we don't need resolutions
14:01:10 <mjk> mm: let's have a short main call to decide if we need a main call
14:01:34 <mjk> kaz: let's have a progress check before we start the TD topics
14:01:50 <Ege> q+
14:01:54 <Ege> ack b
14:01:58 <Ege> ack m
14:02:04 <mjk> ... that can be the first part of the planning meeting
14:02:42 <kaz> ack e
14:02:58 <benfrancis> q?
14:03:06 <mjk> seb: any other comments? AOB?
14:03:19 <mjk> ... adjourned
14:03:36 <kaz> rrsagent, draft minutes
14:03:38 <RRSAgent> I have made the request to generate https://www.w3.org/2023/06/20-wot-minutes.html kaz