Re: Wants from Chromium's ecosystem infra team in Q4 and beyond?

That was an email to public-test-infra. I've also reached out to team leads 
internally at Google. Are there other places we should seek feedback?

On Saturday, September 16, 2017 at 10:19:05 AM UTC-4, Philip Jägenstedt 
wrote:
>
> Hi all,
>
> I lead Chromium's ecosystem infra 
> <https://docs.google.com/document/d/1MgcisuMnvh3z6QNIjDSvRbt4uoNtmI_cljcQkGXzNQ8/edit?usp=sharing> 
> team, and we want to help you! For an idea of what we're currently working 
> on, see the Q3 OKRs 
> <https://docs.google.com/document/d/1aRpnNQ7Zz_-N9ngdcjQXNjlE1NblppN7lCQwGdxRLlc/edit?usp=sharing>. 
> In summary, it is:
>
>    - The web-platform-tests Chromium↔GitHub import/export process 
>    <https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md>
>    - The web-platform-tests GitHub CI (Travis) and other infra issues 
>    <https://github.com/w3c/web-platform-tests/labels/infra>
>    - The web-platform-tests dashboard <http://wpt.fyi/>
>    - The web API confluence dashboard 
>    <https://github.com/GoogleChrome/confluence> (soon to launch)
>    - Tooling around Web IDL diffing 
>    <https://github.com/GoogleChrome/webidl-diff>
>    - WebDriver and ChromeDriver improvements (example 
>    <https://w3c.github.io/webdriver/webdriver-spec.html#actions>)
>    - Automation of tests that can be automated over WebDriver (first steps 
>    <https://github.com/w3c/web-platform-tests/pull/6897>)
>
> Some clues about what we might work on next are in a brainstorming doc 
> <https://docs.google.com/document/d/1hCOWgU95pN0LaZLdkoJyjlS9A5sjyQQWW6gh8YaDF8o/edit?usp=sharing>. 
> If you have any wants for infrastructure or tooling that would make the web 
> platform more cohesive and more interoperable, please let us know, here or 
> on ecosystem-infra@chromium.org.
>
> Thanks!
>