- From: Ian Jacobs <ij@w3.org>
- Date: Tue, 7 Mar 2023 07:49:37 -0600
- To: François Daoust <fd@w3.org>
- Cc: Team Community Process <team-community-process@w3.org>, public-webtiming@w3.org
Hi FD, Thanks for the update; we’ll keep the group open. Ian > On Mar 7, 2023, at 12:59 AM, François Daoust <fd@w3.org> wrote: > > Hello CG/BG system, > > The group is somewhat inactive but owns the Timing Object draft and repository [1]. Both the topic of synchronization and the draft continue to be raised and discussed in media groups once in a while. CG chairs and I would like to keep the group open as a point of coordination, "to connect with W3C’s international community of Web experts" as the FAQ has it [2]. > > Thanks, > Francois. > > [1] https://github.com/webtiming/timingobject > [2] https://www.w3.org/community/about/faq/#what-is-a-w3c-community-group > > > ------ Original message ------ > From "Team Community Process" <team-community-process@w3.org> > To: public-webtiming@w3.org > Date : 06/03/2023 19:28:53 > >> Dear participants in the >> >> Multi-device Timing Community Group >> https://www.w3.org/community/webtiming/ >> >> Your Community Group appears to have become inactive (per [1]). W3C plans to close this group in 10 days unless we hear compelling reasons from you to keep it open. >> >> Thank you, >> >> CG/BG System >> >> [1] https://www.w3.org/community/about/faq/#close-inactive >> >> >> > -- Ian Jacobs <ij@w3.org> https://www.w3.org/People/Jacobs/ Tel: +1 917 450 8783
Received on Tuesday, 7 March 2023 13:49:39 UTC