[18:24:31] .help [18:24:33] I've posted a list of my commands at https://clbin.com/PaiV5 - You can see more info about any of these commands by doing .help (e.g. .help time) [18:24:47] .help meetbot [18:25:06] .help startmeeting [18:25:07] RhinosF1: Start a meeting. See [meetbot module usage]({% link _usage/meetbot-module.md %}) [18:25:08] RhinosF1: e.g. .startmeeting title or .startmeeting [18:25:20] .startmeeting test [18:25:20] Meeting started! use .action, .agreed, .info, .chairs, .subject and .comments to control the meeting. to end the meeting, type .endmeeting [18:25:22] Users without speaking permission can use .comment #ZppixBot followed by their comment in a PM with me to vocalize themselves. [18:25:43] .chairs RhinosF1 [18:25:44] Meeting chairs are: rhinosf1 [18:25:54] .action this is a test [18:25:55] ACTION: this is a test [18:26:02] .comment worked? [18:26:11] .info [18:26:11] try .info some informative thing [18:26:17] .info worked [18:26:17] INFO: worked [18:26:22] .endmeeting [18:26:22] Meeting ended! total meeting length 62 seconds [18:26:23] Meeting minutes: /zppixbot/%23ZppixBot/2019-11-12-18%3A25_test.html [18:26:45] Voidwalker: https://staff.miraheze.org/wiki/Miraheze_Meetings [18:26:46] [ Permission error - Miraheze Staff Wiki ] - staff.miraheze.org [18:26:49] Just tested it [18:27:39] Well the meetbot module [18:28:45] Voidwalker: Can You see if meetbot stuff can be made public [18:28:59] uh, I don't even know how meetbot works yet [18:29:05] so I need to see what's what [18:32:28] RhinosF1: the meetbot stuff is a pain in the ass [18:32:44] RhinosF1: it wont be made public automatically it requires human intervention [18:33:07] Zppix: we could do with it per #miraheze-staff [18:33:25] RhinosF1: Like i said it would require human intervention to make stuff public [18:33:31] which would require tool access [18:34:04] Zppix: that's rubbish [18:34:10] Any better alternative [18:34:14] RhinosF1: not that im aware of [18:34:20] I might just add a logging bot [18:34:30] Or find out who hosts actual meetbot [18:34:32] RhinosF1: nothing short of rewriting the sopel default meetbot module [18:34:46] there's probably a way to do it [18:35:01] Voidwalker: oh yeah, we would just have to rewrite the default module [18:35:03] Voidwalker: any idea how exactly? [18:35:15] not yet [18:35:33] Voidwalker: if we rewrote the module to save it to /public_html voidwalker and had it restart the webservice in toolforge it could be done automatically [18:35:37] but thats easier said then done [18:35:53] Voidwalker: because we have to get the kubermetes server to exec the command on the bastion server n [18:36:24] well, first things first, where even is the damn file? [18:36:33] Voidwalker: which file? [18:37:02] it generates a file after every meeting, so where does it go [18:37:31] uh hold on let me find it ( i have to actually try to find because thats how i remember lol) Voidwalker [18:38:19] Voidwalker: ~/ZppixBot/public_html/#ZppixBot i know it says its in public_html but it isnt in ~/public_html [18:38:39] Zppix: 18:26:23 Meeting minutes: /zppixbot/%23ZppixBot/2019-11-12-18%3A25_test.html [18:38:40] ~/ZppixBot/public_html/channelname is the dir the logs would go in Voidwalker [18:38:49] RhinosF1: im aware of what the bot says [18:38:56] I'm seeing if we could use the WikiMedia version If That's easier [18:38:59] RhinosF1: im also aware of what i actually see [18:39:14] RhinosF1: not really [18:39:21] RhinosF1: that would be an entirely new bot [18:39:31] RhinosF1: which means another thing to maintain [18:39:33] It's in a separate channel though [18:39:45] No I mean use their instance [18:39:55] RhinosF1: yeah good luck with that [18:39:57] https://tools.wmflabs.org/zppixbot/%23ZppixBot/2019-11-12-18%3A25_test.html [18:39:58] [ test at #ZppixBot, 2019-11-12 18:25 ] - tools.wmflabs.org [18:40:00] it is public [18:40:06] oh [18:40:08] :P [18:40:18] Voidwalker: so {{done}} ? [18:40:20] That's good [18:40:56] .addchannel #miraheze-meetings [18:40:56] Hey Voidwalker, Reception123 or Zppix, RhinosF1 would like to have me in their channel: #miraheze-meetings [18:41:05] hold on it got it [18:41:41] [02ZppixBot-Source] 07Pix1234 pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Jew5U [18:41:42] [02ZppixBot-Source] 07Pix1234 033366334 - + -meetings [18:41:53] RhinosF1: im also gonna merge your other pr [18:42:02] Ok [18:42:09] [02ZppixBot-Source] 07Pix1234 closed pull request 03#107: add my wikis to status config - 13https://git.io/Je2xb [18:42:11] [02ZppixBot-Source] 07Pix1234 pushed 032 commits to 03master [+0/-0/±2] 13https://git.io/Jew5T [18:42:12] [02ZppixBot-Source] 07RhinosF1 03abbb006 - add my wikis to config [18:42:14] [02ZppixBot-Source] 07Pix1234 0378470c7 - Merge pull request #107 from RhinosF1/patch-3 add my wikis to status config [18:42:37] ZppixBot: reload [18:42:38] Zppix: chanops haven't been decided yet but likely just me and Paladox [18:42:38] Zppix: done [18:43:50] should probably have the actual trustees as ops too, since we'd be the ones managing it [18:44:52] Voidwalker: we can add you guys, I think most meetings will likely be at least one trustee and one staffer hosting [18:45:35] But we'll likely have permeant ops that manage day-to-day then op hosts during a meeting [18:45:54] Might give users with a Miraheze cloaks + other verfied wiki users voice [18:47:27] ZppixBot, reload [18:47:29] Voidwalker: done [18:48:07] was a config change for meeting_log_baseurl = https://tools.wmflabs.org/zppixbot/ [18:48:08] [ Home - ZppixBot ] - tools.wmflabs.org [18:48:40] ok [18:50:28] is there a way to view what logs exist other than using server access? [19:03:59] I'm thinking of creating an index.php or index.html in the /#miraheze-meetings/ folder to display what logs are available, or writing in a new module to handle something similar [20:11:33] [02ZppixBot-Source] 07RhinosF1 opened pull request 03#109: + Miraheze-meetings - 13https://git.io/JewFt [20:11:50] Voidwalker, Zppix: ^ [21:45:44] [02ZppixBot-Source] 07RhinosF1 opened pull request 03#110: Add a new custom response - 13https://git.io/JewNc