When changes are made to meetbot configuration (for example, to have it join and begin logging a new channel), it gets restarted so that configuration can take effect. If it gets restarted mid-meeting, it loses state about that meeting and rejoins in an idle state thinking no meeting is in progress. This can be noticed as the channel topic remaining from the previous meeting, but no further acknowledgement of meeting-related commands until the next #startmeeting is issued. Following subsequent meetings, it will also persist in returning the channel topic to what it found when it rejoined (whatever the meeting topic happened to be at the time it restarted) until a /topic is reissued by a channel operator between meetings.
It would be great to find a way to avoid interrupting meetings when we want to apply updated configuration to the bot. Perhaps when it intercepts a graceful restart signal while a meeting is still in progress, meetbot could defer taking action on it until an #endmeeting is issued.
