Confirmed users
2,595
edits
SeaMonkey/StatusMeetings/2009-12-01: Difference between revisions
Jump to navigation
Jump to search
SeaMonkey/StatusMeetings/2009-12-01 (view source)
Revision as of 13:18, 1 December 2009
, 1 December 2009→Action Items
m (→sgautherie) |
Philip Chee (talk | contribs) |
||
| Line 13: | Line 13: | ||
'''NEW''' | '''NEW''' | ||
* '''KaiRo''' to add to the known issues page additional items from the SeaMonkey 2.0 Final/Feedback section from the previous meeting. | * '''KaiRo''' to add to the known issues page additional items from the SeaMonkey 2.0 Final/Feedback section from the previous meeting. Somebody needs to go through the items and sort out what needs to be added. | ||
* '''Ratty''' to draft out some messages to encourage extension authors to make their extensions compatible with SeaMonkey 2.0. Once the Council approves them, we can forward to AMO for dissemination. The messages should target two groups: | * '''Ratty''' to draft out some messages to encourage extension authors to make their extensions compatible with SeaMonkey 2.0. Once the Council approves them, we can forward to AMO for dissemination. The messages should target two groups: | ||
** Existing SeaMonkey extensions that haven't been upgraded to 2.0. | ** Existing SeaMonkey extensions that haven't been upgraded to 2.0. | ||
** Firefox and Thunderbird extension authors encouraging them to make their extensions compatible with SeaMonkey 2.0. | ** Firefox and Thunderbird extension authors encouraging them to make their extensions compatible with SeaMonkey 2.0. | ||
** Ratty filed AMO {{Bug|527919}} for this. Once the messages are approved, they should be forwarded to AMO and they will take care of sending these out to extension developers. | ** Ratty filed AMO {{Bug|527919}} for this and attached some drafts. Once the messages are approved, they should be forwarded to AMO and they will take care of sending these out to extension developers. | ||
'''OPEN''' | '''OPEN''' | ||
* Get permission from Google to use their geolocation JSON service '''[KaiRo]'''. Contact at Google says: "We don't have a good estimate for when GLS will be opening up more broadly, but I will be sure to let you know when we take that step. Sorry that I can not be more specific at this time." - We can only wait right now. | * Get permission from Google to use their geolocation JSON service '''[KaiRo]'''. Contact at Google says: "We don't have a good estimate for when GLS will be opening up more broadly, but I will be sure to let you know when we take that step. Sorry that I can not be more specific at this time." - We can only wait right now. | ||
** KaiRo emailed Google again more than 8 weeks ago and again 5 weeks ago, no reply yet, even though the MoCo geolocation contact has poked the Google contact as well. | ** KaiRo emailed Google again more than 8 weeks ago and again 5 weeks ago, no reply yet, even though the MoCo geolocation contact has poked the Google contact as well. | ||
** KaiRo will try to get this process restarted. | |||
'''CLOSED''' | '''CLOSED''' | ||