[16:12:57] [1/2] Hi, all. I know it has been a very long time since I have actively taken part in any discussion around here so I was wondering how I get up to speed on recent changes to the extension review process. RhinosF1 mentioned the 'WMF-deployed extension = auto-approve' policy was suspended (as of Nov 8) on Phorge, which I had no idea about. That was a surprise, and it's a particulary impora [16:12:57] [2/2] nt one, too, for my role as a Security Reviewer. Is there a noticeboard these day that I should be looking at, perhaps? [16:13:39] Nope, I don't think we ever decided what we were going to do about it [16:13:55] 'it' being? [16:15:44] Coming up with a permanent policy [16:16:08] Just that we'd pay more attention to wmf extensions and they should have some form of review after privacy concerns with campaign events were missed [16:16:29] I think that fell through the cracks [16:16:56] is more confused about the current policy than he was five minutes ago [16:17:25] So... right now, we don't do code review but someone still has to review it for privacy concerns? [16:17:54] no one ever decided [16:18:15] Just that not reviewing them at all isn't enough [16:19:07] We agreed to change the policy but never what the new policy was [16:19:14] As far as my archive searching can find [16:20:13] Well, that's fun. So that just leaves my other question, how do I keep track of policy changes if I am not gonna be in this channel? DMs, emails, etc. would be good but I can see why that's too difficult. [16:20:35] @notaracham @reception123 @wikitideharej can this be raised at the currently happening board meeting? [16:20:55] We should probably update the policies on meta [16:22:08] @rhinosf1 Q: does ops = infra [16:22:22] Kinda [16:22:44] I think we might have fucked this one up @redmin0 tbh [16:23:11] Policy changes should be posted to the wiki [16:23:24] We need to decide on the change first [16:23:33] We just agreed the current policy didn't work [16:23:38] Never on a new one [16:23:41] Well unless CA decided to suspend that part of the policy, I don't think it would be a valid change [16:23:46] Want me to make SRD blue? [16:23:59] Go on [16:24:16] I think the main policy change should rather be to require wikis to present an actual need for new extensions [16:24:21] CA is MIA to remember what he agreed in March [16:24:25] Not just "we want to test it out and see if we like it" [16:24:33] So responsibility is on you [16:24:57] I thought that was our current policy. [16:25:25] Yes I know so that's what I meant, I don't remember agreeing to any formal change for that [16:25:31] So I wondered if CA had [16:25:36] I know we did discuss it though [16:25:37] As i understand the ‘policy’ was that at least one wiki had a usecase/requested it [16:25:53] Well yeah but it isn't strictly applied [16:25:56] @abaddriverlol blue [16:25:57] No idea [16:26:14] We haven't really questioned users on why they really need an extension [16:26:14] We seem to have agreed it's shit but not what to do instead [16:26:22] So can you please be deputy director [16:28:32] We'll discuss it after as the board meeting is still ongoing so I can't really concentrate on two discussions at once [16:53:02] thx [16:53:30] This is gonna take some getting used to [16:53:53] lol [16:53:55] this is so weird [16:53:59] why he blue [16:54:09] https://tenor.com/view/blue-da-ba-dee-eiffel65-gif-14330492 [16:54:22] https://tenor.com/hC9XKNjekQM.gif [16:54:52] @abaddriverlol congratulations on ops, you're my newest server explosion autoping victim [16:55:06] rhinos can finally sleep [16:55:46] i would share a kilo of candy with you but unfortunately you are across the sea [16:55:53] now I actually need to do something when this happens again lol [16:55:59] and I can't just ping the infra role anymore and go back to what I did before [16:56:06] ikrrrr [16:56:34] i mean you hopefully fixed the only reason why shit blows up consistently [16:57:10] I hope so, db171 had a max load of 3.74 in the last 24 hours [16:57:22] that's so ducking good holy [16:57:34] before that the max load was 20-30 [16:58:28] [1/2] still better than whatever happened to db161 recently [16:58:28] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1439660907960733879/image.png?ex=691b5434&is=691a02b4&hm=5fe88055795bc3d3c2cdfa14c89cf48f8a149546f35275eb73ca09109ca860cc& [16:58:44] when you open RCL once [16:58:51] lmao [17:00:09] that is very interesting [19:23:41] international shipping [19:42:50] https://issue-tracker.miraheze.org/T14537 in case anybody has any opinions on this (even though it's stalled on Debian Trixie) [19:43:03] I think it would be very useful to investigate performance issues in the future [20:00:45] [1/2] Nice! I saw Cook profile DPL3 with some tool a while back and he fixed some performance issues on WG's fork. For example, this line retrieves the image if the url could be unused. [20:00:45] [2/2] https://github.com/Universal-Omega/DynamicPageList3/blob/d6e9206e2ed241779134c80e8768b382cad4a52d/includes/Lister/Lister.php#L333