I can work on updating this sometime this coming week. I am heading out of town for the remainder of the weekend soon.We did make the meeting name with #startmeeting a requirement so that people coiuld find their logs, and it is a parameter. I thought I had added that tot he document when I did that, evidently not. #meetingname is not required, but if you want to change the name in the herald of the room you are in during a meeting, #meetingname will do it, it just won't change the name of the logs, which is set with the name you give with #startmeeting.#meetingtopic will change the topic of the meeting as well, but I believe there are other ways to do that as well these days.Like I said above, I will plug away at this during the week.Thanks,Dave Shier(odin)On Mar 12 2016, at 9:48 am, Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> wrote:_______________________________________________
We have https://fedoraproject.org/wiki/Zodbot, but it doesn't seem very
complete around the meetbot plugin., and I can't find the source we're
using for that. The docs say "#help" instead of "#halp" (which the bot
itself tells you to use), for example. And, I think we changed it to
that you need to provide a meeting name -- except we seem to do it as a
parameter to #startmeeting, although the FESCo meeting template calls
for also setting #meetingname. This is confusing to me — what are
people _supposed_ to do?Oh, and there's #meetingtopic, which seems to be in no one's meeting
SOP. Should it be???--
Matthew Miller
<mattdm@xxxxxxxxxxxxxxxxx>
Fedora Project Leader
_______________________________________________
infrastructure mailing list
infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
http://lists.fedoraproject.org/admin/lists/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
infrastructure mailing list
infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
http://lists.fedoraproject.org/admin/lists/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________ infrastructure mailing list infrastructure@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
