> I suspect that’s because we didn’t rejoin the WG when it most recently rechartered.I’d like to bring your attention to the following communication: https://lists.w3.org/Archives/Public/public-webfonts-wg/2023Mar/0007.htmlIn particular , to this portion of the WG rechartering announcement that reads:“ Current participants are not required to rejoin this group because the charter includes no new deliverables that require W3C Patent Policy licensing commitments.”Thank you,VladOn Aug 4, 2023, at 5:55 PM, hober ***@***.***> wrote: @LeaVerou asked me to edit the explainer to link to published positions rather than rely on telcon and github discussions, which I am happy to do. That’s a great idea! I wish everybody did this. :) Is there a link to the WebKit position? I don’t see one in our standards-positions repo. Please request one! I would welcome further clarification from @litherum because it has been a while since they attended a Fonts WG call. I suspect that’s because we didn’t rejoin the WG when it most recently rechartered. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***> -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/849#issuecomment-1666386898 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/849/1666386898@github.com>
Received on Saturday, 5 August 2023 04:42:32 UTC