Jetpack/Weekly Meeting/2014-01-21
From MozillaWiki
< Jetpack | Weekly Meeting
Contents
Agenda
- High Priority Work
- Add-on Debugger
- Native Jetpack Support
- node loader changes
- [Slaughterhouse] (needs public bug)
- Devtools SDK
- SDK
- SDK 1.16?
- Blockers?
- Roundtable
- Mentioned in Firefox/Gecko meeting last week:
- "To reduce the impact of add-ons/extensions slowing down browser performance, Google updated its Chrome Web Store policy for extensions requiring that all extensions have a single purpose that is narrow and easy-to-understand."
- What do we do with release notes? bug 952709
- Malware Vendors Buy Chrome Extensions Anything we can do to protect against similar?
- Mentioned in Firefox/Gecko meeting last week:
Bugs
Triage Followups
No results.
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);
Open Bugs
Please see suggestion for x label and legend, if possible in JSON
Attendees
Minutes
High Priority Work
- Add-on Debugger
- there were two bugs, completed patch for one, working on the second.
- JSantell will take over the bugs to get them landed
- Native Jetpack Support
- node loader changes
- not much new, need to write a tool to test.
- [Slaughterhouse] (needs public bug)
- looked at changes on the SDK side, very small
- might need changes in console.jsm, more of a devtool.
- high-level api, ready to land?
- what we need in SDK is already there.
- need to review with Bobby.
- Devtools SDK
- Gozala sent email to react.js people, setting up a meeting in SF.
SDK
- SDK 1.16?
- cannot use new modules with 1.15, cannot build acceptable xpi files with github MASTER
- we should do a new release at the same patch level as Firefox 29 (at uplift )
Blockers
- Zer0 and gozala to chat about UX work after the meeting
Roundtable
- Mentioned in Firefox/Gecko meeting last week:
- "To reduce the impact of add-ons/extensions slowing down browser performance, Google updated its Chrome Web Store policy for extensions requiring that all extensions have a single purpose that is narrow and easy-to-understand."
- very difficult to measure, might tbe possible to isolate JS compartments
- previous attempt with talos was flawed
- discuss more at work week?
- "To reduce the impact of add-ons/extensions slowing down browser performance, Google updated its Chrome Web Store policy for extensions requiring that all extensions have a single purpose that is narrow and easy-to-understand."
- What do we do with release notes? bug 952709
- changelog in the code? ideally included in the PR?
- Malware Vendors Buy Chrome Extensions Anything we can do to protect against similar?
- currently the AMO review process protects us here
- off-AMO malicious add-ons are spread via
crapwareer software installers like Oracle's Java