| 02:48 | <bakkot> | ljharb: https://github.com/tc39/ecma262/pull/2810 is ready whenever you get around to it |
| 02:48 | <bakkot> | should land as two commits |
| 03:46 | <ljharb> | huh, what achievements |
| 15:16 | <shu> | ljharb: on the profile page, left hand side, i see Achievements |
| 15:23 | <jmdyck> | https://github.blog/2022-06-09-introducing-achievements-recognizing-the-many-stages-of-a-developers-coding-journey/ |
| 15:26 | <shu> | not a fan |
| 16:09 | <ljharb> | interesting |
| 16:14 | <ljharb> | oh they've had some of them for awhile - the arctic vault one eg |
| 19:48 | <shu> | allen, bless his heart |
| 20:40 | <ljharb> | what now? |
| 20:41 | <shu> | his description of his journey in producing the pdf copies of the specs in the email thread from istvan |
| 20:42 | <jmdyck> | members only, i'm guessing. |
| 20:42 | <shu> | i'm actually not sure who gets those emails |
| 20:42 | <shu> | ecma's email infrastructure is mysterious |
| 20:42 | <shu> | and mostly non-functional, which is why we use github issues now |
| 20:44 | <ljharb> | ah i'm no longer on that thread, i suspect, because it was sent to my coinbase email |
| 20:44 | <ljharb> | feel free to cc in my gmail if you're willing :-) |
| 20:47 | <shu> | forwarded |
| 22:57 | <ljharb> | bakkot: just filed https://github.com/tc39/ecmarkup/issues/468, if you're feeling ambitious :-) trying to crank out some spec text before tommorrow's deadline |