Re: Planning to close Web Media Text Tracks Community Group due to inactivity unless we hear from you

Hi there,

Most of the work of this group has moved to the the Timed Text Working
Group by now, particularly the development of the WebVTT standard.

This group was working on publishing a specification at
https://dvcs.w3.org/hg/text-tracks/raw-file/default/608toVTT/608toVTT.html
which hasn't seen any recent improvements but it's being used in practice.
It's unclear who will continue its development.

The group had lacked leadership in recent years.

Kind regards,
Silvia.

On Tue, 29 Oct 2024, 4:58 am Team Community Process, <
team-community-process@w3.org> wrote:

> Dear participants in the
>
>    Web Media Text Tracks Community Group
>    https://www.w3.org/community/texttracks/
>
> Your Community Group appears to have become inactive (per [1]).
>
> If your group is in fact active, we ask that you respond to this email
> with answers to these two questions:
>
> * Is your group publishing any Specifications?
> * What is the group's expectation about future standardization of
>   those Specifications at W3C or at some other standards body?
>
> We also recommend the following:
>
> * Let us know where the activity is going on so that we can update our
>   data and improve our tools.
>
> * Update your group home page with news of your activities.  Chairs
>   can use the group Wordpress instance of the group to post news; let
>   us know if you have any questions.
>
> If you would like us to keep the group open because you expect it to
> become active in the near future or for other compelling reasons, just
> let us know.
>
> If you would like to schedule a call to discuss the current status of
> your group, your plans, and any obstacles to success, or you simply
> have questions about the CG program, please let us know.
>
> If would like us to close the group, or if we do not hear from you in
> the next 30 days, we will plan to close the group.
>
> Thank you,
>
> CG/BG System
>
> [1] https://www.w3.org/community/about/faq/#close-inactive
>
>