Re: [CSSWG] Announcement: Spec issues are migrating to GitHub issues

From: fantasai <fantasai.lists@inkedblade.net> Date: Thu, 19 May 2016 16:08:04 -0700 To: www-style@w3.org Message-ID: <573E4754.9070205@inkedblade.net> · This archive was generated by hypermail 2.4.0 : Monday, 23 January 2023 02:14:59 UTC

On 05/19/2016 05:54 AM, Sebastian Zartner wrote:
> On 18 May 2016 at 19:53, Chris Lilley <chris@w3.org <mailto:chris@w3.org>> wrote:
>
>     On 16/05/18 19:22, Alan Stearns wrote:
>>     There was some talk of these notifications (issue open, issue close) but I haven’t seen that implemented by Houdini. Do you have that working for 118n?
>>
>     I added them to Houdini today, at the same time as I did for CSS.
>
>
> I assume the issue titles should contain the spec. tags like we used to do here on the mailing list, right?
> Furthermore, what's the strategy for replying to an existing mailing list thread? Should that discussions be ported
> to/continued on GitHub?
> For posting to the mailing list we have https://www.w3.org/Mail/ describing the rules to follow. What are the guidelines for
> commenting on GitHub?

I'm leaning towards just concluding existing threads on the ML.
Moving discussions is not great.

~fantasai