MDN & Kuma progress

Kuma will tear you up with fire attacksI haven't posted in a while for a couple good reasons - I've learned enough django to write more code than words now, and our new intern has taken over most of the project management work for MDN. So, I have time and ability to code and I'm using it! I should still post about *what* we're coding, so here we go.

We've done a lot since my first status post 4 months ago. We released Demo Studio, Learning, and Dev Derby from our "mdn" branch. I played some small parts in the Demo Studio work, and I implemented the Learning feature while I myself learned our jingo and tower libraries.

I did some important but less-visible work - I copied our mdn code from our old mdn repository into our new kuma repository. We maintain an mdn branch in kuma where we do main development to push to the live site. The master branch holds all of the kuma-only features. We frequently merge mdn into master to keep master current. I set up continuous integration projects for both kuma and mdn on the Mozilla jenkins server.

All along I've been fielding bugs on our old MindTouch/DekiWiki system and helped prepare our upgrade from MindTouch 9 to MindTouch 10, currently running on the MDN staging server.

Finally, just last week, I broke free from MDN features & infrastructure to work on the kuma wiki features. The kuma wiki is cloned from the kitsune wiki that powers SUMO. So, we're starting with a large solid wiki foundation already. On Thursday I started changing the kuma wiki templates to match our mdn templates. Along the way, I added ckeditor to the wiki app (just like our existing MindTouch), removed and/or hid many fields that SUMO requires that we will not, and restored and refactored over 80 wiki unit tests. (Which gave me a nice bump up the Leader board in our cigame.) Now I'm working on article viewing - our implementation is different since we store HTML content rather than wiki markup, so we need to change the way we bleach content - and I'll work on article previews next. All of this is continuously pushed to our kuma staging server. Very Soon™ we should be able to invite community testers to the staging server to start banging on kuma wiki and giving us feedback.

Outside of my Mozilla work, I gave a Web Application Security talk for Tulsa School of Dev 2011 along with other members of Tulsa Web Devs. I hacked the crap out of a WordPress site right after our other guys promoted WordPress as a great open-source CMS, which it really is; I feel bad to have hacked it in front of a bunch of Microsoft fanboi's, but oh well. Just please PLEASE keep your WordPress updated and be careful about which plugins you install!

Outside of my tech work, my wife and I had our 2nd baby girl on April 8th - River Daphne. It's been quite a learning experience with 2 kids under the age of 2, but we're starting to adapt. I've also made a couple of trips out to Clear Creek Abbey to help Brother Paul start brewing beer for the monks and guests. This last time I got to sample an American Pale, an English Brown, and a Munich Lager - all of them were great; hard to believe Brother Paul has only been brewing a few months.

Enough words. Time for more code.

Question or comment about this post? Tell me on GitHub.

MDN & Kuma progress / groovecoder by groovecoder is licensed under a Creative Commons Attribution-ShareAlike CC BY-SA
  1. Hrm, so Kuma will use the same editor as Deki? And the editor was the main reason why I abandoned editing anything on devmo/MDC/MDN. Well, I guess not much is lost by keeping me out, in the end. ;-)
  2. It will use ckeditor, yeah. I'm not the biggest fan of ckeditor either, but changing that would probably be Too Much Change™ all at once. ;)
  3. @groovecoder What were you thinking when you named this wikis Kuma and Deki? So, say I go to Nairobi Kenya or anywhere in East Africa. Say am speaking at a conference at the iHub Centre in Nairobi. I have to tell the audience to find more information and resources at Kuma and Deki on MDC/MDN. Basically this translates to Kuma => Vagina, Deki => Penis/Cock. I know Swahili names are easy to use and sound awesome. Like Siri, Safari, Mambo, Jumla/Joomla etc. But think before you use them. How does a teacher say that to a class of young people without looking like an idiot. Amend please. Nelson Kelem
  4. We inherited the "Kitsune" code from https://support.mozilla.org. "Kitsune" means "Fox" in Japanese. We picked "Kuma" - the Japanese word for "Bear". It wasn't until later that we discovered the Swahili word. :( At some point I think Mozilla Webdev should make our code-names more descriptive. We should have MDN, SUMO, and AMO; not Kuma, Kitsune, and Zamboni. Anyway, in a situation where Swahili is widely-known, just refer to the site as "MDN". They are synonymous.
MDN & Kuma progress / groovecoder by groovecoder is licensed under a Creative Commons Attribution-ShareAlike CC BY-SA