| 03:43 | <snek> | i wish they'd just port all the code and infra for it to some public repo, then we could just take some tc39 budget to pay for ci or whatever and call it a day |
| 04:06 | <rkirsling> | it really is an uncomfortable situation, yeah |
| 15:47 | <ryzokuken> | I know https://test262.report/ wasn't properly maintained for a while, but it seems to be fully dead now - does anyone know who to ping to look into that? |
| 15:47 | <ryzokuken> | I can talk to them about it if folks want, but I guess the status is the same as before (they no longer work on any TC39 stuff anymore and don't have the resources to maintain it any further). |
| 15:48 | <ryzokuken> | i wish they'd just port all the code and infra for it to some public repo, then we could just take some tc39 budget to pay for ci or whatever and call it a day |
| 15:49 | <snek> | last time i asked they were not |
| 15:49 | <snek> | maybe the website being fully down is the kick they need though |
| 15:50 | <ryzokuken> | last time i asked they were not |
| 15:51 | <ryzokuken> | maybe the website being fully down is the kick they need though |
| 15:52 | <ryzokuken> | we could consult leobalter about this, they seemed open to the idea |
| 15:53 | <snek> | i mean if someone wants to write all that css, more power to em i guess lol |
| 16:38 | <ptomato> | sorry, it's been an action item in the test262 maintainers meeting to try to get ECMA resources for test262.report, but we haven't worked on it recently |
| 16:40 | <littledan> | Is this Ecma resources for hosting it? Do we have an idea of the expected cost? |
| 16:43 | <ptomato> | no info beyond "we need to talk to people and find these things out" |
| 16:44 | <ryzokuken> | in light of this discussion, it might be good to talk to them on behalf of TC39 instead of Igalia? |
| 16:45 | <ptomato> | yes, that's the plan |