[01:15:21] how long does it typically take for requests to come back? [01:40:18] [1/4] Happy to give a little more context here. [01:40:18] [2/4] All requests are reviewed by volunteers as time allows, all of whom have full time jobs and/or other outside obligations. [01:40:18] [3/4] We don't have a strict time to review but most requests receive a response (even if it's a request for more information) within 24 hours. [01:40:19] [4/4] Average response time for new requests is 4-6 hours depending on availability but can skew a bit higher when volunteers aren't available. [01:41:34] I'm probably the most frequent reviewer but am unfortunately booked solid today. If nobody gets to you in the meantime I'll make sure to review once I'm back at a keyboard [01:41:56] Alright, thanks for filling me in [02:42:50] Sounds like you could do with some more reviewers [02:49:41] Yep, going to get a few more policies in place and then look at what we want to do re: elections and appointments [02:56:20] With a little instruction on what’s needed for the job, I’d be happy to help out. [03:04:45] [1/2] Most folks who aren't former MH volunteers are starting from a pretty similar place in that respect. [03:04:45] [2/2] I'll chat w the others on how we want to move forward w expanding the volunteer bench further but will keep you apprised. [03:17:14] The ultimate goal is elections, appointments are only temporary and will be reconfirmed in a few months [03:17:25] The goal for launching a democratic WikiTide is around December [03:24:17] Will that be the same for WikiForge? [03:28:39] No, WikiForge is completely different. It doesn't make sense for the democratic model to be applied on WikiForge but it does on WikiTide which is a non-profit [03:56:10] WF staff (once we begin expanding that definition) will likely be some form of employee/contractor/consultant, so hire/fire decisions def won't be community driven. [04:38:37] [1/2] I should learn the infrastructure behind MediaWiki. This is the kind of stuff I'd love to get behind, rather than just throwing my money at things lol [04:38:38] [2/2] Also community votes to cause a crumbling of the entire platform almost sounds rather anarchistic yeah lol [04:43:16] [1/2] Definitely. MediaWiki is just such a complex beast though. You have MySQL that you have to deal with, Memcached if you want to have it load at a decent speed, Redis so that jobs like category updates process, Varnish to cache your content, configuring things like the i18n and parser caches, and so much more. It'd be awesome if Wikimedia simplified the whole proc [04:43:17] [2/2] ess [04:43:36] Wiki hosting can be expensive too. I've seen some hosts offer €40+ hosting/mo. [04:43:46] WikiForge offers a simple $9.99 model at least [04:45:08] That said, if you've got some existing competency with code, network management and/or cloud computing, it's a great stretch of your skills [04:45:43] And we always appreciate more folks willing to dive in on the technical side of things, not everyone's strong suit [04:45:44] Dealing with MediaWiki has taught me loads that helps me so much in my field of work and activities [04:46:32] Cool, from that list - I know a tiny bit of MySQL and that's it. XD I would actually have expected such a widely used platform to have a bit more consistency in its infrastructure so, am surprised. Plus if I know more about MediaWiki presumably I can make some extensions cause I do have some ideas. [04:49:56] MediaWiki docs can be so frustrating. You sort of have to know where to look for something as Google won't help 😢 [04:50:25] Heck yeah. I do like learning new stuff. I wonder if MediaWiki is popular enough to have LinkedIn Learning courses... work gives me a free account for it but they don't have a rule on how I can use it. B) [04:50:48] Lol What about Chat GPT? [04:51:14] It outputs code that would've been valid 3 versions ago but now fatals out in the latest version lol [04:51:29] yeah that tracks lol [04:51:30] every version of MW refactors something major, all the time [04:51:50] That explains why so many extensions break [04:52:08] [1/3] Regarding the community vote thing: that one is absolutely a tricky balance to strike. [04:52:08] [2/3] The service many of the founding members/volunteers here came from was run mostly by community vote alongside the efforts of some insanely dedicated volunteers, with some carveouts for legal stuff (domain of the board of directors) and technical stuff (domain of the technical team) [04:52:09] [3/3] We saw firsthand where that worked well and where it really, really didn't. That's a balance we're hoping to push in a healthier direction under this project. [04:52:32] exactly this, yep [04:52:59] devs have to be stalking Phabricator or know who to talk to to make sure they know what's going to break in the next version [04:56:21] Yeah, and just.. having folks who make the extensions to still be on the internet a year or two later is a tall order in itself. Lol [05:14:02] Out of curiosity, how did y'all get into MediaWiki anyway :) [05:14:11] Or like, how did you learn the infrastructure behind it [05:57:51] Better Q for Agent, my specialty is more on front-end wiki management stuff though I'm starting to explore backend as time allows. [13:33:02] Hiya, not sure if everything’s down again for everyone, but I’m receiving a “wiki not found” error on my end. [15:02:15] [1/2] The MediaWiki documentation is by far the easiest way to learn, and probably the best resource. [15:02:16] [2/2] I'd also recommend joining the MW discord, which can be helpful as there are quite a few developers who work for WMF in there. [19:50:25] Thank you! :) [21:36:58] [[test]] [21:37:00]