I would like to have all the apps I listed below to be on the new architecture when we hit May 2016.
But I doubt we will be able to achieve this if we don't change the way we look at the activities we need have ready for a release. We should resource these apps with the engineers we have to make this a success. And we should staff it in the priority order with some experts from those specific apps. BR Wilfred - > On 13 Nov 2015, at 21:52, Marcus Cavanaugh <[email protected]> wrote: > > What kind of timeline are we aiming for? Given that it's a sorted priority > list, what kind of progress would we need to see for 2.6, 2.7, and beyond to > consider this effort a success? > > Nearly half of these key apps are understaffed at best: contacts, calendar, > calculator, and clock have no full-time engineers allocated afaik. We'll need > to actively dedicate people to this project for this to be successful. (We're > hiring, but I wouldn't expect any meaningful acceleration from hiring efforts > until the start of 2.7 development at best.) > > >> On Fri, Nov 13, 2015 at 9:40 AM, Wilfred Mathanaraj <[email protected]> >> wrote: >> Hi all, >> >> Given the Music app splitting we have done in time for 2.5 we want to move >> ahead - I think it makes sense to be executed in a “train model” fashion. >> We should start from the top of the list and work through the list. >> >> When I say splitting of the apps, we are looking for the following >> activities to be done: >> 1. FE/BE split >> 2. Split views >> 3. Page transition >> >> Why did I choose the priority below? - for now we have 2 products that we >> work on: smartphone and TV, but moving forward we need to investigate what >> are the products that make sense for us and when we enter the connected >> devices market 3rd party developers need to be able to develop differing >> views for our core apps. >> >> With this is mind we went through some exercise to define a priority for the >> apps to be ported to the updated architecture. >> >> Priority list: >> Settings - this is a key app for any product mozilla may be planning to >> release; different apps will have different needs to display information to >> the user in the settings >> Camera - again a key app for a lot of the modern devices >> Contacts - everyone wants to have contacts on their devices - but they need >> different level of information - creating differing views is going to key >> here >> Calendar - as with contacts its critical to have differing views but not as >> high priority as contacts >> Gallery - another core app that every connected device may need to have >> E-mail - typing emails on smaller devices will be a problem and therefore >> creating readable email view may be needed for some connected deviceds >> Calculator - table stake app >> Clock - table stake app >> Browser - one of core mozilla apps but a table stake app for some of the >> connected devices >> >> Some of the engineering teams, who have already worked on this split, will >> be reaching out in smaller teams to discuss best practices and quick wins >> for this activity. >> >> BR >> Wilfred >> >> --- >> FxOS Product Management >> Mozilla Corp., UK >> >> >> >> >> >> _______________________________________________ >> dev-fxos mailing list >> [email protected] >> https://lists.mozilla.org/listinfo/dev-fxos >
_______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
