[04:54:24] <MirahezeRelay>	 <pixldev> https://issue-tracker.miraheze.org/T15045 do we have any requirement to have a page on mw.org for exts
[04:55:21] <MirahezeRelay>	 <pixldev> would love at least a proper readme
[05:01:45] <MirahezeRelay>	 <aeywoo, replying to pixldev> Afaik we did?
[05:03:59] <MirahezeRelay>	 <aeywoo> Also, if these are just changes to Vector legacy, why can't they just replicate this with CSS/JS?
[05:04:28] <MirahezeRelay>	 <aeywoo> Doesn't make much sense to have a clone of Vector just with some changes, because it'll still have vector-2022 as a part of it. And if you have regular vector enabled it won't be compatible.
[05:05:36] <MirahezeRelay>	 <aeywoo> They should prob remove the 2022 part of the skin if they aren't going to use it.
[05:05:52] <MirahezeRelay>	 <posix_memalign, replying to pixldev> It's not a hard requirement (e.g. Bucket doesn't have it, nor did ImgTag pre-approval) but rather one intended to exclude extensions with no documentation. At least that's my personal interpretation.
[05:06:24] <MirahezeRelay>	 <aeywoo, replying to posix_memalign> Well, the readme in their repo is blank.
[05:31:47] <MirahezeRelay>	 <cosmicalpha, replying to pixldev> Much more scrutiny if there if zero documentation.
[05:33:06] <MirahezeRelay>	 <cosmicalpha> We dont have hard policy on it but I also don't like approving hacks of other skins exactly either as it can mostly be done via CSS/JS and it is more likely to break down the line and they'll have to keep maintaining it at our upgrade pace.