AMO:AOM Meeting:Firefox 4

AMO Project Meeting Details

Thursdays, 2:30pm Pacific, 4:30pm Eastern
1-800-707-2533 (pin 369) or 1-650-215-1282 or 1-650-903-0800
Conferencing Center: x92
Conference ID: 357

February 25

Backend

In the process of making installs from webpages work, this is the main blocker I have before we could consider a trunk landing.

Ecosystem

• Jetpack 0.1 due out in the next week.

February 18

Frontend

No update.

Backend

Considering removing the callback option from InstallTrigger.install

February 11

Frontend

• Download progress widget done. Should be possible to do a fancy button -> progress transition.
• Local search done - including sorting based on relevance to search string
• AMO search not done - need API support and UX details

Backend

No update, no Mossop.

February 4

Frontend

Working on getting UI up to speed with Boriss' mockups.

Getting it on trunk:

• Want it on trunk sooner (alphas) rather than later (betas)
• Project branch
• Maybe land without major AMO integration? (use followup bugs)
• UI doesn't need to be pixel-perfect or even finalized (again, use followup bugs)
• Minimum: needs to be able to manage addons

UI qustions:

• Discover pane - complement or replacement of Recommended?
• Want a way to display multiple screenshots?
• Lots of white-spece between relevant things on larger screens (looks great on small/medium sized screens)
• Link to AMO developer profiles - what about multiple developers, that install.rdf doesn't list?
• Detail view at https://wiki.mozilla.org/Extension_Manager:UI_Update_questions isn't very detailed - only adds screenshot (compared to list view); not much value, no incentive to go there

API questions:

• Should API be caching remote resources like screenshots?
• With AMO integration, addons not hosted on AMO will have sub-par experience. add support for additional things like screenshots to install.rdf?
• Status of install/update stuff?

Backend

No update

Ecosystem

• Discovery Pane ideas
• API development underway

January 28

Design

• Been making some changes to the design (not too major), in light of feedback & talks with ux
• Been answering unsure/unanswered questions, many of which graciously supplied by Mossop (Q&A style going on here.)
• Rewriting wiki, getting rid of superfluous stuff - want to make it clear what design is current
• Did random blog post, am getting good feedback
• On Monday, UX is doing lockin session on Prefs and EM - these tend to be six hour design sessions where we hash out everything, look for dependencies, fight!
• Items I'd like to discuss:
  • Personas vs. Themes - especially after seeing Personas post mortem, this seems a bit pricklier than I'd even imagined. How are we thinking about these? Is it decided? What do we have to go on before going ahead on a design?
  • Jetpack - where are we now that 3.6 has shipped? Do we know anything new

Frontend

No update.

Backend

No update

Ecosystem

• Question: what is the plan for uplifting personas plus UI into Firefox?

January 21

Design

• Small changes to existing mocks in wiki, as discussed last week
• A few new mocks, but not yet on the wiki (bad bad!), will add tonight
• Looked at notification styles, trying to align what we tell the user and when, and how we can do less of it. Have a working model of omg (priority 1, can't be dismissed), ok (action is required, but not now, and you'll probably do it anyway), and eh (something happened that you don't care about). I'll explain more in the meeting.

Frontend

No update.

Backend

• Worked on being less restrictive about what html developers can use in their release notes

January 14

Design

• latest from Boriss, hooray!
• Nick wants contributions in the mocks, here's some metadata to consider
  • link to contribute going to AMO meet the dev page
  • dollar amount
  • buy vs contribute
• Feedback from fligtar
  • We can consider getting add-on status data from AMO along with reviews and downloads, and show whether add-ons are reviewed by Mozilla or not reviewed by Mozilla (experimental, self-hosted, and non-hosted add-ons)
  • We should change Recommended to Featured
  • Not a fan of the name Features for add-ons
  • Should be more distinction between My Add-ons and browsing for new add-ons
  • I don't think size information is useful or important to display on every add-on
  • I don't think we need to worry about integrating collections for 3.7. The Add-on Collector will add sections for Personal Recommendations and Collections to 3.7 and we'll be changing the way collections works considerably this year. Perhaps it will be stable enough for core integration for 4.0

Frontend

• http://skitch.com/unfocused/nxxhi/add-ons-manager
• http://skitch.com/unfocused/nxxh6/add-ons-manager

Note: That's on OSX. Needs tweaks on Windows (and probably Linux) to make it look not ugly.

Backend

• Produced list of requirements from AMO API
• Removing support for extension dependencies.
• Tweaked some of the notifications to better suit add-ons that don't require restarts.

Jetpack

• new post from atul on the jetpack reboot

January 7

Design

• Boriss furiously slapping together mocks, will post to wiki

Frontend

• Blair working on initial prototype of EM in content

Backend

• Mossop to provide suggestions for changes to API as we rewrite services.amo

Jetpack

• Jetpack rewrite happening which will allow authors to write jetpacks and build them into standard extensions

Ecosystem

• AMO being rewritten in Python/Django
• API update in February will feature add-ons by locale (currently all browsers get the US feed)

October 29

• Boriss has created mocks to show in content
• Todo: start looking at how to blend different types of add-ons into a single list, and incorporate AMO metadata
• Mossop still working on 3.6 blockers, should start work on API stuff next week.
• Johnath and Gavin coming next week, will sync up on prefs + EM work

September 17

Personas

• Much of the backend now on trunk (today's nightly), still waiting on bug 511771 before it is fully functional though.
• https://bugzilla.mozilla.org/show_bug.cgi?id=510909#c39 has a hacky way to play with the UI

Plugins

• Adding rudimentary ways to check for plugin updates to the add-ons manager. See the screenshots in bug 514327. Checking for updates loads a webpage that will explain how to update.

September 10

Design concepts needed

• Contributions
• Reviews (both read and submit)
• Better, friendlier browse experience
• Personalized Recommendations
• Performance gauge

Personas

• Will land in 3.6, not in minefield yet. Hopefully we'll be able to see this integration next week

Timing

• We should start having this meeting weekly, and set goals with the intent of including a new add-ons manager in 3.7
• Naming of the add-ons manager may change with the goal of creating greater awareness of add-ons (e.g. "Firefox App Store")