- 1 Agenda
- 2 Awesomeness Schedule
- 3 Bugs
- 4 Attendees
- 5 Minutes
- 5.1 High Priority Work
- 5.2 Roundtable
- Can we set up a bug triage day to identify good first bugs for new contributors?
- Loader question [dcamp]
- SDK on Fennec - fix the tests are failing now before landing new features
|Awesome Date||Awesome Person - Awesome thing|
|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
Panel's are working with private-browsing windows again. This needs to get uplifted.
Platform stuff is done. Alex rebased the patch SDK side, but still some work needed there to finish it off. Mossop will pick someone to own it. It's not that scary, says Gabor.
Matteo added 2 API proposals, with a prototype for one, although we will probably use the other one (the first one here: https://github.com/mozilla/addon-sdk/wiki/JEP-Navbar-Buttons).
Jordan's out today, but will be blogging about this.
DOM Window for add-ons
Irakli sent an email summarizing what we should do here.
The great last repack
Will was incomprehensible, then inaudible.
Progressing: Irakli's hoping to file a patch on de-traitifying tabs soon.
Can we set up a bug triage day to identify good first bugs for new contributors?
Could add a flag in triage for new starters. We can add a link to good first bugs to the weekly blog post, too.
Use the "[good first bug]" whiteboard flag.
An add-on can only load things it knows it will need beforehand. The debugger wants third parties to be able to add things to the loader, which the debugger can't know about in advance. Base loader can load everything, cuddlefish loader enforces the manifest. Debugger can use base loader.