Shay Banon

I hope so. Because being very empathetic to OSI, they have to deal with the AI stuff and that's tough. And, you know, we donated money to OSI and we're trying to help, but that stuff, and I think it's more urgent to figure out than, you know, approving SSPL or something along those lines. So I do see a path where AGPL is good enough as a solution, if that makes sense.

I hope so. Because being very empathetic to OSI, they have to deal with the AI stuff and that's tough. And, you know, we donated money to OSI and we're trying to help, but that stuff, and I think it's more urgent to figure out than, you know, approving SSPL or something along those lines. So I do see a path where AGPL is good enough as a solution, if that makes sense.

I think they're very interesting. They're very similar to like Elastic License V2, and we're talking to all of them. It's still the... OSI will never approve these licenses, right? Because of the restrictions. Yeah, exactly. I think what MongoDB tried to do with SSPL is to actually create a very valid license that had a chance to get approved by OSI.

I think they're very interesting. They're very similar to like Elastic License V2, and we're talking to all of them. It's still the... OSI will never approve these licenses, right? Because of the restrictions. Yeah, exactly. I think what MongoDB tried to do with SSPL is to actually create a very valid license that had a chance to get approved by OSI.

And I think that's the path that I would want to take. Not like expand open source to allow for like 50 things get into it, But more around, let's figure out how do we still keep the high value open source term definition and apply it to AI, apply it to enterprise software.

And I think that's the path that I would want to take. Not like expand open source to allow for like 50 things get into it, But more around, let's figure out how do we still keep the high value open source term definition and apply it to AI, apply it to enterprise software.

Yeah. Yeah, I mean, cloning closed source and trying to replicate and reimplement. Well, at least until we can go and chat GPT prompt something that says, create me an open source version of X. Yeah, exactly. But yeah, I think that that's true.

Yeah. Yeah, I mean, cloning closed source and trying to replicate and reimplement. Well, at least until we can go and chat GPT prompt something that says, create me an open source version of X. Yeah, exactly. But yeah, I think that that's true.

By the way, the same is true, you know, it's like when people say rock pool, and by the way, I totally understand where it's coming from because this is like, this is how it feels. And you never argue with what someone feels. You know what I mean? It's like, it's not fair because it's like, that's the first impact reaction and that's how they feel. Then it's your responsibility to figure this out.

By the way, the same is true, you know, it's like when people say rock pool, and by the way, I totally understand where it's coming from because this is like, this is how it feels. And you never argue with what someone feels. You know what I mean? It's like, it's not fair because it's like, that's the first impact reaction and that's how they feel. Then it's your responsibility to figure this out.

But I think one of the beautiful things about open source is the ability to fork a project. And the ability to change it and the ability for it to grow and become something else. And when you change the license, then someone can go and fork the project and suddenly like a whole other project comes up and you remember, I don't know, what was it like? The best example from my old days was Jenkins.

But I think one of the beautiful things about open source is the ability to fork a project. And the ability to change it and the ability for it to grow and become something else. And when you change the license, then someone can go and fork the project and suddenly like a whole other project comes up and you remember, I don't know, what was it like? The best example from my old days was Jenkins.

You remember? There was like Hudson and then Jenkins came along, got forked, and Jenkins became the thing and it worked. And we're seeing some examples of it today. And I think one of the points of reference on why when we changed the license, we still behaved as open source is that no fork got successful, including open search. Because we still behaved like open source.

You remember? There was like Hudson and then Jenkins came along, got forked, and Jenkins became the thing and it worked. And we're seeing some examples of it today. And I think one of the points of reference on why when we changed the license, we still behaved as open source is that no fork got successful, including open search. Because we still behaved like open source.

We didn't suddenly put everything behind closed source. We didn't suddenly make everything commercial. And I think most users were fine with it the same way that most users are fine with Lama as an open source model. You know what I mean? And I think that's why it never happened to us. But yeah, maybe for other companies it might happen and it will be amazing if we can solve it.

We didn't suddenly put everything behind closed source. We didn't suddenly make everything commercial. And I think most users were fine with it the same way that most users are fine with Lama as an open source model. You know what I mean? And I think that's why it never happened to us. But yeah, maybe for other companies it might happen and it will be amazing if we can solve it.

Yeah. And I think Valky for Redis.

Yeah. And I think Valky for Redis.

That's another good example. But this is where I think most users saw how we behaved in the next few days and they were like, nothing changed. And they were less worried. Obviously, a lot of the people that are in the details and go back and have opinions about open source were hurt, justifyingly. I was hurt. But most users were like, it's fine. It's Elasticsearch. We know the team.

That's another good example. But this is where I think most users saw how we behaved in the next few days and they were like, nothing changed. And they were less worried. Obviously, a lot of the people that are in the details and go back and have opinions about open source were hurt, justifyingly. I was hurt. But most users were like, it's fine. It's Elasticsearch. We know the team.