Cordova uses the npm package `insight` for telemetry, you can see more in these two files: https://github.com/apache/cordova-cli/blob/master/src/telemetry.js https://github.com/apache/cordova-cli/blob/master/src/cli.js The data being tracked is very limited, and all done only after explicit opt-in by the user. (You get a prompt when you first install Cordova). The dashboard itself is built on the Google Analytics data source that collects the data for pretty graphs.
One problem: I am under the impression that Google Analytics is blocked for good parts of Chinese users, so Cordova's data regarding usage in China is probably very broken. -J Am Mo., 18. Feb. 2019 um 08:29 Uhr schrieb Dan <faterr...@gmail.com>: > > Hi Jan, > > Thanks for getting back to me. > > Your opinion has helped us a lot. We will migrate the deployment of the > document to weex.apache.org in these two days. > > BTW, do you know the detail about how to do the user-track bellow the > apache way, I know the Cordova has telemetry.cordova.io to record it, and > we also want to record the user's behavior in the weex-toolkit to help us > better improve the tool experience. > > Thanks, > Dan > > Jan Piotrowski <piotrow...@gmail.com> 于2019年2月15日周五 下午7:42写道： > > > Besides what the rules say (which I don't really know): > > > > An apache.org domain has an incredible effect on credibility and > > trust. Apache is a really strong brand with developers, and especially > > new projects like Weex can benefit from that. > > > > (The project will be called "Apache Weex" anyway) > > > > Apache Cordova owns the cordova.io domain and uses it as a redirect to > > cordova.apache.org. That way we can still tell people to go to > > "cordova.io", but on Google and in user's browser everything happens > > on apache.cordova.org. We also have loads of subdomains like > > blog.cordova.io issues.cordova.io, slack.cordova.io, > > telemetry.cordova.io and so on as shortcuts which is very handy. > > > > Using the domains you mentioned, weex.io could redirect to > > weex.apache.org, docs.weex.io redirects to weex.apache.org/docs, > > blog.weex.io to weex.apache.org/blog and so on. Then cn.weex.io could > > redirect to weex-project.io for easier finding of the Chinese domain. > > > > -J > > > > > > > > > > > > > > > > > On 15. Feb 2019, at 07:38, Dan <faterr...@gmail.com> wrote: > > > > > > Hi, Myrle/Willem, > > > > > > Currently, we have a domain name of weex.io and want to use it to > > replace > > > the previous weex-project.io domain name for the following reasons: > > > > > > 1. The domain name is shorter and easier to remember. > > > 2. Apache's website has slower access to the developer in China, so there > > > is a mirror website weex-project.io for Chinese developer. > > > 3. We expect to support https on this website and support some of our own > > > server functions, such as Q&A robots, article blog posts, etc. > > > > > > I would like to ask if apache has any restrictions on this third-party > > > domain name, and look forward to hearing from you. > > > > > > Thanks, > > > Dan > >
