Re:Bento: Open-source fork of the project formerly known as ...
by kstrauser on Friday May 31, 2024 @03:00PM
(#40538994)
Having to audit every commit in what was a FOSS project to make sure the parts I care about weren't relicensed out from under me sounds like a lot of work.
I use Emacs. If the FSF suddenly started pulling parts of it out, I would not sit there and hope that they didn't come after the bits I need. If someone forked it with strong assurances that I could keep using all of Emacs, I'd probably switch to that work. "Just fork the bits that get taken away" would not be an option I'd consider.
Re:Bento: Open-source fork of the project formerly known as ...
by pessimizer on Friday May 31, 2024 @04:47PM
(#40540064)
I'm not sure what reason they would have to wait. If they're not interested in changing the architecture and everything on redpanda's side stays MIT licensed, the only maintenance work will be to pull in the changes. Sounds completely risk-free. Sounds like insurance.
Re:Bento: Open-source fork of the project formerly known as ...
by layer8 on Friday May 31, 2024 @05:23PM
(#40540409)
Mirroring doesn’t constitute a fork.
Re:Bento: Open-source fork of the project formerly known as ...
by demosthanos on Saturday June 01, 2024 @10:23AM
(#40546000)
A mirror that strips out the branding does. And the way Redpanda is treating their trademark would make me extremely nervous about using software with their branding in it, so that alone is a good reason to start a soft fork.
Re:Bento: Open-source fork of the project formerly known as ...
by agallego on Friday May 31, 2024 @05:28PM
(#40540460)
we trippled the team. added 3 meaningful connectors for CDC and zero-trust as well multi-lang SDK and kept 99% of the connectors available for ppl to make money on... as well as the core engine remaining MIT. This is about them not wanting to depend on redpanda products which is ok, but the whole thing is hard to believe from a company that has no open source products. it's more like "hey, i don't like it."
Re:Bento: Open-source fork of the project formerly known as ...
by 12_throw_away on Friday May 31, 2024 @11:11PM
(#40542577)
I dunno ... when you see some guy from RedPanda on twitter throwing around petty "trademark compliance" [1] threats to memory-hole an entire project ... honestly, it would be malpratice _not_ to immediately fork everything.
Re:Bento: Open-source fork of the project formerly known as ...
by scblock on Saturday June 01, 2024 @12:28AM
(#40542876)
The best part of this is "X" is such complete garbage that that post has literally zero context to someone unwilling to ever have an account on the tire fire that it is.
Re:Bento: Open-source fork of the project formerly known as ...
by demosthanos on Saturday June 01, 2024 @10:17AM
(#40545935)
You also managed to be completely tone deaf to the way that developers feel about open source projects. A gradual branding transition can be swallowed, but what you chose to do instead is immediately force everyone to stop using the old name under threat of legal action. Adding new plugins that are proprietary can be tolerated, but if you're surprised that relicensing previously open source code prompted a fork you apparently weren't paying attention to the enormous kerfuffles surrounding recent relicenses by better-loved companies than yours.
You're also at the same risk if you choose to use their fork.