Category Archives: mozilla

Changing my (blog) name, plus Plus

For those following this blog, note that I’ve changed the canonical site name from to Any links and feed URLs referencing the previous domain name will still work for the foreseeable future, but if and when you have time you may want to update your bookmark list, RSS newsreaders, and related information to reflect the new name.

A little history by way of background: I was around when the Internet was first being commercialized, and I had the opportunity to register for myself if I really wanted to. However I passed because I didn’t have a server to associate with it and I thought I needed to be running an actual server in order to register the name (though I’m not sure that was the case even then). When I finally got around to having a personal server in the late 1990s I found that had already been taken by a company that registered thousands of surname domains so that they could offer a shared domain service in which multiple people could have their own personal subdomains under a top-level domain:,, and so on. So I settled on the next best thing and registered instead for use as my primary domain, at the same time registering (as well as the .org and .net variants) to prevent anyone else from getting it.

When I first started a blog I hosted it at using custom blogging software. I later got tired of the management hassles involved, and moved my blog to, using the subdomain because I was still hosting other things at and couldn’t afford to dedicate the entire domain just to my blog. Since then though the blog has assumed more importance as my public face to the world, and I regretted having a somewhat unusual domain name for it. I’ve therefore decided to adopt the conventional approach and use as my primary blog name. (As noted above the old name of will continue to work, thanks to the magic of HTTP redirects.)

Note that my primary personal email address remains; I have no plans to change that. However I can also receive email at, so for example sending email to will get to the same inbox as I may switch over completely to for all uses in future, but in the meantime there’s no need to update your address book.

In other news, I’m now on Google Plus so you can add me to one of your circles if you’d like. I’ve been meaning to try Google Plus out before now, but I use Google Apps for my email and related services, and Google Plus wasn’t added to Google Apps until this week. I’ll publish notices of new blog posts to Google Plus, and maybe some other stuff from time to time.

Leaving Mozilla

Just a quick note to let all of you know that I’ll soon be leaving the Mozilla Foundation to take a new position as a sales engineer in the Federal sales group at IronKey. My last day at the Foundation will be Friday, December 11. Those of you with whom I worked pre-Mozilla know that this is a return to what I’ve done for most of my career (and I’ll be working with folks I’ve enjoyed working with previously). It’s been fun and interesting to work at Mozilla, but it’s time to move on.

I’m spending my last few days at the Foundation working on transitioning my various duties to others and helping out with planning for 2010. If there’s anything you need from me before I leave, please contact me in the next few days. After December 11 you can reach me at; my work address will be if you want to contact me on IronKey-related matters.

I appreciate all the help and support I’ve gotten from other folks at Mozilla. I’m sorry I won’t be able to thank all of you personally, and I won’t be at the Mozilla all-hands meeting next week so I won’t be able to say good-bye in person. I wish you all the best of luck in your endeavors, and look forward to seeing all the great things coming from Mozilla over the next year, from new releases of Firefox and Thunderbird to the start of Mozilla Drumbeat.

Mozilla Education: Looking back and ahead

I’m currently working on putting together a draft plan for Mozilla Education activities in 2010. I’m a bit blocked on coming up with a coherent plan, so I thought I’d try to unblock myself by blogging my thoughts on the subject. These are informed by the recent feedback on Mozilla Education I solicited from several Mozilla folks, as well as the Mozilla Education 2009 report I wrote earlier. Note that I’m thinking out loud here, so this will be somewhat long and rambling.

Based on the feedback, the first point to address is: What is Mozilla Education, and what are its goals? The people I asked were familiar with what Dave Humphrey has been doing at Seneca College in terms of introducing students to Mozilla, but weren’t clear on what was going on beyond that. So, some explanation: “Mozilla Education” as a program started out as an effort by the Mozilla Foundation to take what was going on at Seneca and try to replicate it at other schools, on the assumption that the Seneca approach was worth replicating. (There seems to be general agreement on this, though as discussed below there are some limitations to this approach.)

The primary goal of Mozilla Education now and going forward is to help grow a new generation of Mozilla contributors by working with students and educators around the world. In the original Mozilla Education planning document we outlined another broader goal around promoting general innovation in education (“help to drive a new wave of participatory, student-led learning in fields like computer science, design and business”). As discussed in the progress report, we’ve since deemphasized that second goal and are now focusing Mozilla Education efforts primarily on the Mozilla project proper.

In the context of this discussion the term contributorcovers anyone who makes a significant positive impact on Mozilla worthy of recognition; this includes both technical and non-technical contributions, anything from doing heavy-duty Gecko hacking to helping out with marketing Firefox. Thus there are multiple types of students and educators who might participate in Mozilla Education, and multiple types of activities directed toward them. To provide a bit more focus, let’s follow the advice of one of the people who provided feedback and discuss 1) what has worked (and not worked) in the past and 2) how we might take what’s worked and establish scalable processes for the future.

The first thing to note is that the Seneca approach–integrating teaching of Mozilla technologies and practices directly into college and university courses–is proving to be somewhat replicable, with several schools and professors now teaching or planning to teach such courses. (See the progress report for a full list.) However the pure Seneca-style approach has some limitations, at least from the point of view of producing core Mozilla contributors: It has been successful in producing good contributors in such areas as build infrastructure and release engineering, but less so in terms of producing contributors who are hard-core Mozilla hackers.

In my opinion this is not so much a failing of the approach as it is a failing of academia: The schools that have been most open to integrating open source development work into the classroom (like Seneca) are the schools that focus more on practical instruction for job-seeking students. The high-end research universities that attract top-quality computer science students are the ones least interested in anything that smacks of vocational education.

Until and unless this situation changes, I suspect that the most realistic approach to growing full-time core Mozilla contributors (i.e., people who are good candidates for employment at the Mozilla Corporation or Mozilla Messaging) is as follows:

  • Continue to promote the Seneca approach to schools that are most likely to be receptive to it, and in particular try to target schools interested in teaching topics like quality assurance through automated testing, continuous integration, and other software engineering practices needed in large-scale projects like Mozilla.
  • For research-focused institutions, pursue a more lightweight approach of encouraging professors to have students do Mozilla-related senior projects and independent study, either based on self-generated ideas or based on tasks previously identified as being good student projects. Note this is lightweight only in the sense that it demands less of the school and its faculty; in practice this approach will be limited by the amount of effort existing Mozilla contributors can devote to helping students.
  • For recruitment of hard-core hackers continue to rely on recruiting students from top schools as Mozilla Corporation or Mozilla Messaging interns, outside the context of the Mozilla Education program proper. In this context it’s easier to justify the amount of time needed to bring such students up to speed.

Moving beyond the issue of growing new core contributors, a second topic is that of encouraging students to make technical contributions outside the context of the core Mozilla code. This could include working on Firefox or Thunderbird add-ons, developing web applications that make use of new Firefox features, working with the various technologies being prototyped by Mozilla Labs, and so on.

In the context of Mozilla Education the Processing for the Web project (based on processing.js) is the primary project of this type thus far, and is proving to be quite successful. Projects like this are somewhat peripheral to the core Mozilla activities around shipping new releases of Firefox, Thunderbird, etc. However they do get more people involved in working with Mozilla technologies and code, help to promote adoption of Mozilla products, and help support other Mozilla activities, whether technical or not. (For example, the Processing for the Web work could be used in the context of the “visualize the (open) web” project proposed as part of Mozilla Drumbeat.)

In my opinion doing projects like Processing for the Web is a useful and scalable approach for two reasons. First, it provides a common focus for lots of student work, so that the limited time of mentors can be leveraged across more people: A mentor can help many students at once, and students can help one another. Second, it leverages the time and expertise of people outside the project (in this case people like Al MacDonald who were already working on processing.js), further lessening the burden placed on core Mozilla contributors.

Are there other possible projects like Processing for the Web that could serve as a focus for student contributions? One possibility is a project around Dehydra, Pork, and similar code analysis and rewriting tools designed for large code bases like Mozilla’s. Like the Processing for the Web project, such a project could leverage an existing community of people outside of Mozilla, including developers working in the GCC project and others developing or working with advanced code analysis tools.

Another way to engage students is the design challenge approach pioneered by Mozilla Labs and then adopted in a Mozilla Education context for the Jetpack for Learning Design Challenge. Design challenges and similar contest-like events have proved successful at attracting student participants, including design students and others who are not programmers at heart. Keys to success include have a fairly tightly focused challenge, along with one or more expert mentors who can help the students realize their ideas.

Because they’re focused on leading-edge work not yet ready for incorporation into standard shipping products, the Mozilla Labs folks have some freedom and time available for running design challenges that other Mozilla core contributors don’t necessarily have. In the context of Mozilla Education running a design challenge would typically finding third party subject matter experts to help with the challenge, which in turns means that challenges would typically require additional funding over and beyond what the Mozilla Foundation spends on the basic Mozilla Education program.

With that in mind, here are my thoughts on how Mozilla Education should approach engaging students to contribute outside the context of the core Mozilla codebase:

  • Sponsor at least three projects in 2010 that can each serve as a focus for engaging larger groups of students:
    • continuation of the Processing for the Web project
    • a new project around tools for analyzing and/or rewriting code, leveraging existing work by Taras Glek and others and done in loose cooperation with the GCC project or others
    • at least one other new project in an area yet to be determined.
  • Start at least one new Mozilla Education design challenge project in 2010, if (and only if) there is a suitable problem (e.g., one that doesn’t overlap with planned Mozilla Labs challenges) and funding can be found.
  • coordinate with Mozilla Labs to cross-promote Labs design challenges to the students involved in Mozilla Education activities, and vice versa.

Thus far I’ve primarily discussed engaging with CS students and others in related IT-centric programs. What about students in other areas, such as design or marketing? My feeling is that in 2010 at least Mozilla Education won’t play a major role in terms of growing core contributors in those areas, primarily because they’re outside the expertise of the main people working on Mozilla Education activities.

However that doesn’t mean that those areas have to be (or can be) ignored from a Mozilla Education point of view. One of the things we discussed in 2009 was the role of the proposed web site (currently instantiated as a set of pages on We’ve pulled back on some of the more expansive ideas for what that site might become. However I do think it makes sense to use it as a central point from which students can find information on Mozilla activities of potential interest to them. That leads to my final Mozilla Education proposed activity for 2010:

  • Establish and actively maintain a single high-profile page (e.g., that can serve as a portal to information about Mozilla activities of potential interest to students, including not only Mozilla Education material but also links to Mozilla Labs design challenges, student internship opportunities, etc.

Those are all my thoughts for now. If you have comments or questions about the above, please let me know. I’ll next boil this down into an actual plan.

One final day for Jetpack for Learning submissions

We received a lot of submissions for the Jetpack for Learning Design Challenge just prior to last night’s deadline. In order to accomodate last-minute entries, we’ve decided to further extend the deadline through midnight (US Pacific time) tonight, Tuesday, December 1. There will be no further extensions.

We’ve received a lot of good submissions thus far, and the Jetpack for Learning team is hard at work preparing for the next phase of the challenge.

Jetpack for Learning deadline extended

Do you have a great idea for a Jetpack or Firefox extension to help support learning online? Would you like a chance to attend an intensive Jetpack design camp in Austin TX and stay over to attend SXSW Interactive? Then you have less than a week left to send in your submission for the Jetpack for Learning Design Challenge.

To give you a little more time to prepare your submission, we’re extending the deadline for submissions to midnight (Pacific time) on Monday, November 30. If you’re in the US please relax and enjoy your Thanksgiving dinner before you send in your submission, and no matter where you live feel free to take time this weekend to polish it.

Explore the skies in the Jetpack for Learning Design Challenge

It’s now less than three weeks until the November 27 submissions deadline for the Jetpack for Learning Design Challenge. To get folks excited about the challenge Richard Milewski has taken Sean Martell’s great Jetpack design and put together this awesome promotional video that takes the Jetpack for Learning concept into the third dimension of Second Life. Thanks, Richard!

Announcing the Jetpack for Learning Design Challenge

We invite you to help turn the open Web into a rich learning environment and explore new possibilities for using Firefox add-ons to support learning online, by participating in the Jetpack for Learning Design Challenge sponsored by the Mozilla Foundation with support from the John D. and Catherine T. MacArthur Foundation as part of its digital media and learning initiative.

We’re looking for designers, educators and software developers who want to turn their innovative ideas about learning online into working prototypes in the form of Firefox add-ons. We’ll help you refine your designs and teach you how to create Firefox add-ons using Jetpack and other Mozilla technologies. Participants creating the best prototpes
will be invited to the Jetpack for Learning Design Camp and the SXSW Interactive conference in March 2010.

How does it work?

Come up with an innovative idea for a Firefox add-on that brings personal learning features to the open Web. Create a mock-up and submit it on the Jetpack for Learning Design Challenge web-site before midnight (US Pacific Time) on 27 November 2009. Based on the quality of submissions, up to 60 participants will be invited into a 6-week
online course that covers design/UX and technical aspects of add-on development and will help you turn your mock-up into a working prototype. We’ll select the most promising prototypes and invite up to ten of their creators to further refine their add-ons at a
face-to-face Jetpack for Learning Design Camp in March 2010 and to attend SXSW Interactive immediately following the Design Camp.

What kind of ideas are we looking for?

We’re looking for your ideas how Firefox add-ons, preferably add-ons created with Mozilla’s Jetpack technology, can turn the web browser into a platform for rich personal learning on the open web. You are not restricted to work on any particular type of application. Here are a few examples to get you started …

  • Turn social bookmarking and page annotation into effective learning
    tools (for example by including peer-assessment features)
  • Allow users to easily compile personal e-portfolios (for example, by
    combining their own works—photos, comments, articles—with
    testimonials others have written about them)
  • Let the browser suggest relevant materials for learning (for
    example, by automatically identifying additional articles based on
    what sites a person visits or which topics they search for)
  • Support social learning communities (for example, by making it easy
    to find and connect with others who share similar learning interests)

Who should apply?

Participation is open to individuals and teams, but we especially encourage submissions from inter-disciplinary groups (designers, educators, and software developers). You don’t need to be a computer geek, but participants are expected to implement their ideas as
Firefox add-ons, which will require writing some software code.

You must be at least 18 years old in order to participate in the Jetpack for Learning Design Challenge. You must also make your submission and your add-ons available for public use under open licenses. See the Jetpack for Learning web site for more information and complete rules.