00:49
<Mathieu Hofman>
I really hope over time the spec is allowed to change the number of ticks some things take. I believe we did so for async function return already
04:41
<rkirsling>
shu: did you mean to leave this needs-consensus topic just titled by its number on the agenda? 🤔
04:41
<rkirsling>
https://github.com/tc39/agendas/commit/870dd57707700201cc6893d4b7bbb1b133a2e51a
04:48
<ljharb>
yes, that’s intentional
05:31
<rkirsling>
these map.emplace slides are so pretty
05:31
<rkirsling>
nice work dminor
08:13
<rkirsling>
and shu's presentation is totally gonna be a show-stealer, I'm excited for this 😁
20:44
<Chris de Almeida>
copypasting Rob's message from the reflector:
20:44
<Chris de Almeida>

The agenda continues to fill with content and is beyond our capacity. There's roughly 20 hours of agenda content and 16 hours of meeting time to fit it in. So we are over budget by about 4 hours. Sometimes we recover an hour or two, but not four.

Actions

More Time

Our hosts are happy for us to continue until 5pm each day, so I propose we extend Thursday to finish at 5pm instead of finishing at 4pm.

Less Content

To everyone that has placed items on the agenda, please consider voluntary actions to mitigate the capacity problem. For example you could:

  • Mark your item as low priority by adding a ⬇️ icon to the agenda.
    • This means we will only get to it if time permits.
  • Reduce the timebox.
    • You can express the timebox as a range if you wish. The upper limit of which should ideally not be higher than the original request.
  • Remove the item entirely if there is no harm deferring it to the next meeting which is at the start of December.
22:27
<Michael Ficarra>
alright I added lower bounds to my items' timeboxes, hope that helps with scheduling