Action items & decisions
Call moderators no longer create their own list of action items & decisions as this is covered by Forkcast, But they are still hidden with the rest of the summary and treated as experimental.
Action items & decisions should be separate from the TLDR summary and graduate these from experimental, to increase visibility & authority.
We likely need a (short term) feedback loop for call moderators to get manual updates to action items & decisions so that they can be confirmed as definitive.
Example
Core devs shouldn't have to remember the outcome from the last ACD call, a link to Forkcast actions & decisions should be enough.
ACDT 70 had multiple core devs trying to remember scope for bal-devnet-3, when this should be in Forkcast.
https://forkcast.org/calls/acdt/070#t=1549
Tomasz Stańczak: 5 Steps to Make Ethereum Driven by LLMs
https://x.com/tkstanczak/status/2023096942650376343
Action items & decisions
Call moderators no longer create their own list of action items & decisions as this is covered by Forkcast, But they are still hidden with the rest of the summary and treated as experimental.
Action items & decisions should be separate from the TLDR summary and graduate these from experimental, to increase visibility & authority.
We likely need a (short term) feedback loop for call moderators to get manual updates to action items & decisions so that they can be confirmed as definitive.
Example
Core devs shouldn't have to remember the outcome from the last ACD call, a link to Forkcast actions & decisions should be enough.
ACDT 70 had multiple core devs trying to remember scope for bal-devnet-3, when this should be in Forkcast.
https://forkcast.org/calls/acdt/070#t=1549
Tomasz Stańczak: 5 Steps to Make Ethereum Driven by LLMs
https://x.com/tkstanczak/status/2023096942650376343