incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Julian Hyde <>
Subject Re: ASF hosted binaries collecting user data without an explicit opt-in
Date Tue, 06 Jun 2017 02:34:56 GMT
If the binaries are built from the released source code I don’t think we should restrict
what the binaries do. The question is whether the community is aware of what the code is doing,
and considers it to be in the best interests of the project.

The answer seems to be yes, and yes. I saw that the issue was discussed on dev@ignite[1],
and had a corresponding JIRA case[2], and no objections were raised. If anyone has problems
with that behavior (including security bugs) they should raise it with Ignite's PMC.



[2] <>

> On Jun 5, 2017, at 6:48 PM, Roman Shaposhnik <> wrote:
> Hi!
> after seeing this thread on legal-discuss:
> I'd like to ask a policy related question.
> What we currently have is a whole bunch of binaries hosted
> by ASF: that
> collect user data and ship it away to a host currently not
> associated with ASF (nor does it seem to be associated with
> Ignite's PMC). The host name is (and, as a side note,
> as it turns out the connection to that host in Ignite releases prior
> to 1.9 is unsecure:
> )
> Is this something ASF should be concerned with from a standpoint
> of the policy that we have for binary convenience artifacts that are
> hosted on our end?
> Would it make it different if and the data collected
> by it was managed by an Ignite PMC as opposed to an unidentified
> 3d party?
> Thanks,
> Roman.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message