TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Bento: Open-source fork of the project formerly known as Benthos

219 点作者 pauldix11 个月前

14 条评论

jeffail11 个月前
Hey it&#x27;s Ash (the maintainer being talked about in the blog). I&#x27;m not one for fork drama and I haven&#x27;t had a chance to fully read the blog so I don&#x27;t have a lot to say. However, this is a full fork of the entire codebase, which means plugin authors will need to choose one project or the other and are locked in, and is entirely unnecessary on both a technical and legal perspective.<p>If they&#x27;d instead chose to fork the plugins themselves (the only parts where the licenses changed, all except two are Apache V2) then all users can pick and choose which ones they include in their projects, and it doesn&#x27;t fragment the ecosystem at all. Your plugins would compile in my project, and mine would compile in yours.<p>The part they&#x27;re choosing to fork here, which will cause this rift in the community, is still MIT licensed: <a href="https:&#x2F;&#x2F;github.com&#x2F;redpanda-data&#x2F;benthos">https:&#x2F;&#x2F;github.com&#x2F;redpanda-data&#x2F;benthos</a>. If they simply chose to continue using this MIT part we can all live happily together in a utopian society fully saturated with plugged blobbery.<p>Edit: I&#x27;m bit a baby brained so I forgot that I&#x27;m literally streaming live in 30 minutes in order to explain all the changes in detail for those out of the loop: <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=X8nVdUuWZ80" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=X8nVdUuWZ80</a>
评论 #40538730 未加载
评论 #40540650 未加载
评论 #40540525 未加载
评论 #40539802 未加载
评论 #40540675 未加载
评论 #40555924 未加载
评论 #40545010 未加载
mihaitodor11 个月前
As a freelance engineer who&#x27;s a long time Benthos contributor and who volunteered a lot of community support for this project in the past several years, I don&#x27;t think it makes sense to fork it and I&#x27;m perfectly happy with the current approach where the core engine (<a href="https:&#x2F;&#x2F;github.com&#x2F;redpanda-data&#x2F;benthos">https:&#x2F;&#x2F;github.com&#x2F;redpanda-data&#x2F;benthos</a>) is MIT licensed as @jeffail mentioned and 3rd party plugins can live in other people&#x27;s repos and have various licenses, one example being <a href="https:&#x2F;&#x2F;github.com&#x2F;redpanda-data&#x2F;connect">https:&#x2F;&#x2F;github.com&#x2F;redpanda-data&#x2F;connect</a>.<p>I&#x27;m 100% committed to keep contributing to Benthos as long as it remains free and open source and I&#x27;m also happy to continue offering community support to whomever requests it on the official channels on Discord, Slack, GitHub etc.
评论 #40539316 未加载
chambers11 个月前
&gt; Changed the name of the project from Benthos to “Redpanda Connect”, and prohibited anyone from using the term “Benthos.” <a href="https:&#x2F;&#x2F;x.com&#x2F;emaxerrno&#x2F;status&#x2F;1796219957589786810" rel="nofollow">https:&#x2F;&#x2F;x.com&#x2F;emaxerrno&#x2F;status&#x2F;1796219957589786810</a><p>A complete rebranding suggests that the original OSS project will no longer be managed as its own independent entity. I think that alone gives good reason to fork.
评论 #40540471 未加载
ko_pivot11 个月前
I think forking is reasonable in this case. It’s one thing to change the GitHub org for a project because you aquihired the team, but it is another thing entirely to change the name of the project to match your company name, implying that the project is simply one of your products. The latter clearly gives off “Redis Labs” vibes. ‘Fool me once…’ is a justified reaction.
jauntywundrkind11 个月前
Most critical to me seems to be the integration relicensing&#x2F;de-open-sourcing (and the article seems generally to feel the same),<p>&gt; <i>Started relicensing some of the most critical integrations and connectors as proprietary2 under a completely different license</i><p>But left unsaid is which integrations got relicensed. I&#x27;m very curious to know!<p>Ok, from the Redpanda announcement, seems to be Splunk &amp; Snowflake connectors that they have moved to enterprise plan features. I&#x27;m not sure this is exhaustive but I tend to think it is. Source: <a href="https:&#x2F;&#x2F;redpanda.com&#x2F;blog&#x2F;redpanda-connect" rel="nofollow">https:&#x2F;&#x2F;redpanda.com&#x2F;blog&#x2F;redpanda-connect</a><p>It does make me wonder &amp; think, perhaps there&#x27;s too monolithic an architecture if moving two connectors out of core &amp; having bentho-snowflake and bentho-splunk forked off is too hard. Does the entire project really need a fork?
评论 #40538713 未加载
评论 #40538981 未加载
NortySpock11 个月前
As a hobbyist Benthos user (and an admirer of Benthos), I&#x27;m a bit nervous about the &quot;buyout&quot;.<p>But I think I get the logic -- RedPanda maintains support (and a bit of control) of a very useful tool that complements RedPanda&#x27;s core product (a drop-in Kafka replacement). In simple terms, RedPanda is stateful, Benthos is stateless, and Benthos is great for getting things into and out of a stateful thing.<p>Commoditize your complements, as Joel Spolsky said. [1]<p>Make it so no one can hinder developers getting data into (or out of) your database &#x2F; message broker &#x2F; stateful thing, and you&#x27;ll reap the low-friction rewards of &quot;developers finding it really easy to get stuff into and out of your system.&quot;<p>So I think I&#x27;m somewhat optimistic about all this.<p>[1] <a href="https:&#x2F;&#x2F;gwern.net&#x2F;complement" rel="nofollow">https:&#x2F;&#x2F;gwern.net&#x2F;complement</a>
disintegrator11 个月前
The core is still MIT-licensed and I don&#x27;t see a great reason why that would change. I&#x27;ve built many plugins for Benthos and Bloblang in the past and I&#x27;ve always been more inclined to use Benthos _as a library_. The Go package is great and the input&#x2F;output&#x2F;processor interface are easy to build against. I&#x27;m glad that nothing about my ability to do that is changing and I&#x27;ll be using it again in the future. Benthos is a phenomenal project that is now being sustained by a commercial entity.
评论 #40539481 未加载
评论 #40542594 未加载
eatonphil11 个月前
Alex, the CEO of Redpanda, responded.<p><a href="https:&#x2F;&#x2F;x.com&#x2F;emaxerrno&#x2F;status&#x2F;1796593469743620444" rel="nofollow">https:&#x2F;&#x2F;x.com&#x2F;emaxerrno&#x2F;status&#x2F;1796593469743620444</a>
评论 #40538674 未加载
评论 #40539004 未加载
评论 #40538678 未加载
评论 #40542890 未加载
xyzzy_plugh11 个月前
It feels pretty uncharitable for Redpanda to enforce their terms when they haven&#x27;t done anything of value with it yet. They made a bold claim that you&#x27;ll have to pay them to use these features, but you certainly don&#x27;t as they&#x27;re still available under MIT licensing.<p>One does not simply buy Open Source Software.<p>Until Redpanda actually makes any code changes, the ~three now-proprietary plugins are still available as Open Source Software: just browse to the commit before they slapped their license at the top.<p>These are all MIT and bit-for-bit identical to the now-proprietary plugins:<p>- Splunk HEC: <a href="https:&#x2F;&#x2F;github.com&#x2F;redpanda-data&#x2F;connect&#x2F;blob&#x2F;e653dc3f8a6eee072b391d5b3faa6a9a46ba00c9&#x2F;internal&#x2F;impl&#x2F;splunk&#x2F;template_output.yaml">https:&#x2F;&#x2F;github.com&#x2F;redpanda-data&#x2F;connect&#x2F;blob&#x2F;e653dc3f8a6eee...</a><p>- Snowflake: <a href="https:&#x2F;&#x2F;github.com&#x2F;redpanda-data&#x2F;connect&#x2F;blob&#x2F;e653dc3f8a6eee072b391d5b3faa6a9a46ba00c9&#x2F;internal&#x2F;impl&#x2F;snowflake&#x2F;output_snowflake_put.go">https:&#x2F;&#x2F;github.com&#x2F;redpanda-data&#x2F;connect&#x2F;blob&#x2F;e653dc3f8a6eee...</a><p>- Kafka topic logger: <a href="https:&#x2F;&#x2F;github.com&#x2F;redpanda-data&#x2F;connect&#x2F;blob&#x2F;e653dc3f8a6eee072b391d5b3faa6a9a46ba00c9&#x2F;internal&#x2F;impl&#x2F;kafka&#x2F;topic_logger.go">https:&#x2F;&#x2F;github.com&#x2F;redpanda-data&#x2F;connect&#x2F;blob&#x2F;e653dc3f8a6eee...</a>
评论 #40547600 未加载
dangoldin11 个月前
FWIW - Redpanda open sources their core product - <a href="https:&#x2F;&#x2F;github.com&#x2F;redpanda-data&#x2F;">https:&#x2F;&#x2F;github.com&#x2F;redpanda-data&#x2F;</a> while WarpStream keeps their core product proprietary - <a href="https:&#x2F;&#x2F;github.com&#x2F;warpstreamlabs">https:&#x2F;&#x2F;github.com&#x2F;warpstreamlabs</a>
评论 #40542502 未加载
teeray11 个月前
&gt; You might be thinking, “Wait a minute, isn’t WarpStream just another corporation? Why should I spend my time contributing to their project if they can just take my contributions at any time and commercialize them?”. Bento is 100% MIT licensed and will stay that way forever.<p>It would be interesting if there was a “no takebacks” enhancement to popular open-source licenses. Maybe the license could only change with a supermajority quorum of contributors.
评论 #40548312 未加载
评论 #40543316 未加载
评论 #40542529 未加载
olgeni11 个月前
The text &quot;Licensed as a Redpanda Enterprise file under the Redpanda Community&quot; appears in the two RCL-licensed connectors as listed on the web site:<p>github.com&#x2F;redpanda-data&#x2F;connect&#x2F;v4@v4.28.0&#x2F;internal&#x2F;impl&#x2F;snowflake&#x2F;output_snowflake_put.go github.com&#x2F;redpanda-data&#x2F;connect&#x2F;v4@v4.28.0&#x2F;internal&#x2F;impl&#x2F;splunk&#x2F;template_output.yaml<p>But also in an apparently unrelated file (Kafka seems to fall under Apache 2 from the website):<p>github.com&#x2F;redpanda-data&#x2F;connect&#x2F;v4@v4.28.0&#x2F;internal&#x2F;impl&#x2F;kafka&#x2F;topic_logger.go<p>Now I am a bit puzzled. What&#x27;s up with this?<p>I am furiously rewriting my way out of Benthos but I would like to keep the FreeBSD port in shape :D
petecooper11 个月前
&gt;Bento<p>A trip down memory lane:<p><a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Bento_(database)" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Bento_(database)</a>
评论 #40543111 未加载
评论 #40541833 未加载
User2311 个月前
&gt; We’re pretty sure this isn’t how copyrights, software licensing, and trademarks work (like, at all), but we also didn’t feel like arguing about it, or getting the lawyers involved.<p>Software licenses aren’t even required under the Copyright Act. It explicitly gives you permission to do that which you are supposedly licensed to do.