Hey guys In my opinion, maven.org is still owned by a third party (Sonatype). We don't know what kind of data analysis or intelligence extraction they run.
If Ignite servers all over the world were hitting maven.org periodically asking for an Ignite Maven artifact, it gives Sonatype a clear indication of who is running an Ignite server. They could reverse lookup the IP address and find out what corporation it is. How about having Ignite check the ASF Git directly? We could use the Git ssh API, but that would require a new dependency, which I advise against. Alternatively, we could have it scrape this HTML for new Git tags: https://git-wip-us.apache.org/repos/asf?p=ignite.git Another option is to place a txt file in the root of the master branch (e.g LATEST), containing a list of the latest GA versions for each major version line (1.x, 2.x). I would advocate this last option, but it requires somebody remembering to update the file with every release, unless we automate it with a Maven plugin. Hope that helps! On 24 Aug 2017 19:37, "Denis Magda" <dma...@apache.org> wrote: I see nothing wrong with this approach. Cos, Roman, Raul, as Apache veterans, what do you think? Is it good to go? — Denis > On Aug 23, 2017, at 11:17 PM, Dmitriy Setrakyan <dsetrak...@apache.org> wrote: > > Is everyone OK with this approach? Should I file a ticket on it? > > On Mon, Aug 21, 2017 at 2:07 PM, Dmitriy Setrakyan <dsetrak...@apache.org> > wrote: > >> Igniters, >> >> There has been lots of talk of proposals about various usage metrics for >> Ignite and nothing came of it. I would like to resurrect the topic and >> propose something very simple and non-intrusive. >> >> 1. Update Checker >> The main purpose of the update checker is not to collect metrics, but to >> notify users about a new version of Ignite by accessing maven.org and >> getting the version out of the metadata file: >> http://repo2.maven.org/maven2/org/apache/ignite/ignite-core/ >> maven-metadata.xml >> >> This way we do not send any information anywhere and, at the same time, >> urge our users to download and start using the latest version of Ignite. >> >> 2. Startup Counter >> This piece is optional, but we can also get an insight in how many times a >> certain Ignite release gets started. This is just a cool metric for the >> community to gauge the project popularity. You can think of it as of a page >> visit counter shown on many websites. We can even decide to display this >> counter on the Ignite website as well. >> >> To do this, we can simply add a JAR in maven for every release, e.g. >> ignite-start-counter.jar, which will contain only 1 byte. Every time an >> Ignite node starts, it will download this JAR in the background. Then we >> will be able to view the number of the total downloads for this JAR in >> Maven Central, which is essentially the number of starts of Ignite nodes. >> >> *Note that neither of the above suggestions require Ignite to send or >> track any user information whatsoever.* >> >> Please reply suggesting weather you are OK with this approach. >> >> D. >>
