Adam Jacob Profile picture
6 Dec, 14 tweets, 3 min read
This misses the point wildly. There aren’t different understandings of what open source means. There are people who want what they want. If they still can get it, they’re usually fine with whatever.
That’s why we buy software, use Twitter, whatever. Most of us aren’t open source zealots. We’re just people with a job to do.
So it’s not surprise to me that a bulk of @graylog2 users, especially customers, are fine with this. They’re not in the class of user who is affected!
This is why I think it’s a bad move to muddy the waters here. Adopting the SSPL is a business choice. Combined with a CLA that grants only them the privileges to relicense the whole, they can build derivative works that exceed the SSPL, but others cannot.
That means any SaaS biz not run by them is dead. That clears the way for them! Which is fine. It’s your business! Go for it.
But it isn’t open source anymore. Not because of the CLA, but because the mechanism they’re using isn’t an open source license. Mongo tried to make it one and withdrew before being rejected.
But it’s the same move they made. Lots of independent MongoDB saas offerings. Wiped out or acquired by MongoDB. This is the same move. It’s a rejection of open source in order to ensure a revenue stream.
A rejection that’s easily accepted by their customers (already paying, still get the code). Developers who don’t like the new contract can be painted as difficult. Businesses that are harmed, we’ll - that was the point.
But ultimately, open source is a vital part of the modern internet. It’s values and definition drove its success. When we let people define it “how it means to me”, we’re weakening it deeply. It’s not about just you. Never has been.
If you want to adopt a non open source license for your business, go for it. That can be a good decision (although I think the opposite is almost always better strategically, but I might be a hippie).
But come at the very community norms that fostered you? So you can have just a little more air cover? Get the fuck out of here.
That’s why what they need to do is stand by their choices. Say it proudly! We invest millions into @graylog2. We give you the source. We need revenue to continue that investment. The deal is only we get to run that SaaS stream for profit and keep the source closed.
Because that’s how you get this great thing for free. A lot of users are going to be fine with it. Some won’t. You don’t care about those users though, or you wouldn’t have changed the license!
Instead you do all that *and* weaken the foundation of open source. Yucky 💩. Don’t do it. Have some principles. Lead.

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Adam Jacob

Adam Jacob Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @adamhjk

6 Dec
When you think you get to define what an important software term means, because you want to retain an advantage - I don’t care what you believe. Just because you say the sky is purple doesn’t make it so. Gross. Do better, @graylog2.
To be clear - like it or not, open source is defined by OSI. As a community we rely on it. We need it, so we can trust what liberties it grants. I’m on the side of there being a more open discussion - but just saying “we think it’s okay” is some bullshit.
You know it’s not. You wanted the non-compete part of the license more than you cared about it being open source. Own that shit. Stand up for your principles.
Read 5 tweets
3 Dec
@webframp Ok! Basics first. F1 is a constructors sport. Each team must build its own car, from scratch. They can use listed parts, outsource some, but the design and build has to be done in house by the team.
@webframp That means the team often can build the car around the driver. They give feedback on how it feels and behaves, and the teams change and adapt over time. It also means each teams car is unique to the team.
@webframp The cars themselves have no driver aides allowed. No power steering. No traction control. If you’ve ever driven a rear wheel drive sports car with no assists, I’ll tell you: it’s difficult. You have to pay maximum attention all the time. They’re absolute monster cars.
Read 25 tweets
2 Dec
There is a market opportunity for an alternative to k8s. You won’t “beat” it, but you don’t have to. You just have to decide to compete. Right now nobody even tries. Nomad is closest, and even their marketing is complimentary at heart.
To be clear - I’m not building one
Also, it’s not because k8s is bad. It’s because it’s such a success, the groundwork for the market is laid. People don’t question its place in the stack. They do question the implementation complexity. Operability.
Read 5 tweets
9 Sep
I haven't used Fluid, but I just devoured all the info on it, and I want to share why I think it should be a game changer for most of us.
First - doing large scale collaborative state transitions is really hard if you want it to feel fast. The number of different factors at play range from the low-level wire protocol to the high level application design. It all has to be right, or you get very hard bugs.
Until now, I suspect most everyone wound up taking either the Operational Transform route or the CRDT route. What Microsoft did here was cleverly different (unique? certainly to me, and I've done a lot of reading and implementing here)
Read 9 tweets
7 May
For people wondering if switching to the red hat model has worked for chef - super yes. It’s for others to give details, but I wouldn’t do the open core model again, if I wasn’t building on an existing free software island.
Selling the whole product, and having the whole product be open source, and having third party produced builds, collaborating together, it’s better on, I suspect, every angle.
It’s less clear you could begin this way, but I think you could. If we had, it would’ve been less of a shock to parts of the chef community. Not hearing a single conversation about lack of differentiation is like being in a hot tub, if you lived 13 years of it.
Read 7 tweets
28 Mar
Let's talk about this whole "k8s yaml is assembly" thing. When this gets said, it's often in a protective way. "The reason its so verbose is that it is assembly", or "The reason isn't dynamic is that is assembly". This is.. a bullshit excuse. It's not assembly at all.
What it is, is raw API calls. Without any of the kind of user tooling that might make it okay to make raw API calls. I know the story is, we're supposed to make those tools. But that's an enormous cop-out. A quick survey of the landscape shows that we're already @ ~6.
That's viable paths. None of which you could use effectively if you wanted to remain within the ecosystem broadly - each one will conflict with the others, do things slightly differently, and ultimately all of that will wind up straight on the user.
Read 19 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!