- 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
|Awesome Date||Awesome Person - Awesome thing|
|05/27||Jordan - ?|
|06/03||Erik - Download Module|
|06/10||Gabor - ?|
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);
High Priority Work
No progress this week.
Meeting last week. Tested toolbar module, mostly works, one bug.
Had long discussion about the API, will make changes, hopefully by end of week. The JEP API is no longer up to date - will update it asap.
Review assigned to Mossop for websocket. Ran into issues with local storage. Talking to Gabor this week.
We have definitive lists for which add-ons we could and could not repack. Yesterday we sent out emails to authors whose add-ons we can't repack. We've assigned manual testing to Will, Jeff, Matteo, Erik. Hope to complete this in 2 days, then send out the final mass emails by end of this week. It's later than we had hoped, but progressing.
Audio problems, so no update on this.
Mossop needs more reviews.
Alex has made a platform patch to make this easier, would like feedback - will talk to Irakli.
We have an intern coming in next month (SF-based). Irakli, Jeff, Mossop, DCamp to discuss what to do with him in Friday's meeting.
Jeff: we should delay deprecating until we have a replacement (Fx 25, when people will be able to use a SDK toolbar module). Especially as this will give them review problems, as it will result in warnings being logged. Do warnings cause review problems or just errors? Ask Jorge: if only errors cause problems, then it's OK to start issuing warnings in Firefox 23 (Aurora uplift). Erik will update the toolbarbutton module.
Bug 786681 Cross domain content script flag finally landed!
devtools brainstorm (optional)
What's coming up in Q3? Tools to help add-on developers. Add stuff to the etherpad, go over it in next week's meeting.