Waze Plugins, rules?, official policy etc.
Hi.
Im currently developing a chrome plugin. (it will be released official shortly, today its in a public beta stage in the Swedish community).
I feel that its strange that there are no official policy and rules, and my feeling when communicating with waze officials is that there is no official rules as long as u don't use non allowed third party information...
But with the post from waze at 2012-11-15, http://www.waze.com/blog/community-buil ... p-editing/
i felt that waze encouraged this kind of contributions.
What i would like to see is,
a clear official policy with rules. (what is allowed, what isent, how to deploy...)
a basic set of functions (a plugin should control the WME version and only load if its a tested version)
a forum part where plugins can be found. (so all can find them easy, and developers can share and help each other, and maybe get some answers from Waze dev)
Dennis
Im currently developing a chrome plugin. (it will be released official shortly, today its in a public beta stage in the Swedish community).
I feel that its strange that there are no official policy and rules, and my feeling when communicating with waze officials is that there is no official rules as long as u don't use non allowed third party information...
But with the post from waze at 2012-11-15, http://www.waze.com/blog/community-buil ... p-editing/
i felt that waze encouraged this kind of contributions.
What i would like to see is,
a clear official policy with rules. (what is allowed, what isent, how to deploy...)
a basic set of functions (a plugin should control the WME version and only load if its a tested version)
a forum part where plugins can be found. (so all can find them easy, and developers can share and help each other, and maybe get some answers from Waze dev)
Dennis
Re: Waze Plugins, rules?, official policy etc.