Let's connect real weather service to weather widget and get rid of current stubs. By default we are going to have Yahoo! widget for it.

I'm now working on connecting to Yahoo weather API. But I'm not sure our policy on using external APIs. Howie or Joe do you have any idea to find someone confirming about this (maybe legal?) issue?

Hi Gervase, could you guide us for Comment 1 here? Thanks!

:howie: I don't think this is a question for me. I don't think there's any policy against Gaia apps downloading data from external services. Of course, the Mozilla-y way to do a weather widget would be to have multiple providers available, and an open API. If you are going to use Yahoo!, probably best to bring in someone from the biz dev team work works on our Yahoo! relationship, to make sure there won't be a problem here. Gerv

Hi Charles, do you know anyone from BD that works on Yahoo! relationship? Thanks.

Hi Howie, I have checked and linked you with Joanne, she is our main contact for Yahoo She has sent you some quesitons via e-mail, please help to answer that BRs Charles Chen

Hi Howie & Charles, Doing a quick search of the Yahoo Developer Network, shows that the Weather App has Rate limits: Rate Limits Use of the Yahoo Weather API should not exceed reasonable request volume. Access is limited to 2,000 signed calls per day. The terms of use indicate that this API is for individuals and non-profits and are limited by the rates I referenced. Here's the link to their site: https://developer.yahoo.com/weather/ In order to have a conversation with the appropriate Yahoo team, it would be helpful to understand what volumes of usage you anticipate - possibly on a quarterly basis as you expect usage to ramp up? Let me know how you want to proceed. Thanks, Joanne

Sorry, we got some re-discussion on the spec recently with UX. We would still need to use the API, but let me postpone for a few days before confirming the use case.

Hi KM, In this case should I still file another bug to check the legal related topics with Yahoo Weather? Or should I wait until you have final proposal? BRs Charles Chen

Well, after some syncing, I can try to give the answer now. Each TV would need to do about 3 to 6 requests per hour if it's turned on. So if we assume it's turned on 8 hours a day, it sends about 24 to 48 requests per day. In short term, we would just use it on our reference branch (master), which would be used just by developers. If we have partners that release their own products later, they may require to request API by themselves. Does it help on estimating the amount of use? Oh, and I have one question... Not sure if it's a legal issue. If we need the API key/token/ or something to use the API, would it be ok to put the key inside our open-sourced repository? I'm OK to open another bug for these issues unrelated to implementation. Thank you!

Hi KM, Based on your assumption each TV needs around 50 pins. Yahoo's Rate Limits says below: Use of the Yahoo Weather API should not exceed reasonable request volume. Access is limited to 2,000 signed calls per day. It also need to be personal or non-profit. So if we limit to internal developers and no more than 50 developers/devices use this API, it should be okay to just use it (following the instruction and requirements Yahoo mentioned). If someday we will have more than 50 developers/devices or we will use it for commercial purpose, we need to check with Yahoo

Firefox OS is not being worked on