AMO/Squeaky/2012-10-09: Difference between revisions

From MozillaWiki
< AMO‎ | Squeaky
Jump to navigation Jump to search
(Created page with "= Meeting Notes for 2012-10-03= ==Attendees== == Agenda == * Lack of engineering resources and the need to prioritize more aggressively. * Babylon update. == Notes ==")
 
No edit summary
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
= Meeting Notes for 2012-10-03=
= Meeting Notes for 2012-10-09=
==Attendees==
==Attendees==
* Jeff Griffiths
* Matthew Grimes
* Kris Maglione
* Tyler Downer
* Jorge Villalobos


== Agenda ==
== Agenda ==
* Lack of engineering resources and the need to prioritize more aggressively.
* Lack of engineering resources and the need to prioritize more aggressively.
* {{bug|799266}} - Malicious Safe Browsing add-on changes id and name.
* Babylon update.
* Babylon update.


== Notes ==
== Notes ==
* Agreement that a short term solution should be to proceed with bug [https://bugzilla.mozilla.org/show_bug.cgi?id=784189 784189].
* Dialogue would appear if any of the settings from [https://github.com/gavinsharp/SearchReset/blob/master/bootstrap.js bootstrap.js] are edited.
* Tentatively shooting for FF 19 or 20 for reset feature
* We will be attempting to use a hotfix update after blocking a medium level add-on. This will be our test case to see if this approach can be used on larger issues.
* Short term solution for Mozilla Safe Browsing would be to hard code the name in the add-ons block list.
== Action Items ==
* Jeff - Reach out to Alex about using the hotfix to address searchqu as a test case.
* Jeff - Talk to Dave Townsend about bug 784189
* Jeff - Talk to Joanne about Yahoo

Latest revision as of 22:52, 16 October 2012

Meeting Notes for 2012-10-09

Attendees

  • Jeff Griffiths
  • Matthew Grimes
  • Kris Maglione
  • Tyler Downer
  • Jorge Villalobos

Agenda

  • Lack of engineering resources and the need to prioritize more aggressively.
  • bug 799266 - Malicious Safe Browsing add-on changes id and name.
  • Babylon update.

Notes

  • Agreement that a short term solution should be to proceed with bug 784189.
  • Dialogue would appear if any of the settings from bootstrap.js are edited.
  • Tentatively shooting for FF 19 or 20 for reset feature
  • We will be attempting to use a hotfix update after blocking a medium level add-on. This will be our test case to see if this approach can be used on larger issues.
  • Short term solution for Mozilla Safe Browsing would be to hard code the name in the add-ons block list.


Action Items

  • Jeff - Reach out to Alex about using the hotfix to address searchqu as a test case.
  • Jeff - Talk to Dave Townsend about bug 784189
  • Jeff - Talk to Joanne about Yahoo