- From: Pieter Colpaert <pieter.colpaert@ugent.be>
- Date: Wed, 2 Oct 2024 16:55:26 +0200
- To: "public-treecg@w3.org" <public-treecg@w3.org>
- Message-ID: <ba25a84f-3a2a-4317-891d-77372349f21a@ugent.be>
Hi all, We did not press the merge button today as there were still minor comments that needed to be processed. I’ve noted them down in the slides: https://docs.google.com/presentation/d/103Dc_pHTKFPEjvfb3VfjsSFW2IM3-fM_qt7tVmInyFg/edit#slide=id.g30749ebbdea_0_13 In the slides you will also be able to see I’ve already tackled them and have linked to relevant commits. The spec.html attached to this mail can now be inspected. Can I get a quick read and +1 reply from one person of each organization in the CG meeting to publish this one as the new live specification? Such as: Thomas, Sander, Xueying, Julián? For the next CG meeting in November, we can then start devising a plan of attack for the TREE CG in 2025: what will we prioritize and how will we get it done? Kind regards, Pieter On 1/10/2024 17:23, Pieter Colpaert wrote: > Hi all, > > Tomorrow we have the 22d TREE CG meeting at 14 CET. The link is this one: > https://meet.google.com/ngy-ashk-dzn > > > I’d like to prioritize one big point and it is checking whether we can > accept the rewrite and merge it in the main branch. I’ve made > discovery a spec with a lot of TODOs defined in it, and I cleaned up > the entire main spec. It’s the latter that is now attached to this > mail as proposed in the PR. > > Kind regards, > > Pieter > -- https://pietercolpaert.be/ +32486747122
Attachments
- text/html attachment: spec.html
Received on Wednesday, 2 October 2024 14:55:35 UTC