OK, I have to ask, what are you planning to use Extension:RelatedSites for? I can give it a security pass because it's used on a WMF wiki (wikivoyage). But it's only used on the wikivoyage wikis -- and it looks like the plan is to remove it: https://phabricator.wikimedia.org/T128326
So while it's OK now, I just don't know if we want to get in the situation where your wiki is the only customer for this extension. It would pass the maintenance burden on to Miraheze. So I guess the question is: What are you trying to achieve with it? So maybe we could come up with an alternate way you can get there? If not, I guess an install is OK.
Very surprised by the discussion you linked to as a look at the extension's page doesn't convey that at all! The only site I was thinking of using that extension with was Wikipedia. My intent was to avoid repeating "For background information see Wikipedia's article XYZ at http..." in many articles. I also wanted to encourage wiki editors to avoid duplicating Wikipedia's content overall.
@Calnation, you never actually told me what to do on RelatedSites. You can do something similar with a template, of course, and include it in relevant pages. Or we can go ahead with this extension, I guess.
Also don't be surprised by the the extension pages because they can be years out of date for what the extension actually does.
Drop RelatedSites for now as it's just holding things down. Also, Extension:CreateArticle might not be necessary if PageForms is as powerful as it seems (i.e. implementing that first plz).
@labster I have never used MultiBoilerplate. Does it allow duplication of any existing article like Duplicator does?
Let me add that for Duplicator I'm not looking to use it for cases where an article pattern is very recurring that it's better handled with a templating of some sort. It's more for simpler cases when a type of article is so similar to an existing one that duplicating and editing from there is the shortest route.
For templating I'm counting on PageForms extension. Pretty powerful.
@Calnation Unfortunately that Code Climate tool makes me feel somewhat dumber than before I looked. Complaints about MW API complexity (yeah I know), complaints about calling constructors as static methods (how are we supposed to avoid that?), complaints about code style in extensions (oh I am so aware of this problem already).
Extension:CreateRedirect is approved for install, no security issues found. It feels a bit like changing a lightbulb by rotating the house, but nothing harmful or over-wasteful of CPU. Just uh, be careful about redirecting to categories, there's a bug here because of this. Workaround is to use the colon, Luke.
The analogy actually came from this: http://shadow.cat/blog/matt-s-trout/war-stories-open-sesame/
That's my company he's talking about, # 1. The analogy is what one of his friends said on reading the blog post above; he retold me in person I think. The idea being that you can either rotate the lightbulb into the socket, or you can rotate the socket (which may be attached to a house).
In terms of this particular piece of software, it creates an Article object, then creates another request object internally and fills it with parameters, then executes that request. Rather than doing a page edit on the Article object it created at the beginning.
OK, the word on Extension:PageForms is that I don't have time to do a standard review of it. I'm thinking both Extension:PageForms and Extension:Cargo are in the 10kLOC range, which means that they're reasonably mature products. And a random look at some files shows that yes, Yaron Koren writes some good PHP; a full readthrough isn't necessary like most crappy extensions. So I'm going to say security approved on that basis for both Cargo and PageForms.
(As a counter-example of a large extension I wasn't going to approve, look to DPL (third-party) which is a mature product in the same sense as wine with a hint of vinegar.)
That said, I have no idea about resource requirements for either extension, other than to note that it's a piece split off from Semantic Wiki. So I can't really offer guidance here to the sysadmin team as to whether installing it is within our capabilities.
If I'm not mistaken Extension:PageForms can be installed without Extension:Cargo as well though I think that would limit some of it's functions.
@Reception123 Thanks for Duplicator. I'd love to see Extension:CreateRedirect and PageForms soon since we got the green light on those as well.
@labster What did you think of Extension:Moderation in terms of functionality? I requested it cuz when I looked at FlaggedRevs, it just seemed a bit tortuous.