Hi
This seems to be a significant failure in courtesy by the EF.
a) not notifying committers before M7 that this was planned.
b) not notifying committers at M7 that it was in place
c) notifying committers at such a late time that the notification
stinks
d) not giving users a genuine opt-out.
-----
But let's get real.
If Eclipse was a paid for product, users would have to accept
some objectionable Ts & Cs without reading and receive a
unique license id enabling their usage to be tracked. Far worse
than anything Eclipse is proposing even if the UUIDs are cracked
by malware.
Strangely, Eclipse users never accept anything if they only use
an EPP; only additional installs require mindless acceptance of
unread Ts and Cs.
It seems that if we are to continue to treat our users in a
genuinely Open fashion, we must introduce a first usage Ts and Cs
acceptance dialog with an opt-in for anything that even slightly
impinges on privacy. If this cannot be done at a platform-only
RC5, then I feel that it should wait till Neon.1.
I hope the EF will learn from this and treat committers and users
with more respect in future.
Regards
Ed Willink
On 04/06/2016 10:31, Markus Knauer
wrote:
So late in the release cycle?
Without any broader involvement of and verification by the
Eclipse community? Just an announcement after Neon RC3 (or after
Platform RC4)?
Not as an opt-in like in AERI?
Without any further notice to the user at all?
WITHOUT any working opt-out mechanism? Giving the user the
theoretical chance to edit a file and set a property to '0'
cannot be called a valid opt-out option.
And all that from an Open Source organisation?
I believe our users downloading Eclipse deserve more respect.
Silently introducing even more user tracking is nothing that I
want to be identified with.
Markus
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev