_msw_

Joined 9 years ago

Karma
696
Submissions
235
Member since
Nov 7
Socio-technical systems engineering at Amazon. Opinions are my own.

msw at amazon dot com

https://twitter.com/_msw_/

[ my public key: https://keybase.io/msw; my proof: https://keybase.io/msw/sigs/uK93UzjUgwYQWn0RIoE4Vq3Emdm5tMxur2CssTtmqk0 ]

View on Hacker News

Recent submissions

Comment · 1 year ago
Yeah, that really grinds my gears too.

It especially bugs me when company blogs call out “abuse” when they only exist as a company because others gave them the permissions needed to build a business on software they did not author themselves!

Comment · 1 year ago
Comment · 1 year ago
Comment · 1 year ago
Comment · 1 year ago
Comment · 1 year ago
Disclaimer: I am not a lawyer, this is not legal advice.

In theory, one would not be able to offer a combined program under other licenses (in particular, RSALv2 and SSPLv1), as those licenses have conflicts with GPL obligations.

Direct contributions to the Redis project avoid this issue via a separate Contributor License Agreement. It would only mean that Redis developers could not unilaterally copy code from Valkey.

I'm not saying that the Valkey community should do this. Personally, I think it's better off as a BSD-3 licensed project, with the community fulfilling the promise made by others that it would always be that way.

Comment · 1 year ago
Comment · 1 year ago
Comment · 1 year ago
Comment · 1 year ago
Comment · 1 year ago
My personal opinion: we shouldn't let Google's bad policy poison our brains. The people who wrote that policy had their reasons for taking this position. It might have been the right thing for Google at the time the policy was written.

That doesn't mean it's the right position for you, or for every situation. Many organizations with a higher levels of maturity in open source matters will take a more nuanced approach when it comes to AGPLv3 licensed software.

Comment · 1 year ago
Disclosure: I work for Amazon.

AWS never offered a service based on the AGPLv3 version of the MongoDB server. Therefore the change of license terms to SSPLv1 was not directly caused by Amazon’s use of the software as part of an offered service, and had no impact to Amazon DocumentDB as an independently developed interoperable protocol implementation.

There were cloud providers headquartered in Asia that did offer AGPLv3 based MongoDB server as a service.

Comment · 2 years ago
> PS: There are exceptions like postgres but there aren't enough of them at that scale.

We need more communities and projects like PostgreSQL. Why can’t Valkey be another one?

Comment · 2 years ago
There is more Free Software produced today than ever before, even if some firms are deciding they no longer want to produce it. There are far more who are continuing to add to the commons of public software unnoticed; those who publicly quit get far more attention.

I’m all about increasing the private provision of public goods. I don’t think that licenses that give firms exclusive rights to monetize the goods they produce advances that goal. That’s just the status quo of firms being landlords of their intellectual property, extracting rents from others who want to enjoy them. That’s just proprietary software, which is clearly a useful thing for society to have.

The thing that leaves a bitter taste in the mouth is when you apply your resources to produce common goods, and then one party declares that you are somehow a “bad actor” while changing the terms to enclose the goods and exclude you from enjoying that common good.

Luckily with FOSS, those who are excluded can move their efforts elsewhere. But the future goods will not be the same. And I think that’s a shame.

Comment · 2 years ago

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton