Meeting minutes
minutes review from last week
<kaz> Jan-11
Sebastian: any changes or corrections or objections?
Sebastian: approved, ask Kaz to publish
updates
IIWOT debriefing
McCool: the workshop presentation went well
… the slides will be useful as a survey of implementations
… academic projects aren't included
… liaisons could also be added
Kaz: would be nice to put the information on the implementations and liaisons on the WoT Marketing page.
McCool: should update the website as well
… the link in the agenda points to the pdf
use case call
McCool: we need to schedule a use case call to gather information for the charter
McCool: the lack of ability to un-cancel meetings is a problem
Ege: we can un-cancel by special request to the system team, but it's a lot of overhead
Ege: created an issue for the system team
Kaz: sysreq@w3c.org can be used to uncancel items but you can simply create a new entry for the "WoT Use Cases" call. Also what is important is everybody is aware when to have the call and the WebEx coordinate.
Sebastian: new use case call Tuesday the 31st, 0800 US Eastern time
next week schedule
call logistics
<kaz> PLH's msage on conf logistics (Member-only)
Sebastian: W3C is moving to zoom starting February
McCool: MIT will keep the webex until June, so we have time to transition
Kaz: the message asks us to transition by the end of June. we don't need to rush but we need to think about when to transition to zoom.
publications
Sebastian: snapshot CRs were published, thank you, Kaz
<McCool> w3c/
McCool: discovery needs a CR update, there is a PR to review the draft
… we want to have a resolution on Feb 8 to publish on Feb 15th
… on github we have a diff and preview link
… 2 problems, DID part and DNS-SD part need to be updated
Kaz: we should talk with Philippe about these changes
McCool: maybe there is another option besides 2nd PR, will talk with Philip
Kaz: there are several options, including not changing things
McCool: there are errors that would break an implementation
… we can't change the text to informative
McCool: there are enough errors to require a normative change
Kaz: thought this was identified as "at-risk".
McCool: no, actually not identified as "at-risk". that's the problem.
Kaz: in that case, I'd suggest again we consult with Philippe.
McCool: will talk with Philippe
Sebastian: agree that it's a bug that needs to be fixed
McCool: maybe we could publish an errata
Sebastian: please review the PR
schedule plan
McCool: go to the PR and view
McCool: many updates to the schedule plan
McCool: the plan doesn't include the charter draft, needs to be inserted
McCool: there is about a month allowance for the draft, so we should be able to complete it on time
McCool: next face to face meeting, mid-June time frame or at TPAC in the fall
Kaz: OK with the schedule, but are we sure about the date for the charter draft?
McCool: there is a review date that informs the earlier deadlines
… we can add more PRs to the document as we refine the schedule
Kaz: can we add one line for the draft charter?
McCool: OK
McCool: will fix
… February 22 date for starting the AC review
McCool: next subject is when and how do we complete the draft charter
Sebastian: no objections on the PR, adding the one line?
Sebastian: there are PRs for proposals for the various TFs, please review and refine
… in 2 weeks we plan to use the use case time slot to merge the PRs and finalizre the charter
McCool: there is some concern that the charter is too detailed
… like to capture the detail in the first merge, then simplify it later
… merge the PRs with all the input and detail, then refine
McCool: maybe we can use the use case call on Feb 21st also
Kaz: I think we should start with the basic scope and mission statement
… OK to manage the input we have, but we need to clarify the basic policy, scope and mission
… suggest another 1 week dedicated meeting
<Mizushima> +1 kaz
McCool: we can make PRs for the mission statement and review them
… the only week available would be February 13th
McCool: we could do a doodle poll to set up these time slots
… would like to keep a few meetings open that week to make progress
Sebastian: we can use part of the TD call also
Kaz: we can handle the PR review and charter discussion separately
McCool: we can merge the PRs on February 8th
McCool: how many hours will we need that week?
McCool: recommend 4 hours
Kaz: 4 hours baseline is OK and possibly another 2 hours as reserve.
… we have already published the specs so need to decide how to wrap up the documents
McCool: call for a resolution to review the PRs on February 8th
Ege: there is a concern that these are being merged without discussion
… when are we going to discuss? we will need the general policy to inform this discussion
McCool: the PRs capture the TF consensus but not group consensus
Kaz: originally suggested we use MD before fixing the content but we've already started to use the HTML template. So would propose to use a second repository for the refined document
McCool: yes, we can create a clean space for the refined document so that we can see the rendered HTML for each proposal to have thorough reviews easily.
Sebastian: I currently don't have the big picture for the charter or the total content
… so it would be good to get a first impression with all in one place
McCool: the resolution to merge the PRs will be proposed later
<McCool> proposal: will work on current set of PRs for draft WG 2023 charter until Feb 8, then will propose a resolution to merge into a first draft charter, then will schedule a set of meetings the week of FEb 13 to restructure, with the goal of publishing the final draft representing the consensus on Feb 22
<McCool> proposal: will work on current set of PRs for draft WG 2023 charter until Feb 8, then will propose a resolution to merge into a first draft charter, then will schedule a set of meetings the week of Feb 13 to restructure, with the goal of publishing the final draft representing the consensus on Feb 22
Sebastian: sounds good to me
<sebastian> +1
McCool: any objections?
RESOLUTION: will work on current set of PRs for draft WG 2023 charter until Feb 8, then will propose a resolution to merge into a first draft charter, then will schedule a set of meetings the week of Feb 13 to restructure, with the goal of publishing the final draft representing the consensus on Feb 22
McCool: resolved
AOB?
Sebastian: any more agenda points?
… request to the group to create testimonial statements for the W3C press release
McCool: let's discuss testimonial submission at the testing call
Sebastian: anything else?
AOB?
Sebastian: adjourned
<kaz> [adjourned]