MediaWiki Contributions: My Extensions

Recently, I have decided that I want to start writing some extensions for the MediaWiki wiki engine. This is, in addition to being a chance for me get a hands-on knowledge of the project and its code base, a real opportunity to actually contribute to the software I have been using for ages.

Of course, it might be that the extensions I will write won’t be that useful. Indeed, several others exist that already do what my first extension is supposed to achieve. However, the way they go about it is not as tidy and neat as I am used to. Their set up and configuration is not minimal. They have not kept up with the best practices of software development, and have not kept the pace of growth of the Object-oriented paradigm within the PHP community.

Most importantly, they are not well maintained. I remember well that my OOD professor used to say that a software dies the day its maintenance is discontinued.

So, I will be writing a state-of-the-art and well-designed (hopefully) extension to handle the job of preloading user specified texts into newly created pages, while allowing them to maintain control of this aspect of their Wikis without having to have any knowledge of programming.

I have currently requested access to Gerrit and Git for the MediaWiki codebase and will hopefully start coding as soon as I get this access.


Well, I am kind of disappointed in the whole MediaWiki developer community. It took them four days to review and then grant my request, even though the influx of requests was not that high (10 per 5 days).

Afterwards, I had to request, separately, for git access, and now, after a whole week my request has not even been reviewed.

Will be posting updates on this.

New Updates

Well, I officially give up. I don’t think I will be pursuing this extension, since the MediaWiki community don’t seem to really want to take new users.

I might perhaps work on this on my own and then publish the extension somewhere else, and make the code available publicly.

Leave a Reply

Your email address will not be published. Required fields are marked *