malliz wrote:http://forums.mozillazine.org/viewtopic.php?f=38&t=2650547
I wonder how many just don't bother to ask?
Made into a sticky until this is resolved.
malliz wrote:http://forums.mozillazine.org/viewtopic.php?f=38&t=2650547
I wonder how many just don't bother to ask?
jorgev wrote:
Add-on stats are private by default, but developers can make them public if they choose to. So, for example, you can see the stats for Remote XUL Manager, but not the stats for Easy YouTube Video Downloader. Same goes for themes. Personas are different because I believe the update ping still points to getpersonas.com, so they are handled differently. If I try to look at the stats for a Persona, I see a message saying there is no data.
jorgev wrote:As for the bug fix being delayed, that tends to happen when there's design work at play. First the design needs to be approved, then implemented and finally pushed. We're trying to get this out as soon as possible. The change to Complete Themes (another oversight in the old design) was just an easy change which is why it was done first.
LoudNoise wrote:
It is curious that this bug https://bugzilla.mozilla.org/show_bug.cgi?id=822486 , which resulted in a major change, got pushed with three posts and in less then a month.
LoudNoise wrote:So, other then download numbers you folks don't actually have any information about how popular/how many folks use Personas?
malliz wrote:Meanwhile what about just getting the AMO page fixed as a matter of priority?
malliz wrote:Seriously if it had a bug in it it would have been fixed already
malliz wrote:you are talking to people who know how to code web pages and know how quickly this could be solved if Mozilla wanted to
jorgev wrote:When it requires design work and approval by the team, it takes longer.
jorgev wrote:Coding a web page is different from maintaining a site as large as AMO. It's not just a matter of editing a file and uploading it to a server. If it were just a simple code change, it could be done within a week because of the push schedule. When it requires design work and approval by the team, it takes longer.
LoudNoise wrote:The name mess is going to big. Someone is going to have to go through MDN and replace Themes with Complete Themes and Personas with Themes. If you do a google search the only hits you get for Firefox making Themes that have anything to do with Personas is how-to pages from Brandduhder which means the means that there is likely to be an increase in hijacked search questions.
If you call something "Themes" for more then 12 years and then suddenly decided to call them something else you are asking for the trouble you are going to get. For at least a few years someone who wants to make a nice skin is going to have to work through a vast collection of useless information (to them) if they do a search. They will also need to rename all the Persona utilities at AMO.
The same problem is likely to make BrowserID largely irrelevant. It is like Coca Cola decided to concoct a new fruit drink and name it Coke while renaming the legacy cola drink Sprite.
This is classic Mozilla. It would not have been all that difficult to find a new name for BrowserID (which I'll admit sucked). Instead they chose not to do so, will either spend a hell of alot of money (or not, I have never been impressed by their attention span) changing things to avoid confusing folks, confuse them anyway and piss off a number of folks both during the change and for quite a bit afterwards.
All of which would be fine if "Persona" was an extremely compelling name to describe BrowserID. It isn't, if anything it works better for the skins. secureid isn't trademarked (securid is so it might not be the best choice) and would be a considerably better description of the product.
jorgev wrote:Yes, I'm sure everything in your workplace happens instantaneously by sheer will power.
jorgev wrote: I think we will also update the screenshot Frank Lion mentioned.