Topic on User talk:Kghbln

Leucosticte (talkcontribs)

So, I committed Extension:ROT13 to GitHub. It wasn't so bad. As mentioned earlier, I went in expecting some serious punishment; however, I came away feeling as though I'd been only mildly disciplined by a moderately-skilled and halfhearted dominatrix. It left me unsatiated and yearning for more. Therefore, I'm going to work on what is apparently one of the less-documented areas of the MediaWiki codebase, external storage! Surely I will come away from that experience bruised and whimpering, brutally chastized but having secretly and perversely loved every moment of it. If it were otherwise, I would have spoken the safeword (or safe phrase), "I'm switching to a different open-source project."

Kghbln (talkcontribs)

I knew I wouldn't be too bad and I am happy that it did not mistreat you too much. :) Yeah, there are unfortunately a lot of only thinly documented areas. Nice that you want to tackle it!

Cheers

Leucosticte (talkcontribs)

As it turned out, I was able to use Revision::newFromArchiveRow(), ContentHandler::getContentText(), and Revision::getContent() to avoid needing to write my own code for handling external storage. I was shuddering at the thought of needing to set up my own external storage system for testing; but fortunately the programming was already done by others and I needed only make use of it. Whew, that was a close one! (It's always unpleasant to find out you just unnecessarily reinvented the wheel with an inferior design to what was already out there. That's basically what happened with Extension:EmailDeletedPages.)

By the way, you definitely deserve that Tireless Contributor Barnstar. Thanks for cleaning up some of those extension pages; I'm learning to just copy and paste some of your work into new extension pages. The only problem is, now that the new stuff will be in Github, how will you internationalize? Hmm...

Kghbln (talkcontribs)

Lucky you this time. To reinvent the wheel is a tedious task one should really avoid. Sometimes it still happens but this should really be an exception. Probably asking in IRC is a good shot for finding out certain information in a lot of instances. I find the people out there pretty helpful.

Before I forget: Thanks for the compliment. It is always good it people value one's work. :)

Kghbln (talkcontribs)

I will translate at GitHub. It is as easy as doing it on wiki. :)

Leucosticte (talkcontribs)

Oh, I thought I had to add you as a committer.

Kghbln (talkcontribs)

I will just fork an send a pull request. :)

Leucosticte (talkcontribs)

I still have to approve it, though. What if I get hit by a bus? Who will approve your pull requests then? Do you want to be a co-owner of these repositories in case that happens?

Kghbln (talkcontribs)

Let's hope that this will not happen. However, there are a lot of reasons not to be online for some more or less longer time spans. Thus it is always good to have a fall-back solution. So yes, you may add me as a co-owner if you like. My only problem will be that I have only very limited knowledge to assess code changes since I am not a programmer.

In case no further development is done or may be done a cloned fork of the code will be the best solution.

Leucosticte (talkcontribs)

Oh noes, I've been naming all these repositories MediaWikiFoo when they should have been simply Foo. When people clone them, they get a folder with that superfluous "MediaWiki" in front. I had just wanted to make sure I distinguished those repositories from any other Foo out there, but it turns out it's unnecessary because they put /leucosticte/ in front anyway, e.g. https://github.com/leucosticte/MediaWikiInterwikiMap Fortunately, renaming the repositories turned out not to be nearly as difficult as I thought it would be.

Kghbln (talkcontribs)

Oops, actually I could have told you. Since I did not git clone one of your extensions, I did not stumble over this as a reminder for me. Cool to know that renaming a repo is not very difficult.