Apps/StatusMeetings/Engineering/2012-07-10

From MozillaWiki
Jump to: navigation, search

Details

  • Time: Tuesday, 2012 July 10, 9:00 - 9:45am PT (16:00 - 16:45 UTC)
  • Backchannel:
    • irc.mozilla.org #openwebapps
  • Virtual Location:
  • Physical Locations:
    • Mountain View: 4K - Kung Fu
    • San Francisco: 7N - Noise Pop
  • Audio-only Access:
    • +1-650-903-0800 or +1-650-215-1282, x92, conf#: 98652 (US/INTL)
    • +1-800-707-2533, pin: 369, conf#: 98652 (US toll free)

Agenda

  • significant updates
    • Please attend Apps Work Week in MV, July 31 - Aug 3
      • Logistical details?
      • MoCo only or could Marco be invited to this as well?
    • Desktop WebRT - 6 blockers to go, one week until FF 16 merge to Aurora
    • AITC Desktop - Status for FF 16
    • Android WebRT - Status for FF 16
  • questions and concerns
    • Must/Will we have Packaged apps in Basecamp?
      • What are packaged apps?
    • Is b2g doing triage for imminent code freezes that we don't know about?
    • What is happening with basecamp triage?
    • Concern - Desktop and Android WebRT guys are well synced together, but I don't feel like that's the case for B2G in reference to desktop and android
  • roundtable
    • Packaged apps are coming
    • Apps Q3 Goals

Minutes

Significant Updates

  • Please attend Apps Work Week in MV, July 31 - Aug 3
    • rickfant is new VP of marketplace
    • wants to get folks together end of july/early august
    • has notified folks via internal mailing list
    • Apps, like most Mozilla projects/programs/efforts, is community-centric
    • work week organizer has final say, but generally such weeks are open to all significant contributors, regardless of their employment status
    • and bwalker has confirmed that's the case for this one as well
    • so marco should definitely be invited
    • NO ACTION ITEM IDENTIFIED (recommend -> invite marco to work week)
  • Desktop WebRT - 6 blockers to go, one week until FF 16 merge to Aurora
    • at risk
    • six blockers is a large number for such a small non-dedicated team
    • and fixes tend to entrain additional work (followup fixes, regression fixes)
    • if there's any way you can help, please do so!
  • AITC Desktop - Status for FF 16
    • at risk
    • three blockers
    • want AITC for end-of-august event
    • it requires a pref to be turned on
    • but the most important thing is to have the records on the server
    • ticachica wants to make sure legal is ok with it
    • so the current plan is to leave the pref turned off, get legal review, and then turn pref on in aurora
  • myk is concerned about lack of exploration/investigation of interaction between desktop aitc and webrt
    • we haven't figured out how to expose aitc to users
    • but we can decide this later, the minimum viable featureset is to have apps synced to server
    • we should explore and identify the issues here
    • NO ACTION ITEM IDENTIFIED (recommend -> explore intersection between AITC and desktop WebRT and identify issues)
  • apps for fennec 16
    • rags looking into issues for apps on android
    • large list of blockers
    • at risk

Questions And Concerns

  • Must/Will we have Packaged apps in Basecamp?
    • see also Bug 772364 - Implement update mechanism for packaged app
    • see also Bug 756729 - Implement trusted apps
    • there is dependency chain that says packaged apps are needed for basecamp
    • to do things like access device storage api and possibly parts of camera api
    • for which you need to be trusted app, which needs signing, which needs packaging
    • packaged apps are a zip file with an app: protocol whose resources load from the zip file
    • the security model hasn't changed, only the packaging model has changed
    • all trusted apps will need to be packaged
    • untrusted apps might also be packageable at some point
    • this aligns better with what google is doing
    • we should standardize the runtime before we standardize the packaging format
    • Only "docs" we have so far is the initial newgroup posting. But lots of things not defined yet. https://groups.google.com/forum/?fromgroups#!topic/mozilla.dev.webapps/hnCzm2RcX5o
  • will packaging format be cross platform?
    • unclear
    • installation code might not magically work in both b2g and android/desktop
  • when will this land for b2g?
    • everything is supposed to land by july 20
    • but that isn't going to happen
    • some things might land by then
    • it's a few weeks out
  • don't we need changes to mozApps.install API to support this?
    • yes, we do
    • it makes sense to have a separate function to install an app with a URL to the zip file (f.e. mozApps.installPackage)
    • anant thinks we should overload the function (mozApps.install takes a URL that points to either a manifest or a package)
    • biggest change will be about doing updates, which needs coordination with the store
  • unclear if marketplace will be able to support packaged apps by january
    • important to distinguish between hosted vs. packaged apps and trusted vs. untrusted apps
    • -> bwalker to set up meeting between marketplace, security, and platform to discuss work needed to support packaged apps
  • how are developers expected to test packaged apps?
    • only a trusted store can install a trusted app
    • we don't have an answer right now, but it'll be something like addon testing right now
    • f.e. put phone into developer mode
    • we aren't concerned about sophisticated users choosing to install these apps on their devices
    • there'll be some way for developers to do this
  • Is b2g doing triage for imminent code freezes that we don't know about?
    • jsmith raised question with dietrich
    • triage taking place twice a week: tuesdays at 1pm PDT is one time, in dietrich's vroom
    • not necessarily posted to b2g list
    • https://etherpad.mozilla.org/b2g-triage
  • What is happening with basecamp triage?
    • basecamp triage is b2g triage
    • cgalimidi is going to talk to folks about it
    • QA folks are nervous about b2g because it's hard to get a stable build of b2g
    • we have ten days left to get things done for b2g
    • lmandel has been looking at burndown, which is extensive
  • would it help for qa to do analysis?
    • lmandel would first like to talk to dietrich and michaelt
    • -> lmandel to talk to dietrich and michaelt about basecamp status and then let jsmith know if a qa analysis would be helpful
  • Concern - Desktop and Android WebRT guys are well synced together, but I don't feel like that's the case for B2G in reference to desktop and android
    • f.e. jsmith finds bugs in desktop, aaronmt looks for the same bugs on android, keeping quality concerns synced and seeing the big picture
    • doesn't seem to be the same case with b2g
    • multiple "oh crap" moments where jsmith realizes that desktop/android plans don't align with b2g
    • f.e. re: opening links in browser, b2g was going in a different direction, but it changed once folks called their attention to desktop/android plans to do this via target="_blank"
    • b2g folks are not as in tune to what's happening here
    • but we can't ask them to join in on this meeting given that it's 100 people
    • there are a lot of people doing apps related stuff in b2g
    • cgalimidi and lmandel should connect about it
    • part of the reason is that b2g has bigger fish to fry
    • usually we have michaelt here
    • we could ask dietrich to this meeting, but he has a gaia meeting at this time
  • this meeting is not for every individual member of every team doing apps work
    • it is for one representative from each of those teams
    • plus any additional folks who have something to contribute or want to stay abreast of events
    • also, b2g is the h2 project and the organization's topmost priority
    • so the onus is on the desktop/android folks to initiate interaction with them and sync them up while not slowing them down
    • -> cgalimidi to meet with lmandel about syncing up b2g with the rest of the apps efforts

Roundtable

  • Apps Q3 Goals:
    • Ship B2G Marketplace Alpha One in support of BaseCamp for testing and evaluation with 50 Apps, billing implementation agreed, Apps hosting/repository working, Brazil deployment plan agreed, and support model defined.
    • Launch Marketplace Beta for Desktop and Android with Firefox 16 Beta in English speaking countries with 200 Apps, PayPal billing, Apps hosting/repository working, DevHub and support services operating.
    • Publish Master Roadmap for Apps Program with V1 - V3 product features, 2013 Go-to-market plan and overall Business Plan (Goals/KPI's).

Actions

  • bwalker to set up meeting between marketplace, security, and platform to discuss work needed to support packaged apps
  • lmandel to talk to dietrich and michaelt about basecamp status and then let jsmith know if a qa analysis would be helpful
  • cgalimidi to meet with lmandel about syncing up b2g with the rest of the apps efforts
  • NO ACTION ITEM IDENTIFIED (recommend -> invite marco to work week)
  • NO ACTION ITEM IDENTIFIED (recommend -> explore intersection between AITC and desktop WebRT and identify issues)
Retrieved from "https://wiki.mozilla.org/index.php?title=Apps/StatusMeetings/Engineering/2012-07-10&oldid=449221"