canmove, Confirmed users
2,056
edits
Jetpack/Features/2011-11-04: Difference between revisions
Jump to navigation
Jump to search
add minutes
(→Agenda) |
(add minutes) |
||
| Line 1: | Line 1: | ||
= Details = | |||
* Time: Friday, 2011 November 4, 9:05 - 9:50am PT (16:05 - 16:50 UTC) | * Time: Friday, 2011 November 4, 9:05 - 9:50am PT (16:05 - 16:50 UTC) | ||
| Line 8: | Line 8: | ||
*** US/Intl: +1-650-903-0800 or +1-650-215-1282, extension 92, conference number 99449 | *** US/Intl: +1-650-903-0800 or +1-650-215-1282, extension 92, conference number 99449 | ||
= Agenda = | |||
* review actions from previous meeting | * review actions from previous meeting | ||
| Line 19: | Line 19: | ||
** dietrich to figure out if Jetpack reviewers are core reviewers and, if not, what it would take to make them such | ** dietrich to figure out if Jetpack reviewers are core reviewers and, if not, what it would take to make them such | ||
** myk to establish working group with regular meetings to determine feasibility of modular Firefox feature development using Add-on SDK | ** myk to establish working group with regular meetings to determine feasibility of modular Firefox feature development using Add-on SDK | ||
* F1 and meeting with Chris Lee | |||
* review project schedules and establish knowledge/decision-making milestones | * review project schedules and establish knowledge/decision-making milestones | ||
* understanding l10n plan | |||
= Attendees = | |||
== | * dietrich | ||
* ttaubert | |||
* dascher | |||
* mixedpuppy | |||
* myk | |||
* pike | |||
= Minutes = | |||
== review actions from previous meeting == | |||
'''dietrich to get results from BrowserID performance test runs and post them to BrowserID wiki page'''<br> | |||
'''dietrich to talk to build team about performance test run issues''' | |||
* dietrich hasn't had time to do these but intends to, so they remain on list | |||
* performance testing should happen for F1 addon as well | |||
* teams should be able to share the cedar project branch | |||
* [[https://etherpad.mozilla.org/identity-fx etherpad about using cedar branch]] | |||
'''mixedpuppy to test the new navigator.* feature in aurora (firefox 9), provide technique to stomlinson''' | |||
* mixedpuppy got it working, and it works great | |||
* he rewrote injector.js script to have a backward compatibility shim | |||
* the work is in an OWA branch that anant should review and land today | |||
* info forwarded to BrowserID team | |||
'''myk to follow up with dcm, who is not present, about localization meeting''' | |||
* l10n is top priority for Jetpack team, ochameau is working on it in bug 691782 | |||
* Q4 goals are to support l10n of strings in JS and have plan for l10n of strings in HTML | |||
* integration with l10n web application/service moved to future phase of development | |||
* initial phase of development to support manually-bundled files | |||
* BrowserID, OWA, F1 Sharing features want to ship as soon as possible | |||
* BrowserID loose goal as of a couple weeks ago was proof of concept by end of year | |||
* OWA goal sounds like alpha in two weeks, release in January/February | |||
* we should decouple Jetpack long-term plans from short-term needs of features | |||
* Test Pilot addon experience may be instructive: strings localized via standard process and shipped in core | |||
* we could do the same for these features and then write scripts to convert .properties files to JSON format supported by Jetpack | |||
* or features could use .properties files directly via XPCOM | |||
* l10n team developers busy working on native android app localization, not available to write scripts | |||
''-> someone (dascher?) to figure out who on identity team will be driver for l10n''<br> | |||
''-> myk to report back on the specifics of Jetpack's l10n plan''<br> | |||
''-> myk to identify and propose short-term plan to localize these features''<br> | |||
'''dietrich to blog about modular development''' | |||
* [[http://autonome.wordpress.com/2011/10/25/building-firefox-in-the-post-browser-age/ so blogged]] | |||
* benadida plans to follow up with more specifics | |||
'''dietrich to figure out if Jetpack reviewers are core reviewers and, if not, what it would take to make them such''' | |||
* dietrich talked to gavin and mossop about it | |||
* gavin thinks jetpack developers should be reviewing jetpack code, including code that lands in /browser/ | |||
* review policy doesn't have to be exactly the same as firefox's but must be reasonable | |||
* some issues around review were raised in wake of test pilot experience | |||
* questions around mechanics of landing jetpack platform in firefox and landing addons with jetpack platform inside them during transition period | |||
''-> dietrich to identify review concerns based on test pilot post mortem''<br> | |||
''-> dietrich to send a message to working group about mechanics of plan''<br> | |||
''-> myk to figure out where besides these meetings working group discussions should be taking place''<br> | |||
''-> shanec and dascher to figure out who from the various feature teams should participate in these meetings'' | |||
= Actions = | |||
* dietrich to get results from BrowserID performance test runs and post them to BrowserID wiki page | |||
* dietrich to talk to build team about performance test run issues | |||
* someone (dascher?) to figure out who on identity team will be driver for l10n | |||
* myk to report back on the specifics of Jetpack's l10n plan | |||
* myk to identify and propose short-term plan to localize these features | |||
* dietrich to identify review concerns based on test pilot post mortem | |||
* dietrich to send a message to working group about mechanics of plan | |||
* myk to figure out where besides these meetings working group discussions should be taking place | |||
* shanec and dascher to figure out who from the various feature teams should participate in these meetings | |||