[02:44:00] there's another way to view it. Things like "wiki about the world's monuments" can be safely considered a fork of Wikipedia, even if some specific monuments aren't on it yet, they obviously will be added [05:27:13] @posix_memalign For Miraheze Monthly, only tech tip and wiki highlights left. I assume you are handling the highlights since I am not familiar with them (where do you find these wikis) for tech tip maybe asking other tech for suggestions, or @pskyechology as the tech correspondent 👀 [07:39:25] [1/2] Wiki highlights is imo easier than the rest because they just require a short description. E.g. Pinnipedia is a wiki about seals which I think is pretty neat because it's a topic you don't see on most wikis. [07:39:25] [2/2] For tech tips I think the current one on Code Mirror 6 syntax highlighting works. [07:40:23] If anyone can finish MH Monthly that'll be great. If not, I expect myself to have more time tomorrow so I can finish it off as well. [09:35:46] Not really, Wikipedia is specifically an encyclopedia of everything. A clearly constrained topic doesn't fall within that. It's when you get a request about rock climbing, aromatherapy, knitting, dinosaurs, and osteoporosis that the Wikipedia restriction is relevant. [09:44:51] So what would be considered a broad topic and a specific one? A broad one would be something like disease, animals, ancient animals or such? And specific ones are ones that have a strong topic to go off from, such as a game or documentation software? [09:57:39] It honestly depends on the amount of detail per item and plenty of other things. Like Raidarr said, it's one of those things that varies by volunteer. I probably wouldn't have declined the landmarks one, but there are probably also things I'd deny that other reviewers wouldn't. [09:59:39] There are requests that are clearly too broad/too narrow and wikis that are clearly fine, but most requests are in the grey areas somewhere in between and it's mostly discretion and how the request reads at that point. [10:13:49] uh huh [10:14:27] But what would you give as examples that you will reject and examples you will approve without further clarification? [11:01:02] <_arawynn> [1/2] Too broad would for example be a Wiki for all the history and notable people of the world. [11:01:02] <_arawynn> [2/2] Because like you can fill books over books about the history of lets say Paris or London alone. [11:25:11] [[Special:Log/Sakurababochka]] is my actual reviewing record for reference if needed, but as a general rule I don't often immediately approve/decline anything. The only exceptions to that are requests which after AI review have improved to the point where there's no major issue, or requests which are clearly incompatible with policy. [11:25:13] [11:57:35] So is it mostly just vibes + some guidelines when approving/rejecting wiki requests? [12:40:03] [1/16] No, it's mostly policy. It's just that some specific parts of that are somewhat subjective. My workflow is something like: [12:40:04] [2/16] 1. Is it a blatant policy breach? [12:40:04] [3/16] > If yes decline, else continue to 2. [12:40:04] [4/16] 2. Does it have a high risk of being a policy issue? [12:40:04] [5/16] > If no, continue to step 3. If yes ask how they'll mitigate that and decline if insufficient, if satisfactory proceed to step 3, if ambiguous seek second opinion. [12:40:05] [6/16] -# Very few high risk requests produce anything satisfactory here. [12:40:05] [7/16] 3. Is it one of a list of topics with special courses of action (eg. Steward decision instead of reviewer for -ball wikis, specific clarification needed for NSFW wikis, etc.)? [12:40:05] [8/16] > If yes, proceed accordingly, then continue to 4. Else go to 4 directly. [12:40:06] [9/16] 4. Can you tell what the wiki is actually going to be about? [12:40:06] [10/16] > If yes proceed to 5, if not request topic clarification and repeat steps 1-4. [12:40:06] [11/16] 5. Is there some attempt at describing structure (for example, "this wiki will document areas, characters, and abilities")? [12:40:07] [12/16] > If yes proceed to 6, if not request scope & content clarification and repeat. [12:40:07] [13/16] 6. Is the scope sufficiently bounded to keep the wiki cohesive but not so small that it makes the wiki tiny? [12:40:08] [14/16] > This is the only real vibe-based question, and it's more experience than vibes. If yes then proceed to 7, else request scope change and repeat from 1. [12:40:08] [15/16] 7. Check title, subdomain, and circumstantials. If all good then approve. [12:40:09] [16/16] In practice I do all this at once, but it's easier to explain in steps. [12:41:34] uh huh... [12:53:02] It looks quite complicated like that, but it's basically a cycle of "can I approve/should I decline this" and if neither, what do I need to know to be able to decide. [22:47:00] policy outright does not cover many edge cases nor many scrutiny cases [22:47:24] https://meta.miraheze.org/wiki/Help:Restricted_Wiki_Topics serves as a generally official extension providing further rationale to build from [22:47:56] assorted guides and informal guidance further serves to fill in gaps [22:50:09] [1/2] the practice is not far from the existence of real world judges in practice having a variety of responses to what is ultimately a broad and not exceptionally well defined legal system though at least we have some options to correct ambiguities; though, scope broadness is one of the trickiest points, and my position can lean more permissive than the team and some of my peers on what c [22:50:09] [2/2] an be accepted depending on conditions. In the end a broader team review/steward escalation is an encouraged appeal recourse for fuzzier instances especially where policy as written does not support a decline, which can offer a more collective or senior final answer to the case.