[Ovmsdev] Fwd: [3-8620000005468] Google Notification to Open Vehicle Monitoring System

Thu Dec 11 20:43:52 HKT 2014

Some apps for ev's have in app subscribtions
so instead of checking them all, they send a message to everyone I guess

easyer also when you do not completely understand the apps ;-)

maybe soon openvehicles code in a google-car?

maybe google has broader plans for google-maps and do not want competition
;-)

2014-12-11 10:43 GMT+01:00 Mark Webb-Johnson <mark at webb-johnson.net>:

> Google getting strict, or just a little fish caught in a bigger net?
>
> Mark
>
> Begin forwarded message:
>
> *From:* maps-api-usage-questions at google.com
> *Date:* 11 December, 2014 3:56:58 pm HKT
> *To:* Mark Webb-Johnson <mark at openvehicles.com>
> *Subject:* *RE: [3-8620000005468] Google Notification to Open Vehicle
> Monitoring System*
>
> Dear Developer,
>
> Thank you very much for sending us additional information about your
> application. After reviewing the information you sent us and looking again
> at the application, it is clear to us that your application is not
> violating the terms we previously mentioned.
>
> We are sorry about the false alarm.
>
> Regards
> Google Maps Team
>
>
>
> On 12/08/14 13:06:06 mark at openvehicles.com wrote:
>
>
> Thank you for your eMail and bringing this issue to our attention.
>
> Our project is a pure open source community project.
>
>
>    - Open Source Repository for vehicle firmware: https://github.com/
>    openvehicles/Open-Vehicle-Monitoring-System/tree/master/vehicle
>    <https://github.com/openvehicles/Open-Vehicle-Monitoring-System/tree/master/vehicle>
>    - Open Source Repository for vehicle hardware: https://github.com/
>    openvehicles/Open-Vehicle-Monitoring-System/tree/master/
>    vehicle/Car%20Module/v2-base
>    <https://github.com/openvehicles/Open-Vehicle-Monitoring-System/tree/master/vehicle/Car+Module/v2-base>
>    - Open Source Repository for server code: https://github.com/
>    openvehicles/Open-Vehicle-Monitoring-System/tree/master/server
>    <https://github.com/openvehicles/Open-Vehicle-Monitoring-System/tree/master/server>
>    - Open Source Repository for iOS App: https://github.com/
>    openvehicles/Open-Vehicle-iOS
>    - Open Source Repository for Android App: https://github.com/
>    openvehicles/Open-Vehicle-Android
>    <https://github.com/openvehicles/Open-Vehicle-Android>
>
>
> We do not charge any fees for our App, and do not charge any fees for our
> service. There is no fee based subscription and no fee based restricted
> access. We do not sell any services, or offer any fleet management facility.
>
> Can you clarify why you think that we are in violation of these terms, as
> from our understanding we are not?
>
> Regards,
> Mark Webb-Johnson
>
> On 8 Dec, 2014, at 3:05 pm, maps-api-usage-questions at google.com wrote:
>
> Dear Developer,
>
> We're happy to see developers interested in our products, however, your
> app, "Open Vehicle Monitoring System
> <https://play.google.com/store/apps/details?id=com.openvehicles.OVMS>",
> violates the following Google Maps APIs terms of service (
> https://developers.google.com/maps/terms).
>
> a) Your app violates clause 9.1.1(a), which states that your application
> must be generally accessible to users without charge and must not require a
> fee-based subscription or other fee-based restricted access. Note that
> mobile apps sold through an app store can be sold for a fee.
>     However, if you charge a subscription for your app, you need a Google
> Maps API for Work license to continue using Google Maps APIs in your app.
>
> b) Your app violates clause 10.2(d)(iii), which does not allow developers
> to use Google Maps APIs for an enterprise dispatch, fleet management or
> asset tracking application without an enterprise license. You must obtain a
> Google Maps API for Work license for your application to continue using
> Google Maps APIs.
>
> Please contact our sales team using this form to obtain a Google Maps API
> for Work license: http://www.google.com/enterprise/mapsearth/.
>
> We’re bringing this to your attention so we can work together to make
> sure your app complies with our terms of service. If you’re not able to
> bring your app into compliance with the terms, we will take action to
> restrict your access to the service. Further, we may request removal of
> your app from all app stores.
>
> Please let us know within the next 14 days that you have updated your app
> to comply with our terms of service. You can respond to this e-mail.
>
> Thanks for your cooperation,
> Google Maps Team
>
> Please contact our sales team using this form to obtain a Google Maps API
> for Work license: http://www.google.com/enterprise/mapsearth/
>
> We’re bringing this to your attention so we can work together to make sure
> your app complies with our terms of service. If you’re not able to bring
> your app into compliance with the terms, we will take action to restrict
> your access to the service. Further, we may request removal of your app
> from all app stores.
>
> Please let us know within the next 14 days that you have updated your app
> to comply with our terms of service. You can respond to this e-mail.
>
> Thanks for your cooperation,
> Google Maps Team
>
>
>
>
> Begin forwarded message:
>
> From: maps-api-usage-questions at google.com
>
> Subject: Google Notification to Open Vehicle Monitoring System
>
> Date: 8 December, 2014 3:05:05 pm HKT
>
> To: support at openvehicles.com
>
>
> Dear Developer,
>
> We're happy to see developers interested in our products, however, your
> app, "Open Vehicle Monitoring System
> <https://play.google.com/store/apps/details?id=com.openvehicles.OVMS>",
> violates the following Google Maps APIs terms of service (
> https://developers.google.com/maps/terms).
>
> a) Your app violates clause 9.1.1(a), which states that your application
> must be generally accessible to users without charge and must not require a
> fee-based subscription or other fee-based restricted access. Note that
> mobile apps sold through an app store can be sold for a fee.
>     However, if you charge a subscription for your app, you need a Google
> Maps API for Work license to continue using Google Maps APIs in your app.
>
> b) Your app violates clause 10.2(d)(iii), which does not allow developers
> to use Google Maps APIs for an enterprise dispatch, fleet management or
> asset tracking application without an enterprise license. You must obtain a
> Google Maps API for Work license for your application to continue using
> Google Maps APIs.
>
> Please contact our sales team using this form to obtain a Google Maps API
> for Work license: http://www.google.com/enterprise/mapsearth/.
>
> We’re bringing this to your attention so we can work together to make
> sure your app complies with our terms of service. If you’re not able to
> bring your app into compliance with the terms, we will take action to
> restrict your access to the service. Further, we may request removal of
> your app from all app stores.
>
> Please let us know within the next 14 days that you have updated your app
> to comply with our terms of service. You can respond to this e-mail.
>
> Thanks for your cooperation,
> Google Maps Team
>
> Please contact our sales team using this form to obtain a Google Maps API
> for Work license: http://www.google.com/enterprise/mapsearth/
>
> We’re bringing this to your attention so we can work together to make sure
> your app complies with our terms of service. If you’re not able to bring
> your app into compliance with the terms, we will take action to restrict
> your access to the service. Further, we may request removal of your app
> from all app stores.
>
> Please let us know within the next 14 days that you have updated your app
> to comply with our terms of service. You can respond to this e-mail.
>
> Thanks for your cooperation,
> Google Maps Team
>
>
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.teslaclub.hk
> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>
>

-- 
http://home.scarlet.be/jcsaintpo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20141211/0b4bdfb4/attachment.htm>