Mozilla & WordPress

Mozilla WordPress

TL;DR - I made the Promote MDN WordPress plugin and enjoyed it; why isn't(?) there a more intentional relationship between Mozilla & WordPress communities?

WordPress development

To make the Promote MDN WordPress plugin these last couple weeks, I've worked with WordPress more than I have in the previous decade. I've run dozens of sites with WordPress, but have never been active as a developer or contributor. Observations:

  • Keep code tidy - Okay, so there's globals and no MVC. But I copied messy code from SEO Smart Links, ran it thru PHP_CodeSniffer and it was actually easy to follow and work with it, due to the ...
  • Good docs - The codex has lots of good info. I Googled for stuff like "wordpress http get", "wordpress cache", and "wordpress i18n" and the codex docs always had what I needed.
  • Can leverage Verbatim for l10n - After I made a .pot file for the plugin, I added it to our existing MDN project on verbatim. Within hours it was translated into Dutch, Polish, and German. Then a couple days later Brazilian Portuguese and Spanish too. I love our localization teams so much.
  • Releasing is painful - It's exactly this painful. It makes me really love and appreciate our new chief deployment system on MDN, and heroku for my other sites.
  • Releasing is cool - It's cool that the plugin is now just a couple clicks away from millions of users. The appeal of "app stores" I guess.

WordPress development at Mozilla

I coordinated a "WordPress at Mozilla" talk for an OKC WordPress User's Group meetup. When I asked about WordPress on Yammer, only Craig and Jake claimed to have WordPress dev and deployment experience at and for Mozilla. They say we have many dozen - approaching a hundred? - WordPress blogs & sites at Mozilla. In addition to that, we have:

Mozilla and WordPress

WordPress runs about 55 million websites in the world. 332 million people view over 2.5 billion pages on WordPress.com's hosted sites alone, where there are also 500k new posts and 400k new comments every day.

Which makes me wonder - does Mozilla have any official or intentional relationship with WordPress? Should we?

WordPress empowers people to make and control their own content on the web. (As opposed to, say, Facebook Pages) It seems like we could combine efforts in some cool ways. At the very least, many of our projects and websites could probably put together a cool and useful WordPress plugin of some kind. It's really not bad at all. :)

Mozilla & WordPress / groovecoder by groovecoder is licensed under a Creative Commons Attribution-ShareAlike CC BY-SA

Firefox rapid releases: developers *are* users

Jono

There's a tempest brewing in the Interteapot over Jono's post about the Firefox rapid release cycle. I reacted the way he probably anticipated - "Good points that are already well taken." But tech media is sensational, so the story reported was "Firefox dev hates Firefox ZOMG!" prompting an official Mozilla Press Statement™ and a sincere face-palm from Jono.

Let me make something clear: Jono is one of my heroes. When he writes something, I read it. And when he writes how Silicon Valley culture has a monomaniacal obsession with hugeness, I read it so often that it's the first hit in my browser bar for 'le'. But I want to add another perspective to his main point - at least the main point he wanted to make.

The main point I wanted to make was about the distance between the developer perspective and the user perspective, the costs for users of updates (even good updates), and the reasons why developers (everywhere, not just Mozilla) may have trouble seeing updates from the user perspective.

Jono

Web developers

I'll emphasize that Jono means the Firefox developer perspective vs. the user perspective. Web developers are Firefox users. Working on MDN, acting as a developer evangelism rep, and running Tulsa Web Devs gives me some insight into the web developer perspective, so let me talk about them.

I've showed the new dev tools, HTML5, CSS, and JavaScript support to web developers and they are always surprised how much has been added to Firefox in the last year (i.e., the time they've been using Chrome.) Most of them make an opposite response to the one Jono describes - something like "Wow, I need to look into Firefox again." And I'm able to re-pitch, re-sell, and re-promote Firefox with "What's new in Firefox for developers" every 6 weeks rather than once a year!

In almost every one of these encounters, I also show web developers the Aurora release channel, and they love it. I tell them Aurora is Firefox, just 7-13 weeks in the future. (Because Mozilla has time machines) It gets new features like the awesome new responsive design view and javascript debugger even sooner, and it lets web developers see how their sites work in future versions of Firefox.

Here's the kicker: Aurora updates more frequently than Firefox does - and web developers love it! These are Firefox users. And importantly, they're usually "the people who shout the loudest about browsers."

So that's it. Just want to point out an important segment of Firefox users for which the new rapid release process is a big improvement. Jono knows this, but maybe some clueless tech journalist will pick this up and write a "ZOMG Mozilla web developer likes Firefox" article. Nah, not enough page-views.

UPDATE: Too perfect. Right after I published this, I got an update prompt from Aurora. ;)

Firefox rapid releases: developers *are* users / groovecoder by groovecoder is licensed under a Creative Commons Attribution-ShareAlike CC BY-SA

Mozilla in OKC

In the last couple weeks I've made two trips down highway 44 to give talks about Mozilla technology to web groups in Oklahoma City.

OKC.js June Meeting BannerFirst, I went to speak at the OKC.js June meeting about the various JavaScript API's and related technologies Mozilla is developing and promoting for the open web.

Jesse had told me the OKC.js group has started well and they were right. There were about 25 or 30 attendees. I covered a lot of material (see my presentations page) and then gave away some swag - an Aurora laptop cover-sticker, shirts, and pens - to anyone who answered a quiz question about the content. Everyone likes shirts! In addition to questions about Gaming, Mobile, Apps and Boot to Gecko, I also got lots of questions and interest about our Tulsa Web Devs activities.

The following week I recruited Craig and Jake to help me give a "WordPress at Mozilla" talk at the OKC WordPress June Meetup.

There were about a dozen attendees and we used vidyo to do a conference presentation on our blogging infrastructure and operations (Jake), our theming (Craig), and finally I showed our BrowserID WordPress plugin. We got some good questions an interest, particularly in new One Mozilla theme and its accessibility features. I left a bag of pens for the meetup group - I had given away all my other swag at OKC.js.

OKC has a good web community that is starting to connect and do more - much like Tulsa. We have a full-time Mozilla employee in OKC. I'll plan to collaborate more between OKC and Tulsa web communities. Maybe float ideas of an OK Mozilla group or something. I'm already planning to talk to students at Francis Tuttle Technology Center Web Design and Development program.

Mozilla in OKC / groovecoder by groovecoder is licensed under a Creative Commons Attribution-ShareAlike CC BY-SA

An open letter to all non-parents from a parent

Thank you for your letter. I laughed and nodded along as I read it, and I shared it with all the rest of my parent friends.

Thank you for babysitting! I understand those 3 hours seem like an eternity of suffering; the 3 hours of quiet you gave my wife and I were an eternity of bliss!

Thank you for understanding when we have to leave your party early to get our children home to bed.

Thank you for letting us decide what to do on the nights we have a babysitter!

Thank you for letting us take 3x as long to do everything.

Thank you for always coming to our house for dinner because it's child-proof.

Thank you for going out of your way to meet at a time and place that works around nap-time.

Thank you for talking to and playing with our kids when they are with us.

Thank you for holding our kid while we clean up the embarrassing mess they left at the restaurant.

Thank you for bringing them a new book for story-time.

Thank you for re-scheduling the work meeting because my kid is sick.

Thank you for taking over so many tasks for our social group.

Thank you for being the one to call me instead of waiting for me to call you.

And I'm sorry.

Sorry I don't answer your text messages.

Sorry I rarely ever go out anymore.

Sorry I forgot your birthday/graduation/other-special-occasion.

Sorry for being so up-tight about germs.

Sorry for having to stop our conversation abruptly to chase down my kid.

Sorry for being so chaotic.

Sorry for being jealous and envious of your frequent dinner dates, your vacations, your boredom, or that awesome open source project you built in your free time. (What's that?!)

But while I was writing this letter - which took a whole week, one or both of my daughters have:

Clover in the pool

River in a hat

said "Dada, I need a hug,"

asked to be held countless times,

giggled uncontrollably as I tickled her,

run up and down our hallway continuously for 10 minutes to tackle me,

been "Beast", "Belle," "Emily," "Nemo," "Bruce," or a dozen other characters,

hugged me with "legs and everything" when I asked,

squealed with delight as she rolled a bowling ball straight into a gutter,

learned to swim back to the edge of the pool by herself,

fallen asleep in my arms while I sing to her,

called out for me when thunder woke her up at night.

Thank you for sticking with me. I'm sorry our friendship has stretched so much, but I hope we'll have great times watching these two new little friends grow up with us.

An open letter to all non-parents from a parent / groovecoder by groovecoder is licensed under a Creative Commons Attribution-ShareAlike CC BY-SA

Please Learn to Eat the World

TL;DR Code is eating the world the same way writing ate the world. We don't all have to be expert writers - of language or code - but we should all be literate in both.

Jett Atwood's "Please Don't Learn to Code" post shocked me a bit, because I agree with almost everything else he posts. I agree with much of it, but the "everyone should learn programming" meme is not the straw man he criticizes, it's a young nebulous movement. E.g., the Mozilla Webmakers initiative is just a series of blog posts and some communication channels organized on a wiki page. So Jeff's input could and should be formative somewhere like the next Webmakers community call.

Writing ate the worldWriting Technology - art from Civilization 5, according to Sid Meier

My MDN colleague and technical, sci-fi, and beer menu adviser Les makes a good "Please Do Learn To Code" counter-argument. I want to elaborate on his analogy to writing:

Consider writing: there's a lot to learn and it used to be a thing done only by a few scribes. But, people today get a lot of mileage out of just sticky notes and email. Sure, improving your grammar and learning how to structure an essay can help in many, many ways. But, you don't need to be a professional writer to be a professional who uses written language.

Consider the state of the world at the time writing was invented/discovered. In Civilization 5 (which is my definitive guide to history), Writing can be preceded by Pottery, Sailing, Trapping, Archery, Horseback Riding, The Wheel, Masonry, and Metal Casting. In a world of subsistence-level agricultural society, writing was a luxury knowledge skill. Maybe there's an ancient "Writing Horror: archiving and human factors" scroll telling potters, sailors, and animal trappers "Please Don't Learn to Write" - suggesting that the general populace only needs to memorize the laws of the land and sign their own name to it.

In Civ 5 - Writing enables Philosophy, which combines with Trapping to enable Civil Service, and also combines with Calendar to enable Theology, which combines with Civil Service to enable Education. Education combines with Compass to enable Astronomy & Navigation, and with Chivalry to enable Acoustics, Banking, Economics. These disciplines combine together in Scientific Theory which enables the Industrial and Modern Eras of advancement - Electricity, Telegraph, Radio, Electronics, Mass Media, Computers, Robotics, Particle Physics, Nanotechnology.

Yes, this is a simplified and gamified perspective, but the truth is, while writing is only of ultimate importance "... in the right context, for some people." the incorporation of writing into other disciplines has been the foundation of the modern world. Reading and writing are the fundamental knowledge skills for every person in every modern occupation.

Code is eating the world, according to Mark AndreessenComputers - Civ 5 Art

Writing is a technology that allows someone to externalize thoughts into a medium that can be communicated to others who parse, interpret, and process those thoughts. Code is a technology that allows someone to externalize instructions into a medium that can be communicated to computers that parse, interpret, and process those instructions. We call that externalization of code, software.

Marc Andreessen always seems to know what's going down and what's coming up. And back in December he wrote a great WSJ essay on Why Software is Eating the World - a survey of industries all across society that are being consumed by software-driven activity and operations. Code combines with book-selling to enable cloud computing. Code combines with telecom operators to enable world-wide video chat (like we were promised would happen in the 23rd or 24th century). Code combines with aviators and aerospace to launch airstrikes without putting pilots at risk. Code is eating the world, just as writing did before it. These combinations seem obvious and intuitive to those of us who make software, but they are neither obvious nor intuitive to everyone else. Jeff is spot-on when he says everyone should know enough code to know "when code might be an appropriate way to approach a problem you have" but his implication underestimates how many problems can be approached with code - i.e., almost all the problems.

What does a code-literate world look like?

Jeff has a laundry list of other problems with the "everyone should learn to code" movement. My vision of a code-literate world is quite different:

  • There's less code. Coders undoubtedly realize that fully 90% of our time is spent reading code rather than writing it. When we do write code, we often refactor existing code. In a code-literate world, more people are aware of this, not fewer. So more people buying code understand that less is more.
  • There's more solutions than code. Even if code hasn't eaten the problem space already, more people are aware of the ability to re-use code, especially open-source code. More people understand how and when to apply code to problems.
  • There's new jobs in place of old ones. Jeff's right about entry-level programming jobs, though I dislike the trace of Silicon Valley hubris. Sure, "many people in the U.S. and around the world lack the education and skills required to participate in the great new companies coming out of the software revolution." But, "This is a tragedy since every company I work with is absolutely starved for talent. Qualified software engineers, managers, marketers and salespeople in Silicon Valley can rack up dozens of high-paying, high-upside job offers any time they want, while national unemployment and underemployment is sky high. This problem is even worse than it looks because many workers in existing industries will be stranded on the wrong side of software-based disruption and may never be able to work in their fields again. There's no way through this problem other than education, and we have a long way to go." -Andreessen

Jeff makes fun of the notion that NYC mayor Bloomberg learning to code will help him make public transit improvements. But Tulsa Web Devs are dealing with this right now as we write code for Tulsa Transit to put our local bus routes and schedules onto Google Maps. Even in the IT department, coding literacy seems low. They're "able to get around on the Internet" and they have "a basic understanding of how computers, and the Internet, work." But they buy code from Trapeze Group - they can't read it and they certainly can't write it. If the Tulsa Transit General Manager went thru Codecademy he could go to our github repository and read the code he sees. But because he doesn't know how to code, our code is as arcane to him as the box of software he buys from Trapeze. From my interactions with Code for America Brigade, I detect this scenario plays itself out in many places and in many sectors.

Code is eating the world. If people don't learn to code, they'll be eaten by it. Coding shouldn't be practiced by an elitist cabal of programmers selling software charms to illiterate masses. Our world is full of consumerism and starved for makerism already. We should encourage and teach others to code. Like writing, it creates opportunities, enables progress, and advances all of society.

Please Learn to Eat the World / groovecoder by groovecoder is licensed under a Creative Commons Attribution-ShareAlike CC BY-SA

Tulsa School of Dev

Tulsa School of DevThis year's Tulsa School of Dev had lots of changes from last year.

  1. New event "chairperson" - Sean Whitesell
  2. New event venue - TCC Northeast Campus
  3. New event website platform - WordPress with custom plugins
  4. New event focus - "hands-on" content

First, the rough edges

For one, we (i.e., Tulsa Web Devs) didn't polish up the website as much as we should have. It was clumsy to do speakers, talks, and technologies with custom post types. I'm still looking for a good open-source lanyrd/eventbrite-type cms - anyone know of one?

TCC Northeast wasn't a good venue - the campus has a weird layout; the common area wasn't suited for lunch and rooms were far away from registration and not conducive to a good hallway track.

Aside from the above issues, I liked the event.

I especially liked mingling with the developers. I had a chance to meet Lindsey, Cory, and Matt from The Div and I hope we do many more events together. I also met Jesse Harlin who did a mobile HTML5 geolocating note app for the 2nd half of the web track. Tulsa Web Devs got together to watch the ustream of the April meeting of OKC.js - the group Jesse and Vance Lucas are running in OKC. I also rubbed shoulders with developers from outside our web community bubble - i.e., mostly Enterprise and Microsoft developers. I still wish there was more interaction between the two "camps" though, along with the sizable Java group in town.

Microsoft was really cool - they gave away a free Windows Phone to attendees who built and published a Windows Phone app that day. I may have to ask if we can give phones away at Tulsa Tech Fest to HTML5 mobile web app developers - let them pick between a B2G phone or a Windows Phone. ;)

I'm looking forward to next year's School of Dev. My notes for improvement:

  1. Improve the format preparation (talks in the morning, workshops in the afternoon?)
  2. Book a better venue
  3. Promote earlier

Most importantly, we'll keep bringing Tulsa area developers together!

Tulsa School of Dev / groovecoder by groovecoder is licensed under a Creative Commons Attribution-ShareAlike CC BY-SA

Beer & Tech Community Events

Disclaimer: I like beer. I read about beer. I make my own beer. I even go to a Benedictine Abbey once a month to brew beer with monks.

Chris shared Ryan Funduk's post describing the tech community's enthusiasm for alcohol that implicitly, and sometimes explicitly, excludes non-drinkers. Ryan makes a keen insight that deserves wider consideration - that the alcohol "fun gamut" attracts brogrammers.

Obviously, "brogrammers" aren't the only ones in our community who enjoy alcohol. Ryan correctly points out that drinking is widespread, yet "brogrammers" are, thankfully, a small though obnoxious minority. So we can ask bigger questions - What is it about alcohol that we like? What does it do to us? Then finally, how should we incorporate it into community events?

What is it about CH3CH2OH that we like?

Science!Alcohol directly affects the prefrontal cortex responsible for judgement and inhibition by prolonging the opening of chloride ion channels which floods post-synaptic cells with chloride ions so the cells cannot as readily respond to stimuli. Alcohol also inhibits dopamine breakdown which extends our dopamine system's pleasure sensations. Alcohol acts as a sedative on our entire central nervous system.[1]

Our brains need some R&R -  All of this can be especially relaxing for people (like developers?) who are constantly exercising their central nervous system; the prefrontal cortex is particularly believed to work on complex cognitive behavior like solving abstract problems. No wonder we like to give it a rest!

Alcohol is an identity microscope

True SelfAs we relax our prefrontal cortex, we also lose inhibitions and judgement.

A couple years ago I discussed this from a Christian perspective with my theology professors (over a couple pints of beer, of course!). Drinking alcohol ranges from religiously required (as in my Catholic tradition!) to socially taboo (in some mainline Evangelical traditions) to religiously forbidden (in Mormon and some fundamentalist traditions) among Christian worldviews. So, we covered lots of angles. I left with an opinion that as alcohol lowers our inhibitions, we can somewhat discover how much of our faith is just inhibitory religious codes, and how much we are actually allowing our "true selves" (as Thomas Merton calls it) to be transformed to the life of Jesus.

It's not just a religious thing. We all know "sloppy drunks", "mean drunks", "emotional drunks", "tired drunks", etc. But alcohol doesn't make us mean or angry or sexist or emotional - alcohol removes other inhibitions we pile on top of those parts of ourselves. So here's the point - if I make a sexist comment while intoxicated, I'm sexist. (For whatever definition of 'sexist' we use.) If I'm sexist, that's something I need to change, regardless of alcohol consumption.

We need to improve as a community in lots of ways, with or without alcohol.

Can we put alcohol on the same level as caffeine?

Since I'm only making my rough observations and opinions, I don't have any specific suggestions for how we should handle alcohol at tech community events. Ryan makes some good ones in his post, there's a decent little discussion going on in Mozilla's engagement-developers list, and Rob gives some good general advice.

I very much agree with Ryan and Rob. I'd like to see alcohol as one entertainment among many at technology events. It can be an aspect of any event, but shouldn't ever be the main aspect of any event. I personally will always go check out the craft and local beers available at any event. (I make a habit to try to visit a brewery and a cathedral anytime I travel.)

But what I really want at these events, and what happens the vast majority of the time, even the "party" events, is to mingle with others who are passionate about technology - no matter what drink they're holding.

Beer & Tech Community Events / groovecoder by groovecoder is licensed under a Creative Commons Attribution-ShareAlike CC BY-SA

Tulsa Web Devs press tour

This Land PressOr 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!

Tulsa Web Devs press tour / groovecoder by groovecoder is licensed under a Creative Commons Attribution-ShareAlike CC BY-SA

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.5 / groovecoder by groovecoder is licensed under a Creative Commons Attribution-ShareAlike CC BY-SA

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

MDN 2.4.5 sprint backlog.

  • 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.

MDN 2.4 / groovecoder by groovecoder is licensed under a Creative Commons Attribution-ShareAlike CC BY-SA
Mozilla & WordPress / groovecoder by groovecoder is licensed under a Creative Commons Attribution-ShareAlike CC BY-SA