Here's the list of supported commands (from Meetbot help printed after starting a meeting):

Meet Bot reminds you of the things that can do in the meeting:

!meetingname : to rename the meeting
!topic : to change the topic of the meeting
!endmeeting: to, well, end the meeting

There are also several handy tags that you can use to tag a message to highlight it in the minutes (and add an emoji reaction here):

!action: 🚩
!info: ✏️
!agreed: 👍
!rejected: 👎
!idea: 💭
!halp: 🛟
!link: 🔗

If the URL for "Meeting format" changes, these pages need to get adjusted:
https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting

there's a non-obvious problem too. I don't know if we can do anything about it, but it's worth noting, and maybe there is something.

if you paste a text block like this:

!info 2 Proposed Blockers
!info 6 Accepted Blockers
!info 0 Accepted 0-day Blockers
!info 1 Accepted Previous Release Blockers
!info 0 Proposed Freeze Exceptions
!info 9 Accepted Freeze Exceptions

into element - and I think most other matrix clients - you don't send six separate messages which each get interpreted as a bot command, you send one multi-line message (I've no idea what the matrix bot would do with it; the IRC bot got very confused when you did this).

When I was running the meetings from Matrix via the bridge to IRC, I had to copy/paste the lines one at a time, which got old real fast.

If there's anything we can do about that, it'd be great.

I'd say let's try it first, and if it doesn't work as expected, let's file an RFE for meetbot.

As a workaround, it should be possible to retype it manually with xdotool (it would physically press Enter after each line), but that only works on X11 session. I don't think there's a viable replacement for Wayland yet (last time I looked, there wasn't).

I'd say let's try it first

I tested it. Here's the full log and here are minutes. As you can see, a multiline block is considered as a single INFO statement, unfortunately. Let's file an RFE.

Let's file an RFE.

Here were go:
https://github.com/GregSutcliffe/maubot-meetings/issues/44

Hopefully in the right place.

Commit 76b87b30 fixes this issue

Deployed to production and SOP updated:
https://fedoraproject.org/w/index.php?title=QA%3ASOP_Blocker_Bug_Meeting&type=revision&diff=698461&oldid=698422

Closing.

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/quality/blockerbugs/issues/281

Please continue any further discussion there.