If things you don't like happen with a project, start a dialogue, fork it, or use something else instead. Don't just wade in making threats.
(Sadly, this has been going on for a very long time: I remember the debacle over .NET 2.0 support in NDoc where the author had some difficult personal circumstances coupled with people constantly hurling abuse at him. Net result: he understandably quit, not just NDoc but all OSS involvement, nobody else wanted to pick up the project, and the project died. This must have been 11 years ago now but it seems like, since then, the problem has if anything become worse.)
As a long-term homebrew user, I am very appreciative of your hard work (and have even contributed here and there), but in that light I am also very disappointed that I have to manually disable analytics and now have a lot less trust in the homebrew project.
In the same way that I would complain if I were to see a bug in your code that radically effects my production, I consider this invasion of privacy - whatever the justification - worthy of complaint, too. Whatever the justification for this, its not an acceptable path to take, and I strongly urge you to consider making Analytics opt-in, and not opt-out. I have no problem with my next 'brew update' pausing, explaining the situation rationally as you have in this post, and giving me a y/n opportunity to proceed with participating in analytics. I do have a serious problem with you assuming that this is okay, not informing me of it in a fashion that makes me aware of the tracking, and just letting it slip in during an update, which I am now even more suspicious of, even though I do them religiously every week, and have done so for years.
You've just made your product less attractive to me as a developer and user. That's a sad state of affairs, and I hope you fix this bug.
Exactly this. The homebrew team has done an amazing job for the past 7 years, all free and volunteer work. People threatening with suing the maintainer are poison for the open-source community. But hey, haters gonna hate.
If I understand correctly, the data is anonymized before it is sent to Google [1]. How may people worrying about privacy download from Github using a proxy/vpn solution to hide their IP?
I've listened to the Changelog podcast about Homebrew and first learned about Google Analytics there. I think people do not realize how big homebrew is (in form of usage and traffic). At this scale, the maintainer opted for collecting data anonymously in order to find bottlenecks and improving the entire software stack. You can disable that feature in the same way you would disable cookies in your web browser.
[1]: https://github.com/Homebrew/brew/blob/master/docs/Analytics....
From a happy and grateful Homebrew user, thank you for all the work you are doing. It's really easy for folks to underestimate how much effort is involved in running a project like this. Details like the above should be a reminder that it's clearly a very significant amount of hard, sometimes thankless, work; work which you are in no way obligated to do. There are large numbers of people who owe you a massive debt of gratitude for all the time and hassle that your effort has saved them. And it's quite sad that we (people) tend not to speak up when we are happy, and only make noise when we're upset about something.
Thanks for continuing to work on this project!!
On the other hand it was likewise surprising to hear that homebrew was using github as its CDN.
I don't rely on homebrew to do anything, but I am concerned about the normalisation of surveilance and will point that out in a reasonably polite manner.
That sounds a bit weird to me. Homebrew gets developed on GitHub... so using GitHub as a CDN doesn't seem wrong (to me).
Sounds like they weren't using GitHub's Releases approach for binaries, instead doing something else. :/
Homebrew is excellent software, and the malice expressed in this and similar threads does in no way reflect (my) real world experience of people's perception of Homebrew. I would go so far to say it's probably the best piece of software that I know, it's really easy to use, always works and helpful if something goes wrong. Good software is pretty rare to find, especially open source software with no commercial backing.
I think that giving up on user's privacy is not an acceptable solution. If you don't have enough time to fix all the bugs and nobody is willing to help then nothing can be done.
What I expect from open source software is that an application should not collect and send home any data by default (I understand that it is not written in the license but still expect this). Breaking this expectation makes me and maybe not only me a little disappointed.
As we're not providing information to any commercial company or selling it I don't think this is a reasonable comparison. If we were collecting information to sell and raise funds for the project I'd object to that, too.
The fact that Homebrew uses Google Analytics means that it provides Google with more data, even if you don't hand that data over to other companies after the fact.
> It uses a randomly generated UUID that you can change at any time and we request IPs be anonymised using the documented method...
You already have a UUID. Why give Google the IP at all? Of course, I don't understand your desperate need for "analytics" unless it's a need for approval. Why can't you take all the blog posts talking about "brew" as approval enough?
Keep up the good work.
I also completely understand the need for default opt-in. I probably wouldn't check the prompt and leave the default, but for a project like this, I honestly don't mind sending usage data.
If you're not happy with the direction taken by the maintainers, find another tool.
So to answer your question, the status of the project and his personal affairs have a huge impact on design decisions.
Priority isn't a design decision.
Analytics help, but the choice to not opt-in is not excused by "but we need them"
I'm just saying that you're putting yourself on risky ground, not that I want to do something personally.
In fact I'd even consider keeping GA enabled IF BEING NOTIFIED.
The current notification is the problem, as it is close to invisble. Hiding output in a long log message is a dark pattern, I think it did not happen out of spite (you just used your normal shell output mechanism to show that).
However: Such a chage of policy is more important than the list of files being removed by git. Even opt out is OK IF THE USER IS INFORMED.
Currently it's like arthur dent being informed about the highway being built ... yeah we did display the notice.
I know building an open source project is no fun and I can really relate to your desire to know more about installations and deinstallations. Personally I don't even object to using google GA, just to the way it feels being snuck beside the radar.
That said, I still don't appreciate threats or ideas to sue me as an individual. That's a massively disproportionate threat to me and my family.
This certainly sounds like you're advocating for people to - at the very least - harass him.
Homebrew lead maintainer here. We're chronically understaffed and underfunded. We have analytics so we can make Homebrew better by figuring out how to prioritise security, maintenance and bug fixes on packages based on how much they are used and how often they fail. I've been working on making regular dumps of this data and have been trying to find people who will provide us with non-Google hosting but: we're chronically understaffed and underfunded.
One of our CI machines burnt out last night so I'm now trying to plan vacation time to drive for a 14 hour round trip and pick it up. While I'm doing that someone points out there's someone on Hacker News threatening to sue me. This is for working on software (mostly) in my free time that's used by people (mostly) for their employment and obtained for free. After the last thread on this (https://news.ycombinator.com/item?id=11566720) I had people emailing me to tell me I'm a nazi and should kill myself for weeks.
Everyone here who objects to the analytics is well within their rights to do so (and should either opt-out or stop using Homebrew) but we need to start asking ourselves as a community whether we think treating open-source maintainers like this is more or less likely to encourage more people to work on the open-source software you rely on to do your job.