ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Roman Shaposhnik <...@apache.org>
Subject Lack of accounting for extremely disruptive functionality
Date Tue, 06 Jun 2017 01:27:07 GMT
Hi!

there's a thread about an extremely questionable practice
that Apache Ignite engages in. A practice that borderlines
on unsolicited data collection (and as such may even be
illegal in some jurisdictions without an explicit opt-in):
    https://mail-archives.apache.org/mod_mbox/www-legal-discuss/201706.mbox/%3CCAGJoAUn-hiE89mWObh1Lb2S_vgqQJ%3DDC%3D1P_V1REQ9hUERCFog%40mail.gmail.com%3E

This thread, however, is not focused on the legality (IANAL) of
the practice nor it is focused on security implications of it. I'd live
to talk about an absolute lack of any accounting for an extremely
disruptive functionality like this one.

Because you see, when I asked myself a question "how the heck
could something like this possible end up in a project with
virtually 0 discussion that I remember?" My next thought was -- well
let me use Git and JIRA to get to the bottom of this. Quite to
my surprise every single commit that touches the URL in question
has virtually 0 accounting for why it is there. No JIRA IDs, not extended
comments -- nothing.

My understanding is that you guys pride yourself on being RTC project.
Can someone please explain to me how all of these got reviewed:
 https://github.com/apache/ignite/commit/952be8b995050b34379006dd6e739da3fe3b49e3
 https://github.com/apache/ignite/commit/33ec73f901ca5dba441c6ca4e118d55165f3d25e
 https://github.com/apache/ignite/commit/551b3d1eab2a0b78d3f259f1bf24f1f6f3ff7b06
 https://github.com/apache/ignite/commit/c4030f926a7339cfcae14e19cec22d9d37cd94dd
 https://github.com/apache/ignite/commit/73c5e43c6c161aa18aa9e8ff2b09e582c7aedce4

Thanks,
Roman.

Mime
View raw message