Meeting minutes
guests
Sebastian: no news
minutes
<kaz> Arp-19
Sebastian: sadly Lagally mentioned that he cannot act anymore as TF lead
… then we discussed cancellations
… and scripting API publication plan
… TPAC, use cases, and chart discussion
… questionnaire is almost complete
Sebastian: we finally did a resolution about Testfest plans
… no issues with the minutes
… any comments?
… ok, minutes approved
quick updates
<kaz> Cancellations
Sebastian: use cases, profile, and architecture are cancelled in favor of the testfest
… next monday is holiday we will cancel Monday calls
… also next week is holyday in Japan
Ege: kaz are you available next week?
Kaz: I can join if really needed.
Ege: ok does this mean that we can do the meeting?
Kaz: it would be better con cancel the calls
McCool: I'm ok of canceling even if there is something to do in profile
… we can cancel everything but testing calls (without minutes)
Kaz: if needed I can join
Ege: in the TD call we need to decided the TF lead
… we can have a tentative resolution
Sebastian: I think we can wait
McCool: the only critical calls that we need to do is testing
Sebastian: ok for me to cancel all the calls
+1
Sebastian: there is an AC meeting this month
… kaz will be not available.
Kaz: technically group chairs can join the AC meeting if you want
… let everybody know if you join that meeting
McCool: we need to finalize test result for the 10th
McCool: I can go, but only if it doesn't conflict with other calls
new charter review
Sebastian: no news?
Kaz: we got response for internationalization
… we are waiting for other groups. will talk about this issue during the W3C Strategy Team call next Tuesday.
McCool: we have one PR that we should merge
… just fixing minor issues (broken links)
Sebastian: ok, any complains?
<sebastian> wot-charter-drafts PR 116 Remove links to template
McCool: no real content change
TPAC
<kaz> TPAC page
<kaz> TPAC group meeting questionnaire (Member-only)
Sebastian: we need an estimate about people going to spain
… we have to submit the heads count next week
… if you are not sure you can just add the probability
… please update the list on the wiki
… we should also start to think about topics
Ege: we talked about this in the TD two weeks ago
… we got same email in the CG
… web agents group might organize something
<kaz> TPAC 2023 WoT wiki
Kaz: we need to identify the expected count of the participants for rooms and slots
… and basic category of meetings which require us dedicated F2F discussion on complicated or controversial topics.
… please help
McCool: we should discuss things that are difficult to solve remotely
… we can create virtual F2F to cover people that are not in good timezone
McCool: let's optimize for japan and europe
Ege: do we have an open day in TPac?
McCool: Wednesday
Kaz: it depends on what we would like to do
… we don't need to have an open day
… but if we want we can organize
… it is something that should be part of the agenda discussion
McCool: let's have a doodle poll
Sebastian: ok
ACTION: kaz to generate a doodle poll to find better slots for Thu/Fri
schedule
Sebastian: scripting api is planned to be published
… which is the status?
Daniel: we are working on it
Kaz: we made the resolution last week
… there was some typos
… the task force wanted to include that too
… plus there were discussion on the scripting api
… some of the Scripting API TF participants are wondering about the possibility of making Scripting API a normative document.
… and how the scripting api was recorded as an informative document
McCool: I also made a PR to update
… the schedule
Sebastian: ok for merging
Daniel: scripting api was just minor changes
<dape> wot-scripting-api PR 469 - Align spec with INFRA
Daniel: just minor changes as you can see
Sebastian: we can even don't do the resolution
Kaz: I think we still should make an updated resolution given we made a resolution last week for PR 469 and we've updated the PR 469 itself after the resolution was made. Note that we should not add any updates to the PR after making resolution, but should create a new separate PR for typo fix.
<sebastian> w3c/
proposal: The group decided to publish Scripting API note after the recently updated PR 469 in the scripting has been merged
proposal: The group decided to publish Scripting API note after the recently updated PR 469 in the scripting has been merged
RESOLUTION: The group decided to publish Scripting API note after the recently updated PR 469 in the scripting has been merged
Cristiano: we were also surprised about finding out that scripting API is informative document
… we were planning to have it a Note Rec track
Sebastian: is this the kind of document that is in between informative and rec track?
Cristiano: yes, but in the charter we said it was just informative
Kaz: As I've been repeatedly mentioning, there is no "Note REC track" defined within the W3C Process, also making part of a group Note normative would be dangerous from the Patent Policy viewpoint.
Sebastian: we are out of time
… maybe we need another discussion slot
Kaz: it would be better to discuss about this offline
Sebastian: it seems there is not something in between doc
dape: it seems that note-track is not recommended by w3c it was not clearly stated.
Sebastian: we need a separate meeting
McCool: let's discuss this in the next chair call
… in the meantime we can use emails
Kaz: for the record from the beginning I was suggesting to not go for that direction.
testing
Sebastian: discuss this in the testing call
testimonial
Sebastian: please talk about your upper management for testimonials
… also about press release
societal impact questionare
Sebastian: michael worked hard on the doc,
… I think it is in good shape
… we can merge the PR as it is
… of course we can always improve it
… but it is fine at it is
<McCool_> proposal: submit the current draft of the societal questionnaire.
<sebastian> w3c/
<sebastian> +1
<McCool_> proposal: submit the current draft of the societal questionnaire at w3c/
RESOLUTION: submit the current draft of the societal questionnaire at w3c/
<kaz> PR 897 - Societal Impact Questionniare
<kaz> [adjourned]