Re: Best practice for issues?

—And this is when I scream:

Everyone, please use our GitHub issue tracker for anything other than administrative announcements:

https://github.com/w3c/font-text-cg/issues <https://github.com/w3c/font-text-cg/issues>

You never know what kind of a thread your short message will lead to, and submitting anything involving written interaction to this list will make it hard for others to refer to it in the future.

Our GitHub repo’s issue tracker is meant to be used as a forum for any discussions—not merely an “issue tracker”.

Best,
梁海 Liang Hai
https://lianghai.github.io

> On Oct 14, 2020, at 00:11, r12a <ishida@w3.org> wrote:
> 
> +10
> 
> Otherwise we revert quickly to the thread spaghetti that we had in the bad old email discussion days.  Untangling discussions and linking them automatically where useful is one of the wonderful things that GitHub issue threads brought us.
> 
> ri
> 
> 
> Chris Lilley wrote on 13/10/2020 16:57:
>> Hi John, 
>> 
>> To keep discussions on each issue together, it is much better to post each one as a separate issue. Different issues will progress at different rates. 
>> 
>> Contributors who remember more can also open new issues for those. 
>> 
>> On 2020-10-13 18:52, John Hudson wrote: 
>>> I have a shortlist of unresolved topics from ad hoc OTWG meetings dating back to 2014: things that were discussed at length, often more than once, but did not get as far as formal proposals or did not result in action being taken in terms of spec updates. I am wondering if I should post these as a single git issue, to which contributor could then add others they remember, or as single issues? 
>>> 
>>> JH 
>>> 
>>> 
>