[00:23:42] the later just needs a review and can be closed I think [00:24:24] for the breaking changes, what’s the process/criteria/whatever for that [00:26:20] [1/6] The process is to read and figure out if anything could affect us. For example, [00:26:20] [2/6] ``` [00:26:21] [3/6] * $wgRCFeeds now explicitly requires a class parameter. The fallback behaviour [00:26:21] [4/6] has been deprecated since 1.38 and has been dropped. [00:26:21] [5/6] ``` [00:26:22] [6/6] affected us [00:36:37] I read it once and couldn't find anything else in mw-config but I didn't feel confident enough to say anything on the task [05:33:03] @wikitideharej is there any progress on https://issue-tracker.miraheze.org/T12328 that could be tracked on the task, im pretty sure i remember more discussion on other software than is listed on there [05:33:44] Not much discussion of substance though. I don't think we still have a real direction of where to go. I think there's a new version of some ticketing system that @rhinosf1 wanted to try [05:35:19] That may have been it [05:35:50] Would be nice to get some progress on it though it feels like something that would basically need to start again from scratch to get momentum [05:35:59] ..not that that would be losing much. [05:44:48] The main problem has been that all the open source solutions suck and all the paid solutions are too expensive [06:51:45] I could also write a version myself and integrate it into a new version of TSPortal. [06:52:05] Do we really want to handroll a ticketing system [06:52:22] It won't be all that hard based on the requirements actually listed on that task. [09:11:33] if it's sufficiently close to something upstream that's okay or basically just needs interface improvement or architecturally damn simple, maybe [09:12:00] especially if the way it handles things is more layer on top of email as opposed to injecting a bunch of unusuable gunk if it collapses [14:03:58] Interesting, I find that a bit hard to believe that for our use case every single OSS ticket software is entirely inadequate in a way that throwing CA at it to fork and adapt wouldn’t fix [16:27:23] @wikitideharej osTicket but it's unreleased with no date yet [16:27:32] Just private beta for v2 last time I checked [16:28:14] No [16:30:15] How bad is v1 [16:30:25] Very [16:32:52] Why so much hope in the second then [16:34:42] Complete rewrite with a brand new UI [16:34:48] It's basically different software [16:37:39] So is it just waiting for that to come out now I guess [16:40:58] Potentially unless anyone has better ideas [18:09:58] Skye and then Reception have projects intended to address the account request flood (which I need to do some cleanup on today. [18:10:10] Those are specific to account requests though and I'm not sure where each is stalled. [18:10:25] Sounds good. Take your time with it.