[00:18:51] [1/4] https://cdn.discordapp.com/attachments/1225560610628964423/1553923911018745988/image.jpg?ex=6abb03ea&is=6ab9b26a&hm=f50ec0ce8f88d3b8b6cb21a97a5689185c8f6c32bd0d84ff55fa9c6469184a4e& [00:18:51] [2/4] https://cdn.discordapp.com/attachments/1225560610628964423/1553923911396098171/image.jpg?ex=6abb03ea&is=6ab9b26a&hm=9e8625149597d000cbc9c6d716700deecfc32beac9284ebf39353b1210e58e21& [00:18:52] [3/4] https://cdn.discordapp.com/attachments/1225560610628964423/1553923911702548551/image.jpg?ex=6abb03eb&is=6ab9b26b&hm=89d02ddc5374a5ec8d41b3b09bad6df41c5fa93cc54784cffae283730eb10c68& [00:18:52] [4/4] https://cdn.discordapp.com/attachments/1225560610628964423/1553923912050417785/image.jpg?ex=6abb03eb&is=6ab9b26b&hm=6133bea6d7eafe519eef579b890a4badadf3e29c700e95d1a05bef17d4d87fbb& [00:25:14] [1/4] Could I get some feedback on the following? [00:25:14] [2/4] [[User:Person0192837465/PWR#Imperial_States_of_Unionlandia]] [00:25:15] [3/4] [[User:Person0192837465/PWR#The_Distributist_Encyclopedia]] [00:25:15] [4/4] [[User:Person0192837465/PWR#U8579_Pax_Historia]] [00:25:15]

[1/3] [00:25:15]

[2/3] [00:25:16]

[3/3] [08:17:25] [1/2] If I remember right [08:17:25] [2/2] Wiki request queue is first line of defense/opportunity to shift or sand out bad ones before it gets into you guys (stewards) desks, since you guys don't have a lot of time [08:17:49] [1/2] So it's primarily a question of [08:17:49] [2/2] Is this wiki really worth the trouble to host? [08:19:51] Why are you against commitees? [08:19:56] Just curious about that [08:21:38] I thought you'd already know him by now since he's also at the Oasis [08:28:22] I really don't mind and it gets the right concept across, I just know that is a bad word for some folks [08:28:52] Why is it a "bad word"? Is it because it got a bad rep from wp? [08:29:11] and 'lost in committee' is very real but tbh that's both possible and has already happened to miraheze without the structure, its really just how its structured that matters [08:29:33] or the committee about a committee to form a committee and other virtually pop culture memes about it [08:29:51] I see [14:40:47] [1/3] tldr what i said in #general: please make more posts in #announcements when major errors or bugs occur so people aren't constantly coming in confused. I'm not sure why this resulted in an argument 😂 but I've had instances where I've literally had to forward something tech or whoever said in #general about a bug in our announcements channel to keep those editors who aren't in this [14:40:48] [2/3] channel informed. like, sure, not everyone is on discord or following the announcements channel, but i think it'd cut down on a lot of repeat questions/delays while also keeping people informed. [14:40:48] [3/3] it'd be nice to have updates on social media + clearer announcements on meta when errors occur as well, but I'm mainly focusing on discord because that's the current platform we're using and imo not a huge burden to start doing if already on the platform. [14:43:47] oh wait I have announcement perms [14:44:13] We used to have people whose job in the Tech Team was exclusively communicating technical topics to the community and being a bridge between the Tech Team and the community. We used to call them CES, now they're https://meta.miraheze.org/wiki/Tech:Organization#Community_Liaison, so if this sounds like you... [14:44:31] Should've been done by CA but since you're around I'd say go for it. [14:45:19] it'd probably help to bring them back [14:45:29] I believe there's been none since Agent [14:46:39] oh argument actually i just find it strange that the user group thing didn't get an announcement before the new incident. my ocd just made me a bit upset about the inconsistency bc i think if they're publishing an announcement they should also do so for the user group incident but not only the db error incident [14:46:53] [1/2] i mean, it doesn't even have to be that formal or complex? i was referring to not just the current bug (which has lasted several hours) but also like the accidentally deleted role bug. Just major things people come in and ask about. Just forwarding what tech says when this happens into #announcements "Roles with only one user were accidentally deleted. This will be fixed, but can al [14:46:53] [2/2] so be fixed manually via recreation." [14:47:05] i mean that's part of my argument! [14:47:15] the user group things should've been announced! [14:47:21] [1/2] And imo manually fixing things was a bad use of CA's time. We should've started parallelizing updates 5 hours ago when it was clear that the issue is caused by wikis being on 1.45 so that we can get it done as soon as possible. Otherwise we're stuck fixing things manually for 48 hours straight. [14:47:21] [2/2] Once CA wakes up hopefully he can take a look at my script. [14:47:56] iirc the user group incident wasn't announced because we weren't sure if we could quickly resolve it for all wikis, in which case an announcement wouldn't have been necessary [14:48:20] i think it's fine to announce things that are resolved quickly as long as it's widespread [14:49:00] i mean I've definitely woke up to announcements about db instability that were resolved already [14:49:28] i understand the feeling of not wanting to bother people too much, but i think most people want more announcements not less lol [14:49:31] Turns out it is not resolved quickly and we aren't even recreating the member group... [14:49:52] oh? i thought you must have been recovering them from log [14:50:16] so it's something that can't be resolved then it definitely worths an announcement [14:50:18] it's an ongoing issue from what i can tell. someone just asked about it recently [14:51:19] my brain's slightly fried from trying to keep up with all the different reports, could you do this please [14:51:50] as long as it's clear how to report the issue in a way that's helpful (discord/help desk) [14:52:45] gets justified [14:53:59] while i think that's fair for something like what's currently happening (which is why i made the suggestion of an announcement in the first place in case they just forgot), it feels like a flimsy excuse for something like the user groups bug which is still ongoing after several days (has it been a week?) [14:55:02] i think it's more like making announcements about things haven't been really internalized yet (as in, they forget it's a useful tool they can use), which is why i mentioned it [14:55:17] i also think announcements are good idea i just mean we should be considerate they can be busy and they're all volunteers [14:55:50] i also once reminded about the announcement of the user group thing earlier [14:56:15] yes, I'm not demanding immediate announcements, but I'm suggesting trying to remember to do them because it can also lead to less work on the volunteer end [14:56:39] instead of having to copy-paste the same text over and over again, people either know what to do, or you can forward/point them to the announcement [14:57:26] Done [14:58:09] thanks! [14:59:09] though i don't think it was sent out to servers that's following the channel? 🤔 [14:59:30] that can be a few minutes delay [14:59:31] oh nevermind just got it [14:59:45] you were right lol didn't realize there was a delay [14:59:49] thanks again! [14:59:50] tho the user group thing still doesn't get an announcement [15:00:12] at this point, probably best to wait until this gets resolved [15:01:06] I will complain about this in other places as well. [15:07:07] honestly agree with users who say it might be best to move this to a thread in #support . collect all those having issues in one place and less of a chance to miss anything amidst conversation [15:10:47] there's also someone who tries to gather all phorge tasks in one task: [[phab:T16158]] [15:10:47]

[15:11:28] i don't think this can succeed. ppl usually don't tend to search and browse main page first when they plan to open a task on phorge [15:14:11] not to mention they triaged it lowest [15:14:35] and ppl kinda panicking left and right [15:15:05] i guess we better simply close it? [15:15:33] ppl are obviously opening new tasks instead of searching for a task with no project and triaged lowest [15:16:03] i think at least on discord, we can change the announcements link to a support thread if we make one [15:16:55] and if jenny goes offline or other people come online to help, all the issues are gathered in one place so it's easier to pick up [15:18:26] i closed it for now [15:20:44] btw i'm considering what the announcement says. it says wikis that are still on 1.45 get the db error? afaik the wikis get db error have 1.46 in their special:version [15:23:29] actually @posix_memalign sorry for the ping, but if i made a support thread to collect all the current database error reports, would you be willing to change the announcements link to it? [15:23:53] Sure! [15:25:46] #1.46 Database Error [15:25:52] special:version does not seem like it should be trusted [15:26:25] we did get new 1.46 pager in places like special:search when we got db error [15:27:46] [1/2] new parser function for 1.46 is also working [15:27:47] [2/2] https://cdn.discordapp.com/attachments/1225560610628964423/1554152650235445410/image.png?ex=6abbd8f2&is=6aba8772&hm=f71106f1f4547139923c1e6c91996f5c52e42036ffa77226fc1edc76187bd2bb& [15:28:20] Announcement updated. [15:28:55] Thank you! [15:29:58] it seems like all wikis had their version changed to 1.46, but the script that patches tables and runs maintenance scripts hasn't applied to all wikis [15:30:42] so I think what's happening is wikis are running 1.46 code but the databases haven't been updated for that upgrade [15:31:11] that makes sense. it's just 'wikis still on MediaWiki 1.45' made me confused bc they appear to be on 1.46 [15:31:22] it's more like 'wikis still in process of upgrading' [15:33:42] From https://discord.com/channels/407504499280707585/808001911868489748/1554145702953615492 the upgrade is done but it certainly isn't. Hopefully it's still running SQL as otherwise many wikis would be left in an inconsistent state. [16:23:43] Actually only one part is still running on the other list. [16:26:39] since this got a bit buried [22:09:19] yeah, you'd think lol