| 02:51 | <Domenic> | how do i coax people to review and merge wpt prs https://github.com/web-platform-tests/wpt/pull/36733 |
| 02:52 | <snek> | They are merged after the corresponding spec change is merged, generally. |
| 02:52 | <snek> | I need to get safari or Firefox to implement this |
| 02:52 | <snek> | and they want tests |
| 02:52 | <snek> | and tests want spec |
| 02:52 | <snek> | and spec wants safari or firefox |
| 02:53 | <Domenic> | Well they should be able to express interest in shipping, which unlocks the spec, which unlocks the tests, which unlocks the ability to actually land code. |
| 02:53 | <snek> | hmm |
| 02:54 | <snek> | then we should be able to merge the spec I guess |
| 02:54 | <snek> | do I need them to like comment on the spec pr or something to make the interest official |
| 03:39 | <Domenic> | Yeah exactly |
| 03:39 | <Domenic> | Or some public indication of willingness to ship |
| 08:02 | <annevk> | Dominic Farolino: it works if the algorithm can be invoked inside "in parallel" only; but yeah, if you want to run it on the main thread that's a no-go |
| 08:05 | <annevk> | snek: https://whatwg.org/working-mode#changes is the process for a change. All of these things can be prepared in parallel or in sequence, but typically any kind of merging happens only after they are all deemed in order by the editor. |
| 09:22 | <snek> | snek: https://whatwg.org/working-mode#changes is the process for a change. All of these things can be prepared in parallel or in sequence, but typically any kind of merging happens only after they are all deemed in order by the editor. |
| 09:29 | <annevk> | snek: it looked to me like the PR was still a draft? |
| 09:30 | <snek> | hmm so it is |
| 09:30 | <snek> | I'll mark it as ready to review |
| 09:31 | <snek> | too used to the tc39 process of tests first |
| 16:20 | <wanderview> | wanderview: ta, hopefully tomorrow |