Open Thinkering

Menu

Tag: Mozilla

Weeknote 03/2014

This week I’ve been:

  • Confirming with the Mozilla Web Literacy community that we’re moving to calling what we’ve created a ‘Map’ instead of a ‘Standard. More here.
  • Meeting for an inaugural (virtual) huddle with my new Mozilla #teachtheweb sub-team mates Michelle Thorne, Laura Hilliger, Kat Braybrooke and William Duyck (aka ‘FuzzyFox’)
  • Sorting out my travel/accommodation for BETT (I’m speaking three times there next Friday!)
  • Hosting the Web Literacy community call. You can listen to the recording here.
  • Proposing and writing about merging the Mozilla Web Literacy call with the Webmaker Mentor call.
  • Sorting out my expenses from the recent CE21 meeting in Orlando. It was a surprisingly involved process.
  • Talking to various people about Mozilla process-related stuff.
  • Meeting with Laura Hilliger to discuss Mozilla’s presence at the Oppi Festival in Helsinki (11th/12th April – I’m not going)
  • Planning out my slides for my BETT presentations.
  • Meeting with colleagues to discuss a refocus of an upcoming Webmaker whitepaper.
  • Taking PTO (i.e. a day off) on Friday as I had too much non-Mozilla stuff to do! I took my (nearly) seven year-old son to Kielder Observatory for part of his birthday present.

Next week I’ll be with my wife in Gozo on Monday and Tuesday trying to find somewhere for us to move to for six months. I’ll also be celebrating my son’s birthday and then travelling down for BETT on Thursday and Friday.

Image CC BY-NC-SA Murray Head

The Web Literacy Standard is dead (long live the Web Literacy Map!)

I spent a good chunk of 2013 working with colleagues and a community of stakeholders creating a Web Literacy Standard. The result is testament to the way Mozilla, as a global non-profit, can innovate on behalf of users. I’m delighted with what we created.

Until recently, the literature and language in the field of Web Literacy has been relatively undeveloped. This is important, because although it doesn’t always seem like it, words are hard:

This seems to be a problem for anyone trying to explain the unfamiliar. If you invent new words, few people will know what you’re talking about, but if you make analogies using existing words, you bring along all their context, whether you want to or not.

In early 2013 we wanted to avoid creating just another ‘framework’. Why? Although we wanted to be more descriptive than prescriptive, we still didn’t want people to just pick-and-choose the bits they liked. Instead, we wanted to co-create something more holistic. That’s we chose to call what we were creating a ‘Standard’. The idea was for the community to come together to build something they felt they could align with.

And that’s exactly what we did. We created something that, while not perfect, we can feel a justifiable pride about.

A problem we’ve encountered is that because words are hard and dependent upon context, ‘Standard’ can have negative connotations – especially in North America. So after announcing the first version of the Standard at MozFest we, as a community, started to have a discussion as to whether ‘Standard’ was a word we wanted to keep.

The result of that consultation is that we’ve decided to move away from ‘Standard’ to describe what we’re doing here. While we could fight a valiant crusade on behalf of the term, it doesn’t seem like a battle that’s worth our time and effort. It’s better to focus on winning the war. In this case, that’s ensuring the newly re-titled Web Literacy Map underpins the work we do around Mozilla Webmaker. After all, we want 2014 to be the year we move beyond the ‘learn to code’ movement and focus on a more holistic understanding of web literacy.

We decided on Web Literacy ‘Map’ because we found that most of the language we used to describe what we’re doing was cartographic in nature. Also, it means that our designers have a lot more scope around visual metaphors! It’s going to be (and, importantly, look) – amazing!

The web is the platform (or, the perils of esoteric setups)

At Mozilla we say that “the web is the platform”. It’s almost like a mantra. By that we mean that, as the world’s largest public resource, the web is big enough, fast enough, and open enough for everyone to use on a full-time basis.

To prove this, we made FirefoxOS, a mobile operating system comprised entirely of web-native technologies. But FirefoxOS devices aren’t the only ones that lean heavily on the web for their functionality. Google Chromebooks have a stripped-down version of Linux that boots directly into Google’s Chrome web browser.

The meme over the last few years seems to have been that Chromebooks (and by extension, I guess, FirefoxOS devices) are for other people – you know, the type that “just do a little bit of web browsing here and there.” They’re not for us power users.

Here, for example, is Andrew Cunningham from Ars Technica talking about covering CES 2014 on a Chromebook:

Even if you can do everything you need to be able to do on a Chromebook, switching from any operating system to any other operating system is going to cause some friction. I use OS X to get most of my work done because it’s got a bunch of built-in features and applications that I like. I use Full Screen Mode to keep my laptop’s display organized and uncluttered. I like Limechat because it’s got a bunch of preferences and settings that lets me change the way it looks and works. I like Messages because it lets me connect to our XMPP server and Google Talk and iMessage, all within one client.

That’s what bothers me the most about Chrome OS. It’s not that you can’t do a lot with a Chromebook. It’s not even about getting used to different tools. It’s just that the operating system works so differently from established desktop operating systems that you’ll have to alter many of your normal workflows. No one’s saying it’s impossible to do, but for people used to something else it can be a laborious process.

Don’t get me wrong: there’s nothing wrong with native apps. I really like Scrivener, Notational Velocity, and others. But unless you’ve got unusual requirements I reckon that in 2014 you should have a workflow that can use the web as the platform. In other words, being away from your own machine and ‘perfect setup’ shouldn’t dent your productivity too much.

One blocker to all this, of course, is other people. For example, it’s very difficult to move away from using Skype (which doesn’t have a web client) because it’s the de facto standard for business VoIP communication. That is only likely to change when there’s a critical mass of people familiar enough with different technologies to be able to switch to them quickly and easily. Hopefully WebRTC will expedite this process!

So, in conclusion, if you’ve got a workflow that depends upon a particular native app, perhaps it’s time to look for an alternative?* Then, at the minimum you’ve got that alternative up your sleeve in a pinch, and at best you may find you want to switch to it full time.**

 Image CC BY Robert S. Donovan

*For example, I’ve recently moved from Evernote to Simplenote and from Adium to IRCcloud.

**If you want to simultaneously focus on privacy/security, look at the newly-revamped PRISM Break site.

css.php