- 1 Agenda
- 2 Awesomeness Schedule
- 3 Bugs
- 4 Attendees
- 5 Minutes
- 5.1 High Priority Work
- 5.2 SDK
- 5.3 Roundtable
- High Priority Work
- API Design
- We should kill all existing intermittents for good or disable them
- We can't really take advantage of being in a tree as much because we test on all trains (rolled over from last week)
- Repacking for Firefox 22: we should plan and start communicating this now.
|Awesome Date||Awesome Person - Awesome thing|
|04/15||Jordan - Places JEP|
|04/22||Eddy - Dutch Mozilla meetup|
|04/29||Erik - Content policies|
|05/06||Mossop - TBD|
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);
High Priority Work
Bug Tree. We're meeting tomorrow to discuss Panel. Ideas for updating panel code have changed from what we had originally planned.
Final patch pushed, backed out, fixed again. Still might be intermittent errors, but will try to push today.
Landed! But needs tests.
We have a JEP: https://github.com/mozilla/addon-sdk/wiki/JEP-Add-on-UI-Integration: Matteo's working the first item, "Toggle/action buttons".
Jordan: working on API design, will blog about it soon.
DOM Window for add-ons
Irakli: has been focusing on private-browsing, so nothing new on this.
Panel has been de-traitified. Still page-mods, widgets, tabs, windows. Erik would like to try to get some of these done.
API Design reading matter
The Mozilla reading group dev-reading is currently reading "The Art of Unix Programming": Erik has been reading this, and it's good (it's at http://safaribooksonline.com ). Jordan: also TrollTech white paper: http://www4.in.tum.de/~blanchet/api-design.pdf.
There is one main intermittent failure at the moment, that Alex thinks might be fixed by a recent patch that we will uplift.
We can't really take advantage of being in a tree as much because we test on all trains
Maybe we can turn off Release and Beta, because we don't expect to uplift to these releases. Discuss this again the next time it's a problem.
Repacking for Firefox 22
We should plan and start communicating this now. Will will write up a plan for what needs to happen, circulate it, and start telling add-on developers.
bug 852240: allow `window.postMessage` to an add-on origin
Proposal to simplify communication with add-on. Comments?