[02:31:19] a purely procedural question for [[Miraheze Volunteers]] [02:31:19] https://meta.miraheze.org/wiki/Miraheze_Volunteers [02:31:52] is our aim to group all volunteers in together or create 2 sections, one for community elected, and one for non-status volunteers? [02:35:19] [discord] Hmmm, given current format, that'd be a bit challenging since several folks hold a mix of the two. [02:35:38] [discord] That'd be a good point of data we don't have today on the contributing page, perhaps that's a better fit for there? [02:36:00] [discord] That'd be a good point the 'contributing' page doesn't differentiate today, perhaps that's a better fit for there? (edited) [02:36:12] yeah [02:36:22] [discord] That'd be a good data point the 'contributing' page doesn't differentiate today, perhaps that's a better fit for there? (edited) [02:36:26] i think it's getting really messy adding in both status and non-status users on MH Volunteers [02:36:33] perhaps two different tables? [02:36:51] [discord] If you're making edits, I'd also suggest adding a column for Discord name since that's usually got more traffic than IRC these days [02:37:10] yeah, happy to [02:37:19] [discord] I didn't know that page existed until today, still need to add my info there. 🙂 [02:40:17] [discord] At the risk of making it even more unusable, perhaps we should consider [02:40:18] [discord] 1. splitting elected vs unelected roles into separate columns, and/or [02:40:19] [discord] 2. Bullet-list the list of roles within the cell [02:40:21] [discord] Not sure if that'd improve readability, but that was one solution that came to mind [02:40:34] yeah i would support that [02:40:36] and streamline [02:40:45] Community support and editor seem to be the same thing [02:40:56] though it's listed separately [02:41:17] [discord] Not necessarily, though one is often also the other [02:42:09] any ideas for streamlining? [02:49:14] [discord] I'll think on it, my current intuition is saying this is kind of backwards for usability and should maybe be refocused based on roles or 'paths/avenues' [02:49:43] [discord] Still worth having a roster in this format though. [02:52:46] Yeah I agree that it should be lessened [02:53:01] for the sake of not doing unnecessary work, i'll hold off for now [02:58:57] [discord] Sounds good, I'm also mostly off for the day, so won't be much further brainstorming help [02:59:38] gotcha [14:13:54] [discord] Are there any updates on the database issue? [14:14:21] [discord] did you see yesterday's meeting updates [14:14:40] [discord] mainly referenced in #announcements and posted on the Community Noticeboard [15:36:59] [discord] Hello! [15:48:28] [discord] o7 [16:38:29] [discord] Ok ok [16:38:39] [discord] Why is the wiki down [16:39:37] [discord] See #announcements and this post on meta community noticeboard (https://meta.miraheze.org/wiki/Community_noticeboard#Db141_update) [16:39:38] [url] Community noticeboard - Miraheze Meta | meta.miraheze.org [16:40:39] [discord] Short version, if you're getting a 'temporarily unavailable' error, it's because there was a series of hardware failures that have brought down several wikis. [16:40:40] [discord] [16:40:41] [discord] Volunteer staff are doing everything they can to get data recovered and restore wikis, but that solution will be measured in weeks not days. [16:40:46] [discord] Short version, if you're getting a 'temporarily unavailable' error, it's because there was a series of hardware failures that have brought down several wikis. [16:40:46] [discord] [16:40:48] [discord] Volunteer staff are doing everything they can to get data recovered and restore wikis, but that solution will be measured in week/weeks not days. (edited) [16:40:55] [discord] Ok [19:39:43] [[Requests for Comment/CVT intervention]] can be closed now, right? [19:39:43] https://meta.miraheze.org/wiki/Requests_for_Comment/CVT_intervention [19:39:59] it's been over 45 days since the original opening [21:02:33] [discord] No non-involved Steward has been around to close it [21:12:51] ah gotcha that makes sense [21:13:19] at a certain point does the involvement of a steward matter? if there’s clear consensus and the rfc is stale [21:14:53] [discord] that is the subject of another ongoing rfc [21:14:53] [discord] That's actually the point of another open RfC. 🙂 https://meta.miraheze.org/wiki/Requests_for_Comment/Involved_discussion_closure [21:14:54] [url] Requests for Comment/Involved discussion closure - Miraheze Meta | meta.miraheze.org [21:16:16] [discord] Current unwritten practice is that closing steward shouldn't have been involved with the topic to avoid appearance of conflict of interest/supervoting, but given small number of available stewards, this codifies clear exceptions to the process. [21:18:23] oh haha i didn’t even realize [21:18:32] yeah i would support that [21:26:19] [discord] Feel free to add your opinion either way when you have a free moment, unfortunately there's been less votes cast on those open RfCs than I'd personally like given the nature of the changes proposed. [21:26:28] [discord] Feel free to add your opinion on Meta either way when you have a free moment, unfortunately there's been less votes cast on those open RfCs than I'd personally like given the nature of the changes proposed. (edited) [21:26:44] [discord] Feel free to add your opinion on Meta either way when you have a free moment, unfortunately there's been fewer votes cast on those open RfCs than I'd personally like given the nature of the changes proposed. (edited) [21:28:32] Remember that every edit is a whole repeat of your message on IRC. [21:31:01] [discord] <06000208> that should be noted somewhere in the discord like the channel description or pins. my presumption with my knowledge of chat bridges was that edits wouldn't be relayed, but I suppose resending in case of important ones is more prudent [21:32:25] [discord] Thanks for the heads-up, I wasn't aware of this but that jibes with the nature of a cross-platform bridge channel. [21:32:25] [discord] [21:32:26] [discord] I have a nasty habit of realizing critical edits after send that I'll be more mindful of in relay channels going forward. [21:32:28] [discord] [21:32:29] [discord] Sorry to the IRC folks who've been inundated with my edit-perfectionism. 😅 [22:32:03] [discord] BRING FOHS ARCHIVE BACK [23:02:50] Please be patient [23:03:23] We can’t rush data recovery [23:07:10] [discord] ok thanks mack