Shay Banon
๐ค SpeakerAppearances Over Time
Podcast Appearances
I'm talking to tons of startups that go and say, I'll never open source my code that would have open sourced the code because they say, we don't want the cloud provider to come in and take all the stuff that we built and pulled something around it. I think there's a few companies that says we need to bring trademarks back and enforcement and things on those lines. All of these are good discussions.
I'm talking to tons of startups that go and say, I'll never open source my code that would have open sourced the code because they say, we don't want the cloud provider to come in and take all the stuff that we built and pulled something around it. I think there's a few companies that says we need to bring trademarks back and enforcement and things on those lines. All of these are good discussions.
Those are the discussions that we need to have. What I can say, at least with our change, and go back to what we spoke about in the beginning, I think that enough time has passed from the hectic days of early cloud that AGPL is potentially good enough protection. AGPL is the license that we chose to be open source, and it's potentially a good enough protection.
Those are the discussions that we need to have. What I can say, at least with our change, and go back to what we spoke about in the beginning, I think that enough time has passed from the hectic days of early cloud that AGPL is potentially good enough protection. AGPL is the license that we chose to be open source, and it's potentially a good enough protection.
So when I talk to companies today, I say, go open source, build things in the open, choose AGPL, and it's probably good enough protection. Because we're choosing a GP, you know what I mean? Because we're showing that that's the case. So hopefully that changes their trajectory of choosing an open source license and which one ends up being chosen.
So when I talk to companies today, I say, go open source, build things in the open, choose AGPL, and it's probably good enough protection. Because we're choosing a GP, you know what I mean? Because we're showing that that's the case. So hopefully that changes their trajectory of choosing an open source license and which one ends up being chosen.
Yeah, I think it's a good question. MongoDB that created the SSPL license. So MongoDB changed their license from AGPL to SSPL, being concerned that cloud providers will take AGPL software, will test AGPL basically, right? So they change it to SSPL.
Yeah, I think it's a good question. MongoDB that created the SSPL license. So MongoDB changed their license from AGPL to SSPL, being concerned that cloud providers will take AGPL software, will test AGPL basically, right? So they change it to SSPL.
So even from then, I think enough time has passed that I think when you put AGPL out there, it's a good sign for cloud providers that this is the contract that you expect to have with them. I think SSPL tries to solve it. MongoDB went through a whole process, and you can read the mailing list discussions and things like that around trying to get SSPL approved by OSI. It didn't happen.
So even from then, I think enough time has passed that I think when you put AGPL out there, it's a good sign for cloud providers that this is the contract that you expect to have with them. I think SSPL tries to solve it. MongoDB went through a whole process, and you can read the mailing list discussions and things like that around trying to get SSPL approved by OSI. It didn't happen.
I'm not pointing fingers at one side or another. There's a lot of emotions and the devil is in the details and what have you. I think there's a good question. I think there's a balance that OSI tries to put around what is open source and how do you define open source, which is very important to maintain. That social contract is important. There's a lot...
I'm not pointing fingers at one side or another. There's a lot of emotions and the devil is in the details and what have you. I think there's a good question. I think there's a balance that OSI tries to put around what is open source and how do you define open source, which is very important to maintain. That social contract is important. There's a lot...
writing on the term of open source that we should cherish it and treat it very dreadfully, if that makes sense. And that's like rushing to adding like five licenses to it and it's fine. And then it becomes, you know, if we do it, it becomes meaningless. Right. So we tried to figure out if there's an option with OSI to maybe revisit the SSPL discussion.
writing on the term of open source that we should cherish it and treat it very dreadfully, if that makes sense. And that's like rushing to adding like five licenses to it and it's fine. And then it becomes, you know, if we do it, it becomes meaningless. Right. So we tried to figure out if there's an option with OSI to maybe revisit the SSPL discussion.
They have a new leader and I think they're open for it. And they're trying to figure out what is the open source, how does open source live also in a world not only of cloud providers, but in a world of models and open weights versus open models and open data and things like that. And how does open source play in it? They have a lot on their hands.
They have a new leader and I think they're open for it. And they're trying to figure out what is the open source, how does open source live also in a world not only of cloud providers, but in a world of models and open weights versus open models and open data and things like that. And how does open source play in it? They have a lot on their hands.
I think they want and they really want to try to figure this out. But for the same reasons why we felt like we had to change the license because we don't have time, I actually think that we're in a position where I'm not worried that someone takes Elasticsearch and provides it as a service. So I can conceptually take the very, very minuscule risk of just going with AGPL.
I think they want and they really want to try to figure this out. But for the same reasons why we felt like we had to change the license because we don't have time, I actually think that we're in a position where I'm not worried that someone takes Elasticsearch and provides it as a service. So I can conceptually take the very, very minuscule risk of just going with AGPL.
And potentially with that, we're actually creating a fact. And it's like, that's it. AGPL is fine. That's how it works. And you don't have to go through the process of approving a different license.
And potentially with that, we're actually creating a fact. And it's like, that's it. AGPL is fine. That's how it works. And you don't have to go through the process of approving a different license.