Re: Weekly github digest (svgwg, fxtf-drafts)

Nikos or anyone else who knows: How do we tweak this bot to change what
it's tracking?

It would be nice if it also reported on SVG-related issues in the ARIA
repo.  But that would require a way to filter issues by title or label.

Something like this search:
https://github.com/w3c/aria/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20in%3Atitle%20SVG%20



On 1 August 2017 at 11:00, W3C Webmaster via GitHub API <sysbot+gh@w3.org>
wrote:

> Tuesday August 01, 2017 Issues w3c/svgwg (+2/-0/💬20)
>
> 2 issues created:
>
>    - #338 Add a method to return the path direction (tangent) angle at a
>    given distance <https://github.com/w3c/svgwg/issues/338> (by AmeliaBR)
>    - #337 Compatibility mid-line rendering attribute to textPath
>    <https://github.com/w3c/svgwg/issues/337> (by msand)
>
> 4 issues received 20 new comments:
>
>    - #338 Add a method to return the path direction (tangent) angle at a
>    given distance <https://github.com/w3c/svgwg/issues/338> (8 by karip,
>    BigBadaboom, fsoder, AmeliaBR)
>    - #335 SVG2 path data coordinates are currently spec'd as integers.
>    <https://github.com/w3c/svgwg/issues/335> (6 by fuchsia, tshinnic,
>    AmeliaBR)
>    - #337 Compatibility mid-line rendering attribute to textPath
>    <https://github.com/w3c/svgwg/issues/337> (3 by msand)
>    - #333 SVG marker orientation at a 180° U-turn not well defined
>    <https://github.com/w3c/svgwg/issues/333> (3 by karip, fsoder,
>    AmeliaBR)
>
> Repositories tracked by this digest:
>
>    - https://github.com/w3c/svgwg
>
>
>    - https://github.com/w3c/fxtf-drafts
>
>