If you’ve been following Ubiquity, you know we haven’t made a new release of the extension since last summer. What’s going on?
Last October, Mozilla Labs got together and had a meeting about all the things we want to get done in 2010. It became clear that there were too many things on our plate, and we had to make some hard decisions. Ubiquity was one of the things that was put onto the back burner in order to focus better on Weave, Jetpack, Bespin, and other core projects.
Everybody I’ve talked to at Mozilla loves Ubiquity and would love to see it developed further — but all have agreed that the other projects are higher priority. Ubiquity remains an exciting experiment and I personally look forward to the time when I can work on it again. But for now I’m focused full time on Test Pilot.
Does this mean Ubiquity is dead? Not at all! It’s an open source project with a fairly large installed user base, and if you look at the Mercurial repository and the mailing list you can see that the community is still active fixing bugs and answering user’s questions. It’s clear that the Ubiquity community has taken on a life of its own and is capable of further development with or without direct involvement from Mozilla Corporation employees.
We’ll probably be releasing a new version of Ubiquity sometime soon, just for the sake of maintenance. The last released version isn’t compatible with Firefox 3.6, and the lack of compatibility is harming the many people who still use Ubiquity on a daily basis. Making it compatible should not be very difficult, since the “trunk” (the latest development code) is compatible with 3.6 to the best of my knowledge. So we just need to roll up a new release and get it out to people. We should be able to get that out this week or next week.
We’re also working on analyzing the first round of Ubiquity experimentation, so that we can figure out what to approach differently when we begin the second round. Yes, I’m pretty sure there will be a second round.) I’ve been writing up my thoughts on what we learned during the first round. It’s turned into quite a long essay. Not exactly a “post-mortem”, as that would imply the project is dead; call it a “retrospective”. Look for it within the next couple of days.
January 20, 2010 at 10:07 pm
Thanks for the update! I miss it in Firefox 3.6, and it’ll be nice to have it back.
January 20, 2010 at 10:31 pm
Showing some love. I only really use ‘search’, but it’s worth it for that alone!
January 20, 2010 at 11:46 pm
thank you for the update and the effort you put in Ubiquity, I really hope some people will take the chance to improve it even more
January 21, 2010 at 1:02 am
I personally would have only prioritized Weave above Ubiquity. That’s probably because I’m not really a web developer, but I think the user experience should take priority over the developer experience regardless. Ubiquity seems more of a revolutionary new way to use the browser while things like Jetpack and Bespin seem more evolutionary. I’m not familiar with Test Pilot, so I’ll refrain from talking about that.
I will put off updating to 3.6 until compatibility is added at least.
January 21, 2010 at 1:53 am
It sucks that Ubiqity, the one I love got low priority
January 21, 2010 at 5:53 am
I can understand the underlying decision, but I always thought, that the focus of ubiquity was just wrong.
That sucker needs to replace both the search, and the address bar. When you ask?
At latest in 4.0!
Of new UI you speak, of new UI because of it’s necessary I speak.
One bar, twenty-thousand possibilities.
Like the Bar in Chrome, only better.
January 21, 2010 at 5:21 pm
First of all, hats off to you and the team for creating a great tool. Thanks on committing to a 3.6 compatible release. Finally I hope I’ll to be able to roll up my sleeves and start chipping in on the project.
January 21, 2010 at 8:53 pm
I think I’m going to downgrade back to Firefox 3.5 until Ubiquity is compatible with 3.6.
January 22, 2010 at 1:14 am
It’s a shame… I uninstalled Weave a month after it was released, didn’t really have any use for it (even though I use multiple computers), but Ubiquity was by far the best add-on out there…
It improved my productivity a lot (needed an image? in a second, a map? that too). Certainly its a shame you took that choice.
January 22, 2010 at 1:49 pm
If you want to use Ubiquity in 3.6, download 0.5.4.xpi, open it with 7-zip, edit install.rdf by changing 3.6apre to 3.6, save it back to the xpi and install the extension from your PC, eg by dragging the xpi to the add-ons menu.
January 23, 2010 at 3:58 am
Adding support for the continuation and growth of this project. It’s been my absolute favourite thing in Firefox since I found it, and I’ve recommended it to everyone I can. It’s positively received by even non-technical people.
January 24, 2010 at 2:29 am
Looking forward for the future of ubiquity.
January 25, 2010 at 7:28 pm
That’s really sad. Ubiquity is a great experiment with a lot of potential.
January 26, 2010 at 11:17 am
So sorry to hear that. Ubiquity has been a life saver to me. If you ever move to a new country with a new language it’s impossible to live without.
That may not be that important in the US, but elsewhere you can’t believe how useful a feature that is for FF to have.
Really hope the 3.6 release comes out at least so that we can use it as-is.
January 26, 2010 at 3:16 pm
Yeah, I wish too that Ubiquity will get some more developer efforts SOON!
I love the idea, and would love to see a fully integrated version that can call any function you want in Firefox and it’s addons, using either natural language or a specific syntax of your choice.
And with flashy GUI too, with themes and all sorts of things.
January 26, 2010 at 3:59 pm
Continuing the common theme… I love Ubiquity!
It’s great that you will add support for 3.6. A real relief!
2cents: No other browser development since the introduction of tabbed browsing has the potential to revolutionize the browsing experience.
I truly believe that If Mozilla wishes to stay at the front of Browser development (And steal more of the market) Ubiquity is a vehicle to get there.
If users love the browser, The Dev’s will come.
I know speed is important but I just don’t see a user getting fired to switch browser because their page loaded 300ms faster…
January 26, 2010 at 4:07 pm
Ubiquity as for me, is the most waiting and main project which im waiting for long time… This is the best project of mozilla labs. im administrator and i love command_all…
January 26, 2010 at 4:24 pm
If you want to use Ubiquity in 3.6
Install the ‘Add-on Compatibility Reporter’ add-on https://addons.mozilla.org/en-US/firefox/addon/15003 which enables add-ons marked as incompatible. So far so good, the commands I use (translate, weather and a few others) seem to work ok.
January 30, 2010 at 12:17 pm
i think ubiquity is a bigger innovation than weave [i use both from 0.2 version]…
February 1, 2010 at 9:18 am
Ubiquity is the one extension I use the most. Would love to see its continued development.
February 4, 2010 at 9:33 pm
I can see why from a developers point of view projects such as Bespin & Jetpack should have a higher priority. However, from an end-users perspective I would really appreciate further development of Ubiquity at some point in the not too distant future. Still, a version that works with Firefox 3.6 will be great for the time being.
February 18, 2010 at 7:56 pm
>So we just need to roll up a new release
>and get it out to people. We should be able
>to get that out this week or next week.
So… er… yeah. Where is it?
February 18, 2010 at 8:08 pm
[...] Posted by jonoscript under Uncategorized | Tags: firefox, ubiquity | Leave a Comment In this post I promised a new release of Ubiquity to be compatible with Firefox 3.6. It’s been a while so [...]
February 18, 2010 at 8:09 pm
Hi Banana Chips. Please see this post: http://jonoscript.wordpress.com/2010/02/18/quick-update-on-ubiquity-and-firefox-3-6/
February 20, 2010 at 12:46 pm
[...] keeping me on Firefox all this while was the Ubiquity add on, and though it still works, Mozilla has decided to put a hold on Ubiquity’s [...]
February 20, 2010 at 3:08 pm
[...] now, it’s basically dead. It’s such a quiet death, that they won’t even say it’s “dead”. [...]
February 20, 2010 at 3:33 pm
[...] now, it’s basically dead. It’s such a quiet death, that they won’t even say it’s “dead”. [...]
February 22, 2010 at 2:11 am
[...] now, it’s basically dead. It’s such a quiet death, that they won’t even say it’s “dead”. [...]
February 22, 2010 at 3:47 pm
[...] now, it’s basically dead. It’s such a quiet death, that they won’t even say it’s “dead”. [...]
March 16, 2010 at 9:12 pm
[...] now, it’s basically dead. It’s such a quiet death, that they won’t even say it’s “dead”. [...]
April 14, 2010 at 6:28 pm
“Making it compatible should not be very difficult, since the “trunk” (the latest development code) is compatible with 3.6 to the best of my knowledge. So we just need to roll up a new release and get it out to people. We should be able to get that out this week or next week.”
DUDE! It HAS BEEN 4 MONTHS, and still nothing. We are Very disappointed of your lack of focus.
April 20, 2010 at 12:23 am
metaholic: DUDE! Did you miss my follow-up post here? http://jonoscript.wordpress.com/2010/02/18/quick-update-on-ubiquity-and-firefox-3-6/
It turns out I was wrong about the trunk being compatible with 3.6. Read that post for possible workarounds.
And, I have plenty of focus: I’m focused 100% on Test Pilot. https://testpilot.mozillalabs.com/
April 20, 2010 at 11:39 am
metaholic: https://wiki.mozilla.org/Labs/Ubiquity#For_Firefox_3.6
The beta version’s based off the 0.5 code.
May 9, 2010 at 9:34 pm
[...] Chyba wszyscy użytkownicy Ubiquity zauważyli, że od lipca 2009 roku rozszerzenie praktycznie stoi w miejscu (20 stycznia dodano obsługę Firefoksa 3.6 w wersji 0.1.9.1, ale już nie 0.5.4). Co się dzieje z Ubiquity? Na początku roku rąbka tajemnicy na swoim blogu uchylił Jono Xia – What’s up with Ubiquity? [...]