The man behind the site.
I just got back from Harry Potter, and I have to say that I’m greatly disappointed. One might even say that I am even upset about it. I feel that the movie didn’t do the plot justice. It was really lacking details, and compared to the book, was rather boring. I could go on ranting about it, but I think I’ll leave it at this – the movie wasn’t worth it. If you haven’t seen it, I suggest you save your money.
Clearly Disappointed,
Shawn
There are some fascinating discussions going on in the newsgroups about the DOM Inspector and events. The basic summary is that there is a demand to view events on a particular node in the DOMi. The more discussion on this issue, the better, so please participate if you have anything to say about this.
I uploaded the newest version of the add-on earlier today to AMO, so once it gets approved, you’ll get a nice update. The following issues were fixed in this release:
Today I just committed a patch to trunk that properly selects the message when you click on a notification in Thunderbird. I’m not going to release that just yet as I want to play with it myself a bit.
I just landed a lovely patch from Lev Serebryakov that does several awesome things for mozStorage (Bug 333848):
I want to thank Lev for putting up with massive delays on getting reviews for his code, and adding xpcshell unit tests along with the C++ test. The thing I really like about having xpcshell unit tests is that it shows you how to use the API with JavaScript (I won’t get into how testing also helps you design a better API…). If you want to see how to the new stuff works, check out the test files.
My last post keeps getting comments, and I’m seeing this brought up on the amo-editors mailing list a lot. Add-on authors have two big questions:
These are both very good questions, but sadly, I haven’t seen a really good answer to either yet.
All you have to do is get people to post reviews to your add-on in the sandbox. Yes, there is a slight barrier to entry with this process since AMO requires users to first sign up and then enable the sandbox before they can even post a review. This process is still being smoothed out by the AMO developers (last I knew), so things may get a bit easier. One of the editors has written up a wiki page with directions on how to post a review that you can link your users to.
There are a number of ways in which you can obtain reviews for your add-on. If you extension is site-specify, post on that site about it, and get the users interested in it. If it targets a specific group, perhaps you should reach out to that group through a mailing list or forum. Blogging is quite popular these days, so blog about your add-on; get your friends to blog about it! Perhaps we should start a wiki page and let add-on authors share how they are getting the word out about their add-on.
They certainly can in my book! The catch is that editors are not likely to go out looking for them, so you should absolutely provide URLs to them in your notes to the review section when nominating your add-on for public status. If you don’t provide links, you should expect that we won’t find them.
I hope this clears things up a bit. If you have any questions, feel free to mail the editors list (amo-editors at mozilla dot org) or post comments here.