AMO:AOM Meeting:Firefox 4: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 15: Line 15:
== April 8 ==
== April 8 ==
==== Design ====
==== Design ====
* Have we thought about blocklist


==== Frontend ====
==== Frontend ====

Revision as of 19:48, 8 April 2010

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

Test builds are available from (use builds dated 03/18 or later):

April 8

Design

  • Have we thought about blocklist

Frontend

Backend

Jetpack

Ecosystem

QA

  • Top Issues
    • bug 557956: No compatibility updates downloaded when version gets bumped up
  • Current work
    • First draft of the testplan is available
    • More testing on recent branch builds
  • Questions
    • Will/Can the top search bar also search for available addons (checkbox search pane)?
    • Will the new preferences pane break all addons which come with a preference dialog?
    • Which features will the search pane be able to handle for Firefox 3.7?
    • Is there a way to fetch add-ons from AMO without increasing the download numbers?
    • When do we start to support Jetpacks on AMO?
    • How many instances of the Add-ons Manager tab do we allow?
    • Can Jetpacks and Personas get blocklisted too?
    • When we could consider to have the first accessibility tests?
    • When we can walk through all frontend bugs to identify automated/manual tests?
    • Do we have a final solution about handling add-on dependencies?

April 1

Design

Frontend

Backend

Jetpack

Ecosystem

QA

  • QA has to finish work for Q1 goals / security releases
  • Henrik will work on the test plan next week; Date for the test plan review needed
  • Retornam created initial testplan for the Discovery Pane]
  • Testdays scheduled for 04/27, 04/29, 04/30; Wednesday is free to allow Dave/Blair to fix found problems.
  • Next 3.7 alpha is dumped to after the chemspill releases - should we wait with the merge?
  • Discovery pane: which devs will work on the discovery pane? Can we get a tracking bug?
  • Discovery pane: solution yet for opt-in or opt-out for sending information?

March 25

Design

Frontend

Backend

  • Fixing bugs that block Blair
  • Addressing review comments
  • Current estimate is a trunk landing early next week

Jetpack

Ecosystem

QA

  • Tony already tested and filed a couple of bugs
  • Henrik stepped through all filed bugs
  • Next or 1st week in April we will enhance the test plan to add more details
  • Start verifying bugs after landing on trunk

March 18

Design

  • Faaborg is keen to explore add-on performance and how to show this in Firefox UI.
  • design

Frontend

  • Install/update/uninstall/enable/disable done (some tweaks & fixes needed)
  • Catching up with mockup changes
  • Not quite ready for review / m-c landing

Backend

  • Still need to add plugins to the API but otherwise all main tasks are complete
  • Restartless add-ons are working!!
  • Bulk of the API work has been submitted for code review
  • Need to talk about Q2 goals

Jetpack

  • Jetpack team wants 'no restart' in some 3.6.* release, mossop is exploring

Ecosystem

QA

  • Initial test plan created
  • Proposed to use the [fixed-in-addonsmgr] whiteboard entry for all fixed bugs on the addonsmgr branch A: Yes, its being used now.
  • Links for Prioritized Goals and Redesign Themes should be added as sub pages under the current project page (still on the outdated page)
  • Search results pane is only displayed after a search has been performed? A: Will it get hidden again? yes, it gets hidden.
  • Will the search engine manager now be a part of the addons manager? A: yes.
  • Do we take care about accessibility for the new ui? (marco zehe can help) A: yes, need to have a meeting with Marco at a later time.
  • Is the order of the pane listing on the left side the final one? Shouldn't we order the items from highest to lowest prio, e.g that search pane is not injected in between get addons and languages, which causes other entries to move down. I would like to see a final list and order of those panes. A: Not the final list.
  • Given by johnath the addonsmgr branch should be merged as early as possible to trunk even when QA is not ready with testing. conflict with code freeze for a4? henrik has sent an email to benjamin. A: will not make it into alpha 4. plan is to goto trunk end of next week, but pending early test results.
  • Temporarily tracking top issues here, before bugging them. https://wiki.mozilla.org/QA/Firefox_3.next/Test_Plan:AddonsManagerRedesign#Tracking_Issues

March 11

Design

Frontend

Backend

  • Webpage installs hooked up and working
  • Project branch set up and ready to receive checkins for testing
  • Will be doing perf testing over the weekend and planning out the trunk landing next week

Jetpack

Ecosystem

QA

March 4

Design

Frontend

Backend

  • Working on installs from webpage, need input from the platform guys.

Jetpack

Ecosystem

QA

February 25

Design

Redoing wiki, taking care of some edge cases, specifying how jetpack/extensions and personas/themes work together

Frontend

Nothing exciting. Solidifying code, enable/disable, etc.

Backend

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

Jetpack

https://wiki.mozilla.org/Labs/Jetpack/Reboot/JEP

Ecosystem

  • Updating add-on review process so add-ons can't stay in sandbox forever

February 18

Design

Frontend

No update.

Backend

Considering removing the callback option from InstallTrigger.install

Jetpack

Ecosystem

February 11

Design

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.

Jetpack

Ecosystem

February 4

Design

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

Jetpack

Ecosystem

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

Jetpack

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

Jetpack

Ecosystem

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

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

Ecosystem

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

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")
Retrieved from "https://wiki.mozilla.org/index.php?title=AMO:AOM_Meeting:Firefox_4&oldid=214499"