Live data from Hacker News

ScyllaDB – Why We're Moving to a Source Available License

scylladb.com

1–10 of 35 posts

Re: ScyllaDB – Why We're Moving to a Source Available License

#4
By now, this kind of open source rug pull is becoming routine. I'm really not sure how I feel about it. I'm thankful for all the free stuff, and I can't fault anyone for trying to make a buck or two.

I'm a huge advocate of free software, but mostly for personal use and individual freedom. So I don't feel like the loss of Scylla is a great loss in that respect. I can't imagine a lot of individuals are harmed by this move.

But still, it makes me distrust corporate "open source" more and more.

Re: ScyllaDB – Why We're Moving to a Source Available License

#6
In reality open source is very difficult to build a business around, which means that software can’t exist long term. It’s not about not wanting to be open source, it’s about realising that you and your employees livelihoods are being abused by people who see open source and take it to mean they shouldn’t pay. Especially egregious when your competitors take your work and build a closed sourced business around it.

Re: ScyllaDB – Why We're Moving to a Source Available License

#8

By now, this kind of open source rug pull is becoming routine. I'm really not sure how I feel about it. I'm thankful for all the free stuff, and I can't fault anyone for trying to make a buck or two. I'm a huge advocate of free software, but mostly for personal use and individual freedom. So I don't feel like the loss of Scylla is a great loss in that respect. I can't imagine a lot of individuals are harmed by this m…

I believe it's the rights assignment that should raise the "a rug pull is inevitable" alarm, not the corporate part

There are plenty of corporate projects that don't require rights assignment to submit changes, just a DCO or even just $(git commit -s)

Post reply on HN