Before anything is installed at Miraheze, it needs a security review. I apologize that I've been slow at doing this, but lately my volunteer hours have been going into writing us a privacy policy, terms of service, etc.

Eventually we'll allow you to enable/disable extensions that we have installed through a ManageWiki interface. It's an ongoing process, detailed in T194.

On the other hand, you do have access to the server files. Everything is on GitHub: https://github.com/miraheze/mw-config/ is the most relevant repo, though some of the others are useful too. We accept pull requests! This is the main way to add extensions that we already have installed. The process for installing a new extension is a bit more complicated -- how do you feel about git submodule?

Semantic Wiki is not installed for performance/financial/technical reasons. While it's cool and secure, it would take more servers than we have to host wikis like that. It's not our general audience.

Anyway, I'll get to reviewing those other extensions.

Oh, never mind. @DeltaQuad has taken this task from me, so I no longer want to review those extensions. Sorry to get your hopes up.

In T1122#21409, @labster wrote:

Oh, never mind. @DeltaQuad has taken this task from me, so I no longer want to review those extensions. Sorry to get your hopes up.

I wasn't trying to interfere. I created a Herald rule to auto-assign tasks involving extensions but not logos/favicons to me, as I can easily create PR's for installed extensions. However, I assumed that the rule would only trigger for new tasks. I didn't expect it to trigger for tasks that were already assigned to someone else. I've disabled the rule now, my bad.

In T1122#21405, @labster wrote:

Before anything is installed at Miraheze, it needs a security review. I apologize that I've been slow at doing this, but lately my volunteer hours have been going into writing us a privacy policy, terms of service, etc.

Eventually we'll allow you to enable/disable extensions that we have installed through a ManageWiki interface. It's an ongoing process, detailed in T194.

On the other hand, you do have access to the server files. Everything is on GitHub: https://github.com/miraheze/mw-config/ is the most relevant repo, though some of the others are useful too. We accept pull requests! This is the main way to add extensions that we already have installed. The process for installing a new extension is a bit more complicated -- how do you feel about git submodule?

Semantic Wiki is not installed for performance/financial/technical reasons. While it's cool and secure, it would take more servers than we have to host wikis like that. It's not our general audience.

Anyway, I'll get to reviewing those other extensions.

Hi Labster.

Thanks a lot for getting back to me. Thanks for the information on what you can't do (install semantic web). Regarding GitHub - I am almost a complete novice.

However, I have forked the mw-config repository under my GitHub user (gumbee86). The way I understand it:

• The list of extensions that are automatically enabled on my wiki is listed in "GlobalExtensions.php"
• The list of extensions that are approved and can be enabled in my wiki is listed in "LocalExtensions.php"
• If I want to add an approved extension to my wiki, then I just add to the relevant section of "LocalSettings.php" the code 'wikidmatland' => true . However, presumably I can't change the master repository, so have to do this in my fork.

The 2 remaining questions I have are then:

• Can I ask for my wiki to point to my fork so that I can easily add and remove approved extensions?
• If I can't do the above, I understand that a pull request is me basically changing the code in my fork, and then submitting a pull request to get you to approve and incorporate my change into your code. Is that correct, and the best way to do it?

Thanks again,
Jono

@JdeJong Yes, the only way to have it changed is by making a pull reuqest on the Miraheze/mw-config GitHub repo. These are generally merged in reasonable time.

@labster

Thanks. I'll go ahead and do that to add the extensions I want in my fork, and will then submit them through a pull request..

I'm looking forward to seeing how that all works.

In T1122#22155, @Reception123 wrote:

@JdeJong Yes, the only way to have it changed is by making a pull reuqest on the Miraheze/mw-config GitHub repo. These are generally merged in reasonable time.

Keyword there is generally. Sometimes requests sit unnoticed for 12 or even close to 24 hours. However, be assured that they are almost always reviewed at some point.

It depends on the type of the request. If it is enabling an already installed extension it can be merged in a few hours.
Also an old sysadmn @revi with a different timezone will return to Miraheze so the process should speed up anyway.

I've started reviewing Extension:W4G Rating Bar, and I've opened a pull request to get started: https://github.com/redekopmark/RatingBar/pull/8 That PR is more in the hopes of someone else (read: not me) becoming the maintainer of that extension, but we'll see how that goes. Little known fact: licensing is actually the first step of security review, because if we can't copy it, we can't run it!

If I want to add an approved extension to my wiki, then I just add to the relevant section of "LocalSettings.php" the code 'wikidmatland' => true . However, presumably I can't change the master repository, so have to do this in my fork.

So close to correct. Actually, you'll need to use 'wikidmatlandwiki '=> true, with the comma at the end, and 'wiki' after the subdomain of your wiki. We use the "-wiki" suffix to make sure that no one tries to create mysql or information_schema wikis that would either not work or leak internal information.

@labster the PR has been merged.

@labster