Apps/StatusMeetings/2011-08-30: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
 
(11 intermediate revisions by 7 users not shown)
Line 5: Line 5:
* AI: Figure out next steps on BrowserID integration
* AI: Figure out next steps on BrowserID integration
* David Clarke is putting together a test plan and should identify what we need.
* David Clarke is putting together a test plan and should identify what we need.
** Done, see https://wiki.mozilla.org/Apps/QA - new Home page
* Mobile folks are waiting for 641552 to land.  
* Mobile folks are waiting for 641552 to land.  
* AI: Paypal is still not done.
* AI: Paypal is still not done.
Line 11: Line 12:
* We will ship first version of F1 with client side oAuth and then update when sites support OWA.
* We will ship first version of F1 with client side oAuth and then update when sites support OWA.
* AI: Figure out meeting format for the future.
* AI: Figure out meeting format for the future.


== General/Product ==
== General/Product ==
Line 21: Line 21:


=== Client Platform  ===
=== Client Platform  ===
* Will be spending this week bringing HTML version into parity with the Jetpack (particularly activities)
* Also implementing Activities API v2 on Jetpack, improving test coverage


=== Dashboards  ===
=== Dashboards  ===
Line 36: Line 39:


== QA ==
== QA ==
* Open Questions
** The add-ons manager has only basic support for add-ons to purchase in search results. When can we expect a testing site to ensure missing features can be added to the AOM in-time?
** Are there any plans yet how to solve dependencies between add-ons? Do we need support in the AOM to install required add-ons first?
** How will a purchase via the AOM work? We don't know the users account and can't associate the purchase.
* Action Items
** OWA test infrastructure doesn't run with latest version of node
** Test Infrastructure: Marketplace
** Test Infrastructure: Central server to go to for latest xpi for owa extension.


== Security ==
== Security ==
* Security reviews for [https://wiki.mozilla.org/Security/Reviews/WebActivities Web Activities] and [https://wiki.mozilla.org/Security/Reviews/F1_%28round_2%29 F1] occurred on 8/26
* Action items
** [bsterne] will need to assign someone for penetration testing once implementation is more finalized
** [bsterne] to schedule further threat modelling discussion with Mike, Ben, Shane
*** [COMPLETE] scheduled for Friday, 9/9 at 1PM in 3 - PB&J
** [dchan] code review
** [sstamm] privacy review
** [scaraveo] need to figure out if the temporary part for Twitter OAuth will end up in the product, or if we can cut it out before the first release.
** [scaraveo] final decision on screenshot thumbnail sharing, this decision will need to be communicated back to secteam
** [scaraveo] bug to track fixing the of OAuth flow/dialog/injector
** [scaraveo] talk to jst about popup blocker code
==AppStore Security==
* https://wiki.mozilla.org/Security/Reviews/AppStore
* https://wiki.mozilla.org/Security/Reviews/AppStore#Application_Security_Requirements
* https://wiki.mozilla.org/Security/Reviews/AppStore#CEF_Logging_Requirements
* https://wiki.mozilla.org/Security/Reviews/AppStore#Data_flows


== User research ==
== User research ==


== Marketing & PR ==
== Marketing & PR ==
Documentation required for MDN pages: http://etherpad.mozilla.com:9000/NvKppMhS4c
Please take a look, and contribute content and existing content URLs.


== Support ==
== Support ==


== Action Items ==
== Notes & Action Items ==
 
* Plan is to integrate BrowserID - we are back on track, expect a patch to land this week or next.
* Wiki/Apps/QA has the beginnings of the test plan.
* PayPal still hasn't replied yet - sales tax and export control are moving along. We are working on the developer agreement.
* Got the AJAX forms done, working on adding prices to your add-on and your app
* Will probably have the developer flow done.
* Shane is still waiting on UX help for F1. Will work with Bryan.
* Hoping to have status.net implemented, should be able to show twitter. Show the drive by discovery panel.
* AI: Shane to ping Alex on F1 flows
* Prioritize HTML sync over HTML activities
* AI: We need to figure out an engineering implementation plan Bill will do that.
* Ben Adida thinks that we have 90% confidence that the OWA manifest will be deployed by Twitter on Tuesday.
* AI: We need build/rel automation
* AI: Anant/Bill will follow up with Justin on making sure the OWA jetpack doesn't get pulled repeatedly from AMO.

Latest revision as of 17:06, 30 August 2011

Agenda

AIs/Follow ups from last meeting

  • AI: Figure out next steps on BrowserID integration
  • David Clarke is putting together a test plan and should identify what we need.
  • Mobile folks are waiting for 641552 to land.
  • AI: Paypal is still not done.
  • AI: Need UX help for F1.
  • AI: David is owning the partnerships for F1.
  • We will ship first version of F1 with client side oAuth and then update when sites support OWA.
  • AI: Figure out meeting format for the future.

General/Product

ILUM (Install, Launch, Use, Manage)

  • Finalize the All Hands demo end to end flows for dashboards.
  • Work with Engineering and QA to put the Dashboard Spec into engineering plans and test plans for All Hands and Q3 delivery.

Engineering

Client Platform

  • Will be spending this week bringing HTML version into parity with the Jetpack (particularly activities)
  • Also implementing Activities API v2 on Jetpack, improving test coverage

Dashboards

Marketplace

f1

  • Web Activities progressing well with Twitter. APIs validated, test deployment hopefully next week.

QA

  • Open Questions
    • The add-ons manager has only basic support for add-ons to purchase in search results. When can we expect a testing site to ensure missing features can be added to the AOM in-time?
    • Are there any plans yet how to solve dependencies between add-ons? Do we need support in the AOM to install required add-ons first?
    • How will a purchase via the AOM work? We don't know the users account and can't associate the purchase.
  • Action Items
    • OWA test infrastructure doesn't run with latest version of node
    • Test Infrastructure: Marketplace
    • Test Infrastructure: Central server to go to for latest xpi for owa extension.

Security

  • Security reviews for Web Activities and F1 occurred on 8/26
  • Action items
    • [bsterne] will need to assign someone for penetration testing once implementation is more finalized
    • [bsterne] to schedule further threat modelling discussion with Mike, Ben, Shane
      • [COMPLETE] scheduled for Friday, 9/9 at 1PM in 3 - PB&J
    • [dchan] code review
    • [sstamm] privacy review
    • [scaraveo] need to figure out if the temporary part for Twitter OAuth will end up in the product, or if we can cut it out before the first release.
    • [scaraveo] final decision on screenshot thumbnail sharing, this decision will need to be communicated back to secteam
    • [scaraveo] bug to track fixing the of OAuth flow/dialog/injector
    • [scaraveo] talk to jst about popup blocker code

AppStore Security

User research

Marketing & PR

Documentation required for MDN pages: http://etherpad.mozilla.com:9000/NvKppMhS4c

Please take a look, and contribute content and existing content URLs.

Support

Notes & Action Items

  • Plan is to integrate BrowserID - we are back on track, expect a patch to land this week or next.
  • Wiki/Apps/QA has the beginnings of the test plan.
  • PayPal still hasn't replied yet - sales tax and export control are moving along. We are working on the developer agreement.
  • Got the AJAX forms done, working on adding prices to your add-on and your app
  • Will probably have the developer flow done.
  • Shane is still waiting on UX help for F1. Will work with Bryan.
  • Hoping to have status.net implemented, should be able to show twitter. Show the drive by discovery panel.
  • AI: Shane to ping Alex on F1 flows
  • Prioritize HTML sync over HTML activities
  • AI: We need to figure out an engineering implementation plan Bill will do that.
  • Ben Adida thinks that we have 90% confidence that the OWA manifest will be deployed by Twitter on Tuesday.
  • AI: We need build/rel automation
  • AI: Anant/Bill will follow up with Justin on making sure the OWA jetpack doesn't get pulled repeatedly from AMO.