SeaMonkey/StatusMeetings/2017-04-23: Difference between revisions

SeaMonkey/StatusMeetings/2017-04-23 (view source)

Revision as of 17:15, 22 April 2017

214 bytes added , 22 April 2017

→‎Action Items: items done

Frg

647

edits

@@ Line 21: / Line 21: @@
 * &mdash;
 '''OPEN'''
-* Something needs to be done about the lack of developers and support staff or SeaMonkey will be no more in the near future. '''frg''' will prepare an "asking for help" draft for the council. When final it will be posted in the various SeaMonkey newsgroups.
+* Something needs to be done about the lack of developers and support staff or SeaMonkey will be no more in the near future. '''frg''' did prepare a "asking for help" draft for the council. He is waiting for final comments and will be post it in the various SeaMonkey newsgroups. Some users are willing to proof-read and translate to other languages before it goes out.
 * Mozilla plans to check in l20n. Unclear what this means for comm-central and the current l10n build configs. Needs to be monitored.
 ** {{bug|1107635}} - Rewrite build system l10n repack rules from Makefile rules into a Python script might also affect a timely l10n repack
-* Google announced V4 of the safebrowsing api. Firefox adds support for it in {{bug|1167038}}.
-** In 2.51+ additional preferences are needed. The blocklist interface will also be changed. You now see errors in a new 2.51 profile. No bug has been filed for this as of now.
 * Google API key for Safe Browsing. Ewong/Callek about getting it loaded onto the build machines.
-** Per {{bug|903439#c10}}, ewong confirmed that he has the Google API key. Safe Browsing keys are on the builders according to ewong. The build config config changes are not yet checked in. Ewong contacted Mozilla for a geolocation key. The Google API key can be used instead of the Mozilla key with some pref changes. rsx11m will open a bug to use the Google key for now in all trees ({{bug|1352850}} created after meeting).
+** Per {{bug|903439#c10}}, ewong confirmed that he has the Google API key. Safe Browsing keys are on the builders according to ewong. The build config config changes are not yet checked in. Ewong contacted Mozilla for a geolocation key and so far received no response. The Google API key can be used instead of the Mozilla key with some pref changes. rsx11m fixed a bug to use the Google key for now in all trees {{bug|1352850}}.
 * '''IanN''' has spoken to mcsmurf about members list. Members mailing-list and council appointments are ready to be reviewed.
 ** TODO: Add Adrian Kalla to RelEng team. Overall no change as of today
@@ Line 45: / Line 43: @@
 * &mdash;
 '''CLOSED'''
+* Google announced V4 of the safebrowsing api. Firefox adds support for it in {{bug|1167038}} which is now mostly fixed. I think the part can be removed for now.
+** Works in SeaMonkey. No additional preferences are needed but for the V4 lists the Googgle API key needs to be on the server. The initial blocklists (unrelated item) were taken care of in {{bug|1358750}}.
 * &mdash;