Status: Jetpack and Content Scripts in Firefox

As Mike Beltzner recently explained, the Firefox team is working on better communicating what we’re working on. We’ve been focusing on more of a Sprint-based model of development, and I’m quite enjoying it. Of course, it’s not a huge change for me, due to the way my previous project was organized. I should note that some of these “sprints” will take significantly longer than a week or two – so I like to think of them as “projects”.

Since its been quite awhile since my last status update (a month!), I’ll cover what I’ve been working on since then. If I take more than a week or two to post again, feel free to yell at me on IRC :)

Taskfox

Status

  • Implemented detection of certain page URLs, and display them as tasks
  • No other exciting developments, working on getting the code review-ready
  • Canceled the weekly meeting

Loose ends

  • Who’s the lucky person that gets to review this? It’s rather big…

Next steps

  • Finish getting review-ready
  • Start getting reviews and iterate

Jetpack uplift exploration

Status

  • Goal: Explore possibilities and requirements for uplift of Jetpack
  • Timezones + scheduling meetings = suck
  • Phone meeting between us (Johnath, Mossop, and I) and Atul (The Jetpack Guy)
  • Plenty of notes up on the wiki
  • Spawned off Content Scripts sprint as a first step in achieving end goal (provide open-web tech to extend the browser)

Loose ends

  • Wanting bug numbers for stuff that Jetpack needs fixed in Firefox/Platform

Next steps

  • Finish Content Scripts sprint
  • More meetings with the Jetpack team

Content Scripts

Status

  • Goal: Provide native support for Content Scripts
  • General requirements gathered
  • Basic functionality completed

Loose ends

  • Install/management is dependent on the Extension Manager UI and API

Next steps

  • Implement custom protocol as a binary component
  • Implement persistence of installed scripts
  • Spec requirements for what API to provide to scripts
  • Potentially implement GreaseMonkey compatibility APIs

3 thoughts on “Status: Jetpack and Content Scripts in Firefox

  1. Please try to get l10n reviews as early as feasible? There’s a good deal of architecture, but I also expect a flock of style-guide-style comments on how to do comments, etc.

  2. Axel: For Taskfox? That’s one of the things I need to work on. Working with l10n is a top priority. I should note that I’m not specifically aiming to land this for 3.6 (although that would be a nice outcome!).

  3. Pingback: My status updates – what can I improve? « Blair’s Brain

Comments are closed.