Tulsa Web Devs press tour
Or as close to anything like a press release that we'll ever have. This Land Press ran a Government 2.0 in Oklahoma article and featured Tulsa Web Devs! w00t!
They also did a live stream from our Tulsa Hackathon event last fall.
Thanks This Land for helping us tell our story!
MDN 2.4.5
Late as usual! MDN 2.4.5 bug list and backlog.
Highlights
- Wiki
Syntax Highlighting
KumaScript is in! (Though it's not available on stage9 yet.)
Migrations are running on stage9 - Bugs
Check the MDN 2.5 backlog for what we're pushing next!
MDN 2.4
MDN 2.4 bug list. This was our first 1-week sprint and release, so there's not as much to report.
Highlights
- Wiki
Nothing shipped, but Les filed the master bug for KumaScript - our replacement for DekiScript. - BrowserID
Fixed lots of little bugs and enabled BrowserID for French, German, Spanish, Polish, and Chinese locales.
MDN 2.4.5
- Wiki
KumaScript lives and I ran it successfully on my local environment!
Syntax highlighting for code samples - both new and migrated
Profile doc activity feed switched to Kuma - Some bugs
So, wiki work continues at a good clip and our process seems to be going well. We're changing our standup time to 10am PT since most of the team is CT or ET now.
Editing MDN with VIM
UPDATED: New screenshot with html filetype! Thanks Screwtape for the tip in the comments!
Yes, it's possible! If you're like me you want to spend as much time in vim as possible. While I appreciate CKEditor on MDN, I personally prefer to edit text in vim, and I think many developers might agree. And since MDN should include content written by developers for developers, here's a way to edit your favorite web developer docs (that would be MDN), using vim. (In my case, MacVim)
- Install the It's All Text Firefox addon.
- Go to the IAT preferences
- set your editor to vim (MacVim.app in my case)
- set your hotkey. (alt+command+e in my case, now that I'm used to Firefox Dev Tools "Inspect" and "Console" keyboard hotkeys)
- Go to the MDN article you want to edit. (Apps/Getting Started in my case)
- Click Edit (duh)
- Click Source
- Type your hotkey!
- Drink beer and edit away!*
- :wq
* groovecoder is not responsible for whatever Sheppy might do to you if you actually edit MDN while intoxicated.
Note: For MacVim you may need to set the "After last window closes: Quit MacVim" preference so it puts you right back to Firefox when you :wq.
MDN 2.3
Released February 28th. We are moving to weekly releases on MDN so these posts are hard to keep up. I will probably start combining releases. And I'm just going to link to the MDN 2.3 bug list instead of linking individual bugs.
- Wiki
migrate tags from MindTouch to Kuma
(Re-)enable tag display and editing
remove extra redirect for locales
verify code samples work post-migration - BrowserID
fix login infinite redirect bug - HTML5 & Apps MWC pages
Paul and Craig cranked out the new HTML5 and Apps landing pages in time for MWC
While Paul was with us he created ScrumBugs! I love it! I always appreciated the way we did Agile/Scrum/XP/whatever at SourceForge.net, and I've been forcing pushing for Mozilla WebDev to adopt some of the same practices. And I just really like pretty graphs! Can you tell?! :)
MDN 2.4 & 2.4.5
We're calling our first weekly sprints 2.4 and 2.4.5, but I think next we'll just move to 2.5, 2.6, ... until we all meet up in New York for MDNYC. At that point we'll probably abandon bugzilla milestones and just use the whiteboard to organize bugs into sprints based on release dates. Until then, here's what we're working on for 2.4 and 2.4.5.
- BrowserID
Hopefully killing all the remaining BrowserID bugs so we can concentrate on wiki - Wiki
Les is rocking lots of KumaScript work
Migrate file attachments
Wiki code syntax highlighting
Refine UI for tag editing
Activate continuous migration on staging server for MDN doc community
