Re: Planning to close Font and Text Community Group due to inactivity unless we hear from you

Before we switch off lines of communication, can we perhaps share some advice for former FTCG members on where they are recommended to seek advice and collaborate? Liang and Simon once spoke of the group “triaging” queries and suggestions, and I therefore wonder if we might productively document on GitHub some classes of questions and proposals along with how group members recommend they are dealt with.

For example, I have been contemplating how to give CSS the power to override certain font metrics. In a recent real use case, I found the area between ascender and descender filled by the background-color was too high, and I wanted the ability to override the values in the font. (I was able to hack the font successfully, but that solution is not normal, and often technically impossible or illegal.)

- Laurence

> On 7 Mar 2023, at 16:47, Ian Jacobs <ij@w3.org> wrote:
> 
> Thank you for the update and additional information regarding the mailing list.
> 
> We’ll plan to close the group, but feel free to come back to us if you think it would be useful to keep this group open as a liaison structure.
> 
> Ian
> 
>> On Mar 7, 2023, at 10:00 AM, Liang Hai (梁海) <lianghai@gmail.com> wrote:
>> 
>> Hi the CG/BG System,
>> 
>> As the acting chair of the group, I don’t object to the closing.
>> 
>> ---
>> 
>> For the participants’ interest:
>> 
>> Recently the Unicode Technical Committee had some discussion about getting into the long time neglected problem of documenting “orthographic syllable structures”. There’s an open action item and Roozbeh’s brief rationalization. This marks some hope that some gaps between the Unicode Standard and the OpenType technologies may get to be closed from the Unicode Standard’s side.
>> 
>> Please get in touch with Lawrence, Norbert, or me, if you’re interested to contribute.
>> 
>> ---
>> 
>> On the other hand, for the participants again, here’s an excerpt from the Community and Business Groups FAQ:
>> 
>>> How do we close a group and what happens?
>>> 
>>> To close a group, send a request to team-community-process@w3.org.
>>> 
>>> When a group is closed, the following happens automatically:
>>> 
>>>    • The list of participants is emptied and people can no longer join the group.
>>>    • The group’s home page indicates that it has been closed and the date of closure.
>>>    • The group appears in the list of past groups.
>>> 
>>> 
>>> By default, we do nothing to the group’s home page (blog), mailing lists, and wiki. However, we recommend:
>>> 
>>>    • Updating the group’s home page description to let people know where to turn (e.g., that work has moved to a W3C Working Group, etc.). The group can augment this communication with a blog post as well.
>>>    • Closing mailing lists that will no longer be used. Please write to sysreq@w3.org to request that a mailing list be closed, which means that content is archived but people can send no new mail to the list.
>> 
>> Because the list of participants will be emptied, I’ve taken a screenshot (attached) so in the future we get to more easily gather people interested in this field.
>> 
>> Currently I don’t plan to request the mailing list be closed.
>> 
>> 
>> Best,
>> Liang (梁海 Liang Hai)
>> https://lianghai.github.io 
>> 
>> 
>> <Screenshot 2023-03-07 at 16.41.41.png>
>> 
>> 
>>> On 6 Mar 2023, at 19:28, Team Community Process <team-community-process@w3.org> wrote:
>>> 
>>> Dear participants in the
>>> 
>>> Font and Text Community Group
>>> https://www.w3.org/community/font-text/
>>> 
>>> 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 Wednesday, 8 March 2023 13:48:46 UTC