= bug description = Discussed in #fedora-admin, 2016-01-28 at 18:51 UTC.
Meetbot does not properly adjust the name of a meeting when using the #meetingname command in a meeting. This can cause teams or sub-projects to have their meetings accidentally saved to an improper team name with a specific date in the string.
Related ticket: #5077
= bug analysis = When using Meetbot, a chair can start a meeting with a name using #startmeeting and then adjust the name with #meetingname. Originally, #startmeeting did not require a name to begin a meeting, but now it does.
Many groups, such as Council, Infrastructure, CommOps, etc., start meetings with the following group of commands:
Normally, after using #meetingname, the meeting name is adjusted, like shown in [https://meetbot.fedoraproject.org/fedora-meeting-2/2016-01-19/commops.2016-01-19-17.01.log.html this meeting]. However, that is no longer the case.
No confirmation from zodbot is sent after setting the meeting name. This log comes from [https://meetbot.fedoraproject.org/fedora-meeting-2/2016-01-26/fedora_commops_%282016-01-19%29.2016-01-26-16.56.log.html this meeting].
= fix recommendation = It seems something has broken in recent days with #meetingname with zodbot.
Only setting the severity to high because this is a problem that actively interferes with how meetings are saved in møte, and it could cause some meetings to need their name changed after the fact, which can break URLs. It could potentially bury some meetings in møte with a new team with a specific string including the date.
It looks like you misspelled "#meetingname"? http://imgur.com/1NtIMm0 (3 e's)
I just tested it in #fedora-apps and it seemed to work ok.
Closing ticket. Was human error… I didn't realize I had #meeetingname with three e's. :P
Login to comment on this ticket.