mikemcquaid

6 ms·

61.
by mikemcquaid 5mo ago
I'd personally got specific contract carveouts for this to only apply e.g. during working hours on company equipment (or even more liberal). The GitHub liberal IP agreement is a good example of being even more chill here.
62.
by mikemcquaid 5mo ago
Author here. I've maintained Homebrew since 2009. This manifesto is for the maintainers I know who have quietly built a sustainable OSS practice inside companies that directly or indirectly depend on their work. I'm also at the po
63.
Open Source Resistance: keep OSS alive on company time(ossresistance.com)
275 points by mikemcquaid 5mo ago|85 comments
64.
by mikemcquaid 7mo ago
Correct. Max created it in 2009. I joined a few months later. I've only maintained it for 17 years.
65.
by mikemcquaid 7mo ago
Indeed, everyone's free to do what they want, that's the beauty of open source. I have zero issues with people vibe coding alternative Homebrew frontends, it's good for the ecosystem for there to be more experimentation. What
66.
by mikemcquaid 7mo ago
We will never be 100% Rust an 0% Ruby. It’s possible that 99% of users end up never running any Ruby, though. It’ll still be needed for local development and our CI. We’re optimising for speeding up the 99% case as much as possible.
67.
by mikemcquaid 7mo ago
If it doesn’t ever execute Ruby: it cannot be compatible with Homebrew. “Compatible” is doing a bit of work here when it also means “implicitly relies on Homebrew’s CDN, CI, packaging infrastructure and maintainers who keep all this running
68.
Homebrew 5.1.0(brew.sh)
7 points by mikemcquaid 7mo ago|1 comments
69.
by mikemcquaid 7mo ago
Homebrew 5.1.0 has been released. Homebrew's most significant changes since 5.0.0 are expanded `brew bundle` support, `brew version-install`, new `-full` formula handling and installer updates.
70.
by mikemcquaid 7mo ago
Yeh I came here to post this. I preferred this approach as user permissions are a bit easier to consistently verify as a second layer of defence. I also found the author to be helpful and responsive and the tool to be nicely minimalistic ra
71.
by mikemcquaid 10mo ago
I did not reread the whole thread before replying and should have done that at which point I would have seen your apology. I apologise for not doing that. Good on you for apologising. I will ignore more in future.
72.
by mikemcquaid 10mo ago
You will find many examples of me apologising and changing on Homebrew’s issue tracker, they just tend to not be the cases that people decide to bring up here. It’s unsurprising to me that 16 years of working on Homebrew most days has a bun
73.
by mikemcquaid 10mo ago
If multiple people are assuming bad faith: perhaps you should adjust your communication in future rather than trying to change their mind. An apology wouldn’t hurt, either.
74.
by mikemcquaid 10mo ago
Don’t. It’s a cool idea and vibe coding it doesn’t make it less interesting. You don’t owe anyone anything and the mean behaviour you’re in receipt of says more about them than you.
75.
by mikemcquaid 11mo ago
If you love Homebrew, maybe you might want to consider if repeatedly calling me a dick or arrogant/blunt is a particularly nice way to treat someone who spends their spare time building software you rely on.
76.
by mikemcquaid 11mo ago
With how Homebrew manages issues: debates about this belong in Homebrew/discussions, not on the issue tracker. That's why they get locked.
77.
by mikemcquaid 11mo ago
> You could have just said this Yup, you're right, I should have. We will adjust the CONTRIBUTING.md accordingly. > If this was true every oss project would either be dead or be entirely comprised of dicks, neither of which are t
78.
by mikemcquaid 11mo ago
I don't think I am a dick, I guess that went without saying. I'll take critique from other maintainers who have done as much or more open source work for similar returns over similar time periods. Funnily enough, I'm friends
79.
by mikemcquaid 11mo ago
There's a misunderstanding here what the issue tracker is for in Homebrew. In some projects, it's for free-for-all discussion. That's great if those projects want to use it that way. In this issue's case, you have someon
80.
by mikemcquaid 11mo ago
Homebrew Project Leader here. Yes, this only affects casks, not formulae, whether formulae are built from source or use Homebrew's bottles (binary packages) or bottles from taps.
81.
by mikemcquaid 11mo ago
Yes, active support dropped for macOS Intel September 26, won’t work at all on macOS Intel September 27. We’d love to support everything indefinitely but lack the resources as a volunteer run open source project to do so, particularly when
82.
by mikemcquaid 11mo ago
No(t yet). It's a slimmer version of the existing JSON API that's similarly only used by homebrew/core and homebrew/cask for now, mainly because they are so huge that using Git for this had very poor performance.
83.
by mikemcquaid 11mo ago
Homebrew Project Leader here. Happy to answer any questions.
84.
by mikemcquaid 1y ago
Sort of? The Glaswegian taxi driver may not consider themself to be speaking a different language but, if speaking to another local and leaving aside pronunciation, they’d use words, phrases and even grammar that’s incomprehensible to someo
85.
by mikemcquaid 1y ago
As someone who spent a bunch of time talking before and after this all went down with current and past RubyGems maintainers, RubyCentral employees, Gem.coop maintainers and Ruby Core folks: this seems like the best outcome that was actually
86.
Analysing RubyGems Contribution Data with Homebrew's Tooling(mikemcquaid.com)
4 points by mikemcquaid 1y ago|1 comments
87.
by mikemcquaid 1y ago
Lots of RubyGems chat recently, very little data. I've used Homebrew's tooling to analyse RubyGems public GitHub data and posted it here.
88.
by mikemcquaid 1y ago
You can't tell if someone is "native British" by looking at them. There's records of non-white British citizens with voting rights back to 1749. Are those people's great-great * whatever grandchildren not British if
89.
by mikemcquaid 1y ago
I’m the Homebrew Project leader and care a lot about Ruby so met with both sides to attempt to mediate and posted two threads on Bluesky about what went down: https://bsky.app/profile/mikemcquaid.com/post/3lz7
90.
by mikemcquaid 1y ago
Parting of ways? Sure. In this case they are in charge of the package index but have removed most maintainers from their projects, implicitly taking charge there too. This is a problem.

More ›