Meeting minutes
minutes
<kaz> Dec-20
Sebastian: minutes of Dec 20, 2023 - chairs have reviewed, fixed a few typos.
… anyone else have any issues or objections?
… if none, propose approving the minutes
… (no objections heard)
… minutes approved
Sebastian: (reviewed minutes policy)
Notices
Sebastian: IIWoT 2024 has been held Jan 6.
… had several presentations - anyone attend and able to summarize?
… Cristiano is not here today unfortunately
McCool: let's defer to next week
Sebastian: sure
Updates
Sebastian: agenda from last year have been archived
McCool: think we should do some more cleanup, e.g. move liaisons to another page
… will also do actions
Sebastian: agree
Kaz: agree
… but should revisit as part of WG planning
Sebastian: next, notice about RDF canonicalization
… also a topic we will follow
Kaz: is just a call for implementation request a few month ago...
McCool: although I'm not sure it's the right answer for TD... we need to analyse
Kaz: so we should move it to liaisons (and then move to another file so that we can continue the discussion appropriately)
Sebastian: agree, will do that now
… (moves to liaisons under W3C)
Schedule
Meeting schedule
Sebastian: several TF calls start Jan 15
… and TD/binding new schedule starts today and tomorrow
<kaz> Holidays
Sebastian: also we updated the holidays, in particular the week of Feb 12
McCool: propose we cancel meetings that week, many holidays
Sebastian: concur
Sebastian: also proposal to have an extended session to discuss IG charter next week, Jan 17
… any objections to that?
… (hearing none)
General schedule
<kaz> schedule.md
McCool: also there is a PR to update the schedule, to archive old events
Lagally: should we materialize some other milestones e.g. for profile planning? There are already planned dates in Q1/Q2 in the new charter.
McCool: suggest in a separate PR
Kaz: agree. note we need a new TF moderator for the Profile work.
Rescheduled Meetings
TD/Binding
Sebastian: already mentioned the new TD slots, review
… note there are new W3C calendar entries
… Wed is primarily TD, Thurs is primarily Binding
Ege: have to make sure we don't "starve" topics, so we will always start with the primary topic
Sebastian: are there also new zoom links?
Ege: Wed uses the old link, Thurs is new
Use Cases
Sebastian: next issue is Use Cases
<sebastian> Doodle for the Use Cases call
Sebastian: there were five options, but it looks like Wed at 7am Eastern, e.g. one hour before the main call
… but that means a long day on Wed
McCool: maybe we start it in two weeks?
Kaz: yes, unfortunate, but we are cutting down the TD call
… I am ok with it
… and charter is not a regular call
Sebastian: ok, let's keep this plan, and have a use case call next week
McCool: we need a TF lead before we can schedule the call...
Sebastian: true, let's deal with that
… we had two candidates: Mizushima and Mahda
… spoke with Mahda yesterday, and maybe better if she takes over another one instead
Mahda: yes, I'm ok with that
Sebastian: mizushima-san, do you agree with being TF lead for use cases?
Sebastian: everyone else ok?
<Ege> +1
<cris_> +1
<luca_barbato> +1
<dezell> +1
<mlagally> +1
<mahda-noura> +1
<kaz> +1
McCool: should have a resolution
<sebastian> proposal: Tomoaki Mizushima will be the new Use Cases TF lead
+1
RESOLUTION: Tomoaki Mizushima will be the new Use Cases TF lead
<sebastian> +1
Sebastian: and to confirm, next UC call will be Jan 17
ACTION: Kaz to allocate a new zoom call for the use cases meeting
Kaz: I will create the zoom link
ACTION: Kaz to help Mizushima send out a calendar entry to the group
<Ege> +1
McCool: propose that after Jan 15 we suspend Security and Discovery for a while, and focus on UC&R, then restart once requirements done
McCool: also, I would like to propose that UC&R focuses on functional requirements, and technical are in each deliverable
Kaz: we need to clearly define functional vs technical requirements, so let's have more discussion during the use cases call.
Lagally: proposal makes sense... but needs some analysis of where requirement is to be satisfied
… use case submitter needs to be available for discussion, may not be WG member
<Mizushima> +1 for kaz
McCool: would like to propose we have a mechanism to "communicate" a technical requirement from IG to WG
Lagally: what if a requirement is split between deliverables? etc.
McCool: let's talk about it in the UC call, part of process, may need a policy, etc.
Kaz: agree with you both, let's discuss more in UC call
Planning
Policies
Sebastian: still several in the pipeline, so will have to schedule another policy session
… maybe in two weeks
Sebastian: (updates agenda to propose Jan 24 for a policy call)
Project Management
Sebastian: TD/Binding - proposal
Ege: see link above
… this also captures some discussion of our current process
… also relates to meeting agendas, prioritization, task decomposition
… also need alignment with UC&R process
… proposal keeps some tables to keep track of items, who has been assigned to it, status (assigned, in progress, done, etc).
Ege: don't want anything too complicated, and don't want to change what we are doing too much
Kaz: TD is making steady progress, but from my viewpoint is still ongoing
… we need to clarify the procedure, in particular how UC & TF work combines
… it's also not just about github issues, but about features, requirements, testing, and so on
McCool: think we need a higher-level view, look at other major planning issues, e.g. testing, requirements capture, etc.
… but this is a good proposal for "agile" github issue resolution
… but we also need a long-term view, see if we are making progress on planned features, etc.
Sebastian: would also be good to look at use-case driven categories
McCool: agree, but it would be good to also catch up with TD requirements discussion as well in UC call
Sebastian: given time we have to move on
F2F meeting in 2024
Sebastian: no new news, but probably next week
TF Reorg
McCool: suggest we put off restarting other TF until Feb, and also we definitely need new TF leads
… I can't lead four, but can do one - which one?
Kaz: also suggest moving TF lead/editor policy to policies section
Sebastian: sure, I can do that (did that)
Social Media
Ege: wants access to posts? Chairs make sense...
McCool: staff at least should have access for succession
Ege: well Marcom team has access...
McCool: ok
Resources
Ege: Jan has made a PR for discovery HTML rendering. TM as well is in progress.
Sebastian: time's up, adjourn. Thanks all!
<kaz> [adjourned]