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
June 3rd 2010
Design
Mocks added to bugs:
- bug 562300 cancel installation
- bug 567120 uninstall confirmation
- bug 553491 blocklist, needs additional mocks
- bug 553455 website install notification
Main focus is now on final graphics unless there are other major bugs that need consideration (anyone?). Final graphics are not done, some initial mockups are here
Other bugs (rdoherty)
- bug 550628 Add "don't show this again" to persona install notification
Frontend
Backend
Jetpack
Ecosystem
QA
- Addons Manager and Extension API
- General
- Will also cover these projects:
- Pull More AMO Data into Addons Manager
- Addons Compatibility Reporter
- Will also cover these projects:
- Testplan: Working on a tracking spreadsheet
- Bug Queries have been updated
- Litmus
- List of expected Litmus tests (Raymond)
- Upcoming Schedule
- Waiting for arrival of final mockups June 4th
- Next testday is on June 11th
- Questions
- Bugs: bug 565610 - Importance of overlaying about: urls
- Bugs: Handling blockers for additional betas vs. final
- Languages: Which specific features we will support? (Install/Uninstall/Switching?)
- Jetpacks: Do we officially use the name Jetpacks or restartless extensions?
- Jetpacks: Can those be installed system-wide (app folder, registry)?
- Jetpacks: Can we get an example Jetpack on AMO
- UI: Usage of modal dialogs (Beltzners Fx4 presentation); e.g. bug 567120
- Discovery Pane
- No update
May 27th 2010
Design
Frontend
- Blair has been working on automated tests for the UI
Backend
- Made plans with bsmedberg to remove the EM restart during startup
- Catching and fixing some bugs critical for the next alpha release
- Started work on the documentation, slow going but getting there
Jetpack
- E10S support in Jetpack possibly in 0.5 or 0.6 release.
- Will allow for isolating perf impact of add-ons individually
- Invisible Hand already ported to Jetpack
- WOT likely next on list
Ecosystem
- Currently exploring a variety of payment options with emphasis on security and user experience
QA
- Overall
- General
- Do we wanna have bugs for the implementation of each of the mockups?
- TODO: Sync mockups with testplan next week
- Testing
- Keeping up2date with verification work
- Litmus
- Started to compile a list of Litmus tests (Raymond)
- Schedule
- Waiting for arrival of final mockups June 4th
- Next testday is on June 11th
- Discovery Pane
- Clearing out communication issues
May 20th
Design
Remaining stuffs is getting done, such as:
Dave made a helpful list of most important bugs, next priorities are:
- Compatibility checks during startup of a new app version
- Blocklists
- Canceling an add-on installation after accepting the installation
- Uninstall confirmation dialog
- Notification of addons being installed from websites
O here are In content UI first mockups
Frontend
- Blair has been working on automated tests for the UI
Backend
- Prioritised the bugs needed for release
Jetpack
- E10S support in Jetpack possibly in 0.5 or 0.6 release.
- Will allow for isolating perf impact of add-ons individually
- Invisible Hand already ported to Jetpack
- WOT likely next on list
Ecosystem
- [1] Lots of interest here both internally and externally
- Some stats: 12% of public Fx add-ons ask for contributions, average revenue per add-on is about $130 but top 3 add-ons comprise 15% of all contributions.
- Currently exploring a variety of payment options with emphasis on security and user experience
QA
- Overall
- General
- As sent-out by Dave we need final Mockups ASAP. When will those arrive? (June 4th)
- Talk about the best way to prioritize bugs for next alpha or beta1
- Do we still need the bug dependencies and whiteboard entries?
- Correct components for existent bugs (right now nearly all are in addons manager)
- Search Engine pane should be hidden (bug 567115)
- Testing
- Finished verifying all fixed bugs.
- Schedule
- Next testday is on June 11th
- Litmus
- Compiling list of Litmus tests.
- Discovery Pane
- No update
May 13th
Design
- This has been UX work week, so mostly in meetings. Going through the UIwanted list still. in-content ui not ready
- UI ideas:
Frontend
- bug 565610 - Overlays don't work on about: URLs - deal-breaker for EM-related extensions. Should be fixable.
Backend
- Re-landed on trunk and working through the remaining issues
- Saw about a 1s Ts improvement for the Fennec guys
- First startup and migration startup times can be vastly improved
Jetpack
Ecosystem
- Discovery Pane scaffolding launching today. link
- Paid add-ons in EM: https://bugzilla.mozilla.org/show_bug.cgi?id=562790
QA
- Overall
- General
- Now that a lot of ui bugs have been fixed, Blair should check the in-testsuite flags. I do not wanna do Litmus work when it can be automated.
- Testing
- Started verification of fixed bugs
- Schedule
- Planning for exact schedule for the next testday
- Litmus
- Starting to add new Litmus tests by next week
- Discovery Pane
- No update
May 6th
Design
- Really not much done this week - a few bugs, more to go through
Frontend
Backend
- The source of the Ts regression has been found, working with IT and Releng to figure out when we can reland.
- Fixed some of the more obvious functionality errors found at the testday
- Investigating a couple of bad cases that I can't reproduce yet.
Jetpack
Ecosystem
QA
- General
- Testday
- Tests
- No overall testing this week; waiting for feature re-landing
- First accessibility tests showed good results
- Schedule
- ETA for final design? Wonder if all ux members work together to give any part of the ui the same look; AMO design is made for Mac but not for Windows as all the other designs; makes it hard to compare.
- As proposed by Mike the search pane should be included in beta 1
- Add-ons Compatibility
- Will there be tutorials for Add-on developers to make their life easier in updating their add-ons?
- Will we have a stable Jetpack API for beta 1 or are other breaking changes expected?
- Mike wants to see people create Jetpacks instead of oldish extensions for RC1
- Discovery Pane
April 29
Landing
- Can we? Pretty please? I'll give you a cookie!
- Yes, now where's my cookie?
- Can I have one too? Plz?
- Yes, now where's my cookie?
- Mobile has branched - don't need to worry about breaking it now
- SeaMonkey is shipping an alpha soon (based on trunk). They'd like consideration for holding off til the 4th if we don't land today, but its not a big deal if we don't.
- Development plans for post-landing
- Usual file bug, attach patch, get review, land - but on project branch? Or on mozilla-central?
Design
- Knocking off some ui-wanted bugs
- Balance time between fire fight & new - what do people need?
- Starting to work w/Shorlander on final graphics
Frontend
- Text describing the Contribute button (ie, its tooltip) - what should it say? (Disclaimer: doesn't actually work yet)
- Should say "If you enjoy using <addon name>, please consider making a small contribution to the developer"
Backend
Jetpack
Ecosystem
QA
- Issues
- Top Issues
- bug 554234: We have changed the behavior and only allow one single addons manager tab open?
- bug 465090: Keyboard shortcut to open the addons manager?
- bug 562360: Compatibility information for add-ons on preview.addons.mozilla.org are not in sync with public pages (Mozmill Tests)
- Purpose of "Your Rating"? We don't share ratings? Missing documentation on design docs
- uiwanted bugs should be processed. We have to many of them.
- State of a Jetpack example?
- Trunk landing
- Needs to have localized nightly builds (localizers will help testing)
- We have to spin new nightly builds after landing (releng is informed)
- Community
- Tomorrow is Testday time!
- Testday focused areas
- When do we wanna have the next testday? Do we have realistic dates?
Personas
April 22
Design
Frontend
Backend
- 2 reviews remaining, at least one should be done by the morning, hopefully the other too. Basically ready to land.
- Next alpha freeze is at least a week away and could be pushed back further at our request.
- May have to delay landing for the mobile team though.
Jetpack
Ecosystem
QA
- Top Issues
- bug 553092: Initialise the permissions manager
- Testing
- Continued testing of branch builds and filed bugs
- Reduced testdays to only Friday next week
- Questions
- What happened with the Get More Extensions/Themes links? We should linkify AMO from within the addons manager
- Others
- Please use bug numbers in the commits for your check-ins
- Henrik is away this Friday and Monday
April 15
Design
- some changes to wiki regarding manual install and checks for updates: link
- don't want to take up time with manual check/install case again unless people are interested, but details are in bugs bug 553503 and bug 553502
- did want to bring up Download Manager changes: Download Manager is becoming a record of all files download, even updates for Firefox and Add-ons. I think this could take the place of an in-addons-manager log. It's already going to be listed within the Downloads Manager, so we'd need to create a second log in add-ons already (can updates be "undone" from Download Manager?)
- just planning hard and soft blocks (two levels, not three) as a third has not been identified as needed. Soft block creates an extra screen in install process explaining risks, hard block shows screen explaining before install. (Question for Nick - should hard blocks be overridden for any case?)
Frontend
- First round of reviews done - not expecting anything big from 2nd round
- Just a few landing-blockers left
Backend
- Main reviews are done. Waiting on additional reviews for a couple of parts from bsmedberg and dveditz
- Couple of bugs I still need to complete but they should be fast
Jetpack
- Code freeze for 0.3 on monday more info
Ecosystem
- Discovery Pane scaffolding and prototype milestone started Tuesday
QA
- No updates - waiting for fixes
- Link to the Blocklist documentation?
- Plan for trunk merge? Dave will speak to Benjamin about the next freeze.
- Working through remaining ui-wanted bugs?
April 8
Design
- Blocklist for next week:
- Hard block and soft block currently supported, the API would support a third
- Talked about manual updates, if a log is requires
- Decided a log is important, and so is being able to easily apply manual updates
- Requires updated design: current "Updates" pane that shows both could be confusing
Frontend
- Lack of progress due to holidays and sickness
- Initial review went well - almost done and ready for next round
- Still some blockers left to do (eg, bug 553515, bug 554245, bug 553631, and unbreaking existing tests)
Backend
- Undergoing final round of review for the first trunk landing
- Couple of small bits and pieces to fix up before that
- QA have identified some issues and we'll need to prioritize them
Jetpack
Ecosystem
QA
- Top Issues
- bug 557956: No compatibility updates downloaded when version gets bumped up
- We should block at least for the compatibility check. Further work can happen after trunk landing
- Which is the list of blocking bugs for trunk landing?
- All blocking bugs are handled with the P1 priority flag. There are 61 bugs => Needs re-prioritization
- bug 557956: No compatibility updates downloaded when version gets bumped up
- Current status
- Tchung dropped of from testing
- 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 (disabled checkbox in search pane)?
- For now, searches will only be run locally. Remote searching will land after the trunk merge. bug 558287
- Will the new preferences pane break all addons which come with a preference dialog?
- We will allow existing preferences dialogs; In the list view you can open it via the context menu; Extra button for detailed view?
- Which features will the search engine pane be able to handle for Firefox 3.7?
- Work will not happen before trunk landing; All features should be included in the final version; Blair will probably work on it => bug 558289
- Is there a way to fetch add-ons from AMO without increasing the download numbers?
- Yes, we should use the preview site instead of the public one.
- When do we start to support Jetpacks on AMO?
- Scheduled for same version as the Discovery Pane landing; We could upload Jetpacks to the preview site
- How many instances of the Add-ons Manager tab do we allow?
- Multiple tabs per window
- Can Jetpacks and Personas get blocklisted too?
- Only Jetpacks
- Do we have documentation for blocklisting?
- Dave will find the best docs for me
- When we could consider to have the first accessibility tests?
- Probably after landing on trunk
- When can we walk through all frontend bugs to identify automated/manual tests?
- Sometime after trunk landing
- Do we have a final solution about handling add-on dependencies?
- It will be dropped
- Will/Can the top search bar also search for available addons (disabled checkbox in search pane)?
April 1
Design
- Talked about manually updating add-ons in cases where addons are set to be updated automatically, only some addons are set to be updated automatically, and all addons are set to be updated automatically
- Talked about purpose of get add-ons pane, if preferences make sense here
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
- Discovery Pane spec first draft
QA
March 4
Design
Frontend
Backend
- Working on installs from webpage, need input from the platform guys.
Jetpack
Ecosystem
- Discovery Pane spec first draft
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
- 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
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
- 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")