=== k1l_ is now known as k1l === evilserfus is now known as serfus [17:06] so, meetingology and topic changes and such [17:07] I am interested in feedback on the talkativeness of the bot [17:08] in general I think it should not talk in channel unless it has something useful to say, such as the outcome of a vote [17:08] it should acknowledge commands with private messages, and change topic with /topic if it can [17:09] one thing I will do is "#startmeeting force" [17:09] which will end a running meeting if someone forgot to end it [17:10] Good idea. [17:11] +1 [17:11] Factoid '1' not found [17:12] huh? [17:12] plus is a factoid now? [17:12] +ping [17:12] another contentless ping... sigh... [17:12] heh [17:13] I didn't mean to do that, really :) [17:14] I think having the bot respond to commands in a private message would be a good way to handle things. [17:16] so /msg charlie-tca I got your link to http://foo.com [17:16] oh, and meetingbot does not cause a topic change to be visible. The only visible change is the bot response that it changed the topic. It is not really changing the channel topic. [17:16] yes, AlanBell [17:16] I think that would be good [17:17] what I wanted to do with the topic was attempt to change /topic and only if that failed (not enough rights) to announce in channel [17:18] the chair has just said #topic bar in channel, no need to repeat it [17:18] but setting the /topic means it is there for people joining halfway through the meeting [17:19] so, maybe it is changing it but not echoing the entire topic change? [17:20] I am using weechat, and every time a topic changes, I get both old topic and new topic, but not when the meeting bot does it [17:21] charlie-tca: that's a weechat's setting afaik, I turned it off myself [17:22] right, but you don't get that old topic/new topic when meetingology changes the topics [17:23] that's odd I don't think the bot changes topic in a different way that we do [17:24] so, the the topic in -meeting really becomes whatever the current agenda topic is named as? [17:24] Yes. [17:25] and someone joining a meeting might see TOPIC: odds and ends [17:25] and that is all they get at that time [17:25] that is the idea, yes [17:25] If thats how their client displays it to them. [17:25] I was going to add a meeting title command [17:26] so it would say "QA Meeting: odds and ends" [17:27] That would probably be better. Joining a channel whose sole topic is "Odds & Ends" doesn't say much about it [17:28] That doesn't even say there is a meeting in progress === k1l_ is now known as k1l === bazhang_ is now known as bazhang