canmove, Confirmed users
2,056
edits
Apps/StatusMeetings/Engineering/2012-06-26: Difference between revisions
Apps/StatusMeetings/Engineering/2012-06-26 (view source)
Revision as of 17:23, 26 June 2012
, 26 June 2012no edit summary
(→Agenda) |
No edit summary |
||
| Line 38: | Line 38: | ||
= Minutes = | = Minutes = | ||
== Significant Updates == | |||
* jsmith organizing testday friday | |||
** if you have time, jump into #testday channel | |||
** QA will have moderators | |||
** https://etherpad.mozilla.org/testday-20120629 | |||
** feel free to add your name to the etherpad to say you're available | |||
** it does help to lurk, even if you don't have dedicated time to contribute! | |||
== Questions And Concerns == | |||
* services is not listed on responsibility matrix | |||
** bwalker will take care of that | |||
* if you miss a ship date, let services know! | |||
** june 21: services scrambled to get a security blocker fixed, and then we didn't launch anything | |||
** once upon a time, we had a goal of launching marketplace on june 21 | |||
** by removing the requirement for pre-approval | |||
** https://wiki.mozilla.org/Marketplace/Releases (under review due to basecamp) | |||
** -> telliott to join marketplace team mailing list | |||
* getInstalled and getNonInstalled: what's left to do? | |||
** we've reached agreement on the API design | |||
** it's basically the API that sicking proposed on the list | |||
** getInstalled/getAll/getSelf will only return launchable apps | |||
** new getNonInstalled will return only launchable apps | |||
* Concern - The two flash blocker bugs for desktop web runtime have received little traction in almost a month | |||
** john schoenick is back to working on them! | |||
** they're his top priority this week | |||
* What other payment providers besides Paypal are being considered for in-app purchases? | |||
** you're poking the bear! | |||
** in the short term, we're working directly with bluvia folks (subsidiary of telefonica; provides payment services for mobile) | |||
** version one will be client side; specific to b2g; happens through navigator.pay interface; as little as possible (down to nothing) stored on the server | |||
** current implementation on desktop and android is with paypal | |||
** we might consider additional payment providers in the future | |||
** a developer that wants to sell in both brazil and android will have to implement two payment mechanisms | |||
** we are going to be providing developers with a client-side library and server-side hooks to determine whether they're on android or b2g | |||
* priority of implementing navigator.pay on android and desktop? | |||
** we're only focusing on b2g use case | |||
** benadida has ideas about what v2 might look like | |||
* How do we balance our apps product concerns for Android Web Apps Experience with the feasibility of what we can or can't do on Android? | |||
** folks are raising various issues | |||
** it isn't clear that we can do enough on android | |||
** android has a bunch of challenges for us | |||
** f.e. we can't generate APKs without requiring you to enable untrusted sources | |||
** as we dig into the details, we're identifying more android-specific challenges | |||
** we'll have to navigate these challenges as we go | |||
** android web runtime triage is happening friday, should help answer some of these questions | |||
* when are we going to allow anyone to access the marketplace? | |||
** rick is the new vp for the marketplace business | |||
** he's working with folks to plan alpha and beta milestones for the year | |||
** that will happen this week | |||
** we should know more next week | |||
* http app ran into problem caching https urls and vice-versa; who can we talk to about it? | |||
** the best person is honza bambas | |||
** mayhemer on IRC | |||
* plugin support in webapps: on b2g we have no plugins, period; probably never will; but on desktop we're supporting flash and only flash; is that the case, and is it set in stone? | |||
** yes, for two reasons: there are a bunch of flash games, and flash is the solution for media playback | |||
** we started with no plugins on desktop as well | |||
** but we realized we won't get h264 playback in time | |||
** so we have to go with flash | |||
* "flash fire" happened; a huge spike in flash-related crashes, which bled firefox users; how do we mitigate the risk? | |||
** we mostly do the same thing we do for Firefox | |||
** but if we get a bunch of flash games, and they're crashy, we might do something special with the socorro team | |||
** we don't need to do anything special at this point, but we should be aware of the possibility and be prepared for it | |||
** we might not have as much leverage with adobe for problems in a webapp | |||
** and problems might be specific to a webapp or the runtime | |||
** good to note and be aware of; nothing to do at this point | |||
** having crash data is important | |||
** at some point we'll want to be better tied into release drivers and have communications plan in place | |||
** so when we have millions of users and a chemspill we know what to do | |||
** crash isn't as much of a risk on runtime because user more likely to blame app rather than firefox | |||
* has anyone thought of automated testing of gecko in the webapp runtime? | |||
** one of the blockers is to get unit testing up and running for the runtime | |||
** we want to test what content can do as well as what chrome does in the runtime | |||
** but the question might be whether we can run existing content tests that we currently run in firefox, but in the webrt context | |||
** there is a race condition that cannot be triggered in firefox but can in webrt, so it may be worth looking into | |||
== Roundtable == | |||
* future of this meeting | |||
** new vp rick sent out an email | |||
** goal to establish a main engineering coordination meeting for all engineering groups doing apps-related work | |||
** bwalker would like this meeting to become that main engineering coordination meeting | |||
** myk has been evolving this meeting in that direction over time | |||
** would need additional representatives, f.e. from b2g | |||
** we need to tightly coordinate amongst all the teams | |||
* Q: does this meeting conflict with the b2g gaia meeting? A: yes. | |||
* what about folks who attend monday marketplace meeting? | |||
** that meeting has plenty of content and likely needs to continue | |||
= Actions = | = Actions = | ||
* telliott to join marketplace team mailing list | |||