Meeting minutes
Minutes review
<kaz> Apr-12
<skims through call notes>
McCool: any objections?
<none>
Quick updates
Lagally stepping down as TF leader
Lagally: Need to step down from TF leadership of WoT WG and IG task forces (Architecture, Profile and Use Cases)
McCool: I take these tentatively, but have limited bandwidth, so we need additional people to help
Kaz: We need to decide which topics are to be handled by whom. As I put on the agenda, the detail to be discussed during the "Planning" topic later, though.
McCool: We have to talk how to plan our work for the new charter
McCool: I will be intermittent chair on these groups, primar yfocus is to get Architecture to PR
… long term we need some planning discussions
cancellations
McCool: We will have architecture tomorrow - need to prepare for the test fest next week
… For next week we cancel Usecases, Profiles and architecture and use these slots for Testfest
… there are some conflicts coming up, golden week in Japan (April 29th-May 7th), Kaz unavailable on May 8-12th
… let'S wait until next week, since Sebastian and Ege are not here
Kaz: I can join the calls during golden week, but don't expect this from other TF members from Japan
McCool: we should respect Japanese holidays as well. let's focus today on the testfest organisation
Daniel: May 1st is bank holiday in many places
McCool: we should respect Japanese holidays as well. let's cancel scripting and security
… discovery should be held, to resolve the critical issues
Daniel: next week on Tuesday 26th there's an italian bank holiday affecting Cristiano and me.
publication of updated Scripting API Note
Daniel: changes mostly editorial, but the diff shows significant changes, but no real content change
<dape_> PROPOSAL: Publish Scripting API document as is with the editorial PR469
<dape_> PROPOSAL: Publish WG Note Update of the Scripting API document as is with the editorial PR469 merged
<dape_> PROPOSAL: Publish WD Note Update of the Scripting API document as is with the editorial PR469 merged
McCool: any objections to the proposal? The resolution is tentative, one week of review
RESOLUTION: Publish WG Note Update of the Scripting API document as is with the editorial PR469 merged
McCool: one week of review, please raise concerns within a week (via email or on the next main call)
TPAC
<kaz> TPAC wiki
<kaz> TPAC group meeting questionnaire (Member-only)
McCool: We should finalize the questionnaire by April 26th, one week from now
Kaz: we need to respond who will be there in person and how many slots are needed
… I already suggested to use Thurday and Friday, have other obligations on the other days
McCool: times are in the afternoon CET - we can probably do 2 sessions
… who can commit to attend?
… Please add your name to the Wiki
Kaz: we should think about joint calls as well
McCool: proposed: JSON-LD, SDW, Privacy, Accessibility
Kaz: some discussion with MEIG might make sense, Ege mentioned video streaming last week
Use Case discussions
McCool: We suspend these calls for this charter period, added a note that we do not take in new use cases in this charter period
charter
<kaz> draft WG Charter
<kaz> Strategy pipeline issue
McCool: We have no input to our charter, it ill take a while, this is in process
… we have to clean up testimonials as part of the testfest
Societal Impact questionnaire
<kaz> Societal Impact Questionnaire
<kaz> draft response
McCool: I created a draft, unfortunately Sebastian did not have time to review
… We could make a tentative resolution
Kaz: Regarding the testimonial, we should clarify our basic logistics and expectations to the group participants. Then regarding the Societal Impact Questionnaire, it would be better to give some kind of debriefing to the whole group as well.
McCool: The draft has been available for 2 months
Kaz: Given we've got feedback from just a few people to the GitHub issue on the questionnaire, probably it would make sense to have quick review of the questionnaire itself and the feedback so far to all the group participants during the main call too.
Lagally: Can you briefly present the draft
McCool: sure, let me walk you through
<McCool walks through the draft>
McCool: I noticed that we should also add scripting, security and other use cases, let me add a note to the PR. Also please review.
Planning
Work on the specs for the current Charter and the preparation for the next Charter
McCool: There were a bunch of PRs that added a few milestones, some of the dates need to be updated
… We have some deadlines that have already passed
… We could align all dates with the dates of Architecture
… we can align dates with Architecture
… I have a PR to move details from the charter planning to the main repo
Kaz: we need to clarify that we have to work for the current charter and the next charter
… it is also fine to handle both together
McCool: suggest to use that for the new charter
… planning for the next charter should happen after we have concluded the PR in the current charter
Kaz: I propose to have one location for current schedule and future planning
McCool: Let me create this directory, will create other PRs for reorganising things
… priority needs to be to conclude current charter, i.e. PRs of Architecture, Discovery and TD
… Architecture is in good shape, only 3 at risk assertions
… TD has 15 at-risk assertions
… discovery needs substantial more work
Testfest
McCool: we have a test fest next week, I want to change the schedule and use the architecture and use cases slot.
… we will discuss details in the testing call
Kaz: test fest during Use cases, Testing and Architecture calls using the existing dial-ins?
McCool: Let me clarify in the README.md
<McCool_> w3c/
McCool: create PR 547 under wot-testing
<kaz> proposal: Testfest next week will be held on Tuesday, Apr 25 at the use cases call slot, Wednesday, Apr 26 at the test call and Thursday, Apr 27 at architecture call
RESOLUTION: Testfest next week will be held on Tuesday, Apr 25 at the use cases call slot, Wednesday, Apr 26 at the test call and Thursday, Apr 27 at architecture call
<kaz> [adjourned]