Oh I agree, but we do need to discuss blockers relatively quickly after they come up, and stand-ups can be an efficient way to do this. You can try to just automate workflows or try to get people to resolve blockers asynchronously, but if it takes more than a couple replies to resolve them, now a meeting may have been faster/more efficient.

If I'm using Meetter to automatically schedule a stand-up, I (presumably) can say, only schedule the meeting if we have blockers to discuss, and only invite the people who are mentioned in the issue/blocker. But how to determine if there's blockers, and who to invite? Query the issue tracker.

You could look up blocked GitHub or ZenHub Issues and generate a stand-up to discuss them once they happen, and maybe re-generate a stand-up after X time if they have not been updated, to prevent stale blockers.

What I get out of this is when I work for a company which requires stand-ups, I don't have to go to them if I have no blockers. I know I would pay for that privilege :-)

Ah, I see what you are suggesting. This indeed makes sense and may be possible not so far down the road when we expose APIs.

For now, it is possible to implement the same workflow with the current version of Meetter just by asking someone to check task tracker for blockers about 30 minutes before the Meetter hour and manually create topics.