Makes sense to me. I would love to know which components/APIs are used more
than others. Obviously, we should make sure everything is anonymous and we
don't collect any private user data, but I believe this is already
guaranteed by Google Analytics.
-Val
On Tue, Nov 3, 2020 at 3:59 AM Alexey Gonc
Folks,
I want to bump up this discussion and slightly change the format suggested
by Nikita. I dot think it is correct to gather any information related to
the user environment. However, can we collect just the fact of some of the
Ignite APIs/subsystems being used with no user information whatsoev
I would try to ping legal again and see if they respond. If not, I think we
will need to come up with a simpler approach, that does not require legal
approval.
D.
On Jul 18, 2017, 2:23 PM, at 2:23 PM, Nikita Ivanov wrote:
>Igniters,
>Just a quick update. I haven't gotten response from ASF Le
Igniters,
Just a quick update. I haven't gotten response from ASF Legal on this
thread and I frankly don't know how to proceed here. What's the process to
arrive to a decision point here?
Thanks!
--
Nikita Ivanov
On Mon, Jul 10, 2017 at 3:11 PM, Konstantin Boudnik wrote:
> On Sat, Jul 08, 2017
On Sat, Jul 08, 2017 at 11:04AM, Nikita Ivanov wrote:
> Cos,
> Based on my experience having it off by default negates the entire
> purpose... We need statistically meaningful data set to make any inferences
> from it. Moreover, if we are going to ask folks to turn it on it will
> significantly ske
Cos,
Based on my experience having it off by default negates the entire
purpose... We need statistically meaningful data set to make any inferences
from it. Moreover, if we are going to ask folks to turn it on it will
significantly skew the resulting data set anyways and show full picture. I
think
Actually, that should be OFF by default. It sounds like this reduce the amount
of the data collected, but this would address the concerns of companies like
Roman's. I know for sure that a few of my clients would sue my ass out of
existence if I gave them the platform collecting their data-centers i
The idea so far is to have a single system property in configuration that
turns this off completely. I envision that this will be prominently
featured on Ignite website so that everyone who would like to disable it -
can do it in seconds.
Thoughts?
--
Nikita Ivanov
Founder & CTO
GridGain Systems
Nikita,
Sending and storing (somewhere the company cannot securely handle) any
information (OS version, IP addresses, etc.) that can be used to compromise the
services would be unacceptable.
Turning it off might be ok (possibly through the cluster settings, not via
globally-accessible site), but
With such statistics collected by Ignite , we won't ever accept ignite in our
environment.
However, turning on and off stats collection capabilities would be helpful here
if the feature is accepted further for implementation.
Take Care,
Rishi
> On Jul 5, 2017, at 8:15 PM, Roman Shtykh wrote:
Roman,
Thanks for the feedback. What are those questions specifically? Are IP
addresses and OS is what causing it?
Thanks!
--
Nikita Ivanov
Founder & CTO
GridGain Systems
On Wed, Jul 5, 2017 at 6:15 PM, Roman Shtykh
wrote:
> NIkita,
>
> While this will help improve Ignite, it will prevent its
NIkita,
While this will help improve Ignite, it will prevent its adoption by many
projects -- sending and retaining IP adresses, OS versions, etc. raises tons of
questions when considering to use Ignite. Even if it can be opted out.
-- Roman
On Thursday, July 6, 2017 5:38 AM, Nikita Ivanov
12 matches
Mail list logo
