jgraham

So it sounds like setting up WebKit/iOS testing is the most tractable to get running at all (we can just set up the simulator on existing infrastructure, which is work,...

I made an [Interop 2023 proposal](https://github.com/web-platform-tests/interop/issues/201) for this work. I think it's helpful to have set out the reasoning for making this a priority, and the roadmap for the work,...

My point of view: * Use `/third_party` for third party code * We can write a rule to exclude all `third_party` directories from linting * The best way to add...

I am somewhat concerned by PRs like that randomly adding third party code under different licenses all over the tree. @foolip started looking at lints for this; I wonder if...

I think that makes sense, although I'm not fully clear on the details of what you want to lint. I think we can enforce two things: * Every file with...

@foolip looked at some of these https://bugzilla.mozilla.org/show_bug.cgi?id=1637924 is filed for the css-color issue but is waiting for @dbaron I think we can also assume that `fonts` is all third party....

On the gecko side: * We update the tools with the rest of the changes; there's no special handling * When stuff breaks on import it usually requires emergency patches....

So one reasonable goal here would be to remove `localpaths.py`. I wonder if something like the following could work: * We have a requirements_vendored.txt file that installs everything under third_party...

One concern here is startup latency; if every `wpt run` call is invoking `pip` and checking that all the packages are installed it's going to add noticable startup time.

Right, I think the question is how to find out that "everybody is fine with it" or "some user of WPT doesn't support it well". It sounds like the process...