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

科技回声

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

GitHubTwitter

首页

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

资源链接

HackerNews API原版 HackerNewsNext.js

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

Moving Apollo Federation 2 to the Elastic License v2

57 点作者 cjcenizal超过 3 年前

8 条评论

sneak超过 3 年前
This means this project is abandoning open source and free software, as the Elastic License is not an open source license.<p>&gt; <i>The Apollo developer community is at the heart of everything we do. As stewards of our community, we have a responsibility to prevent harm from anyone who intends to exploit our work without contributing back. We want to continue serving you by funding the development of important open-source graph technology for years to come. To honor that commitment, we’re moving Apollo Federation 2 to the Elastic License v2 (ELv2).</i><p>One of these things can&#x27;t be true.<p>It&#x27;s really disheartening to see fake-open-source projects like this tout &quot;the community&quot; without realizing that taking software freedoms away (which is what this not-open-source license does) is ultimately an antisocial move. Being able to run a business off of a private fork of the <i>software you gave away</i> is not a bug, it&#x27;s a feature. It&#x27;s not exploiting anyone.<p>There are lot of fake open source people and companies around now. Docker Desktop, for example, isn&#x27;t even source available.<p>Similarly, I personally view the AGPL as a nonfree license, although it&#x27;s being pushed by anticapitalist zealots at the FSF who of course invented the notion of software freedom in the first place so my classification is, of course, controversial.
评论 #29115430 未加载
评论 #29122524 未加载
评论 #29118553 未加载
评论 #29115809 未加载
评论 #29126405 未加载
评论 #29118023 未加载
评论 #29118681 未加载
ralmidani超过 3 年前
I used to be a Copyleft zealot. Thanks to the emergence of AWS and GCP, I’ve come around to being OK with licenses like Elastic, and if I start a software company in the future, I wouldn’t rule out protecting myself by licensing critical parts of my code with Elastic or a similar license.<p>I don’t even agree that these kinds of licenses are inherently “anti-FOSS”, but I do object to them being portrayed as actual FOSS licenses. “Source-available” is a reasonably well-defined term that should be used more often in these kinds of situations.<p>Edit: “You’re either with us or against us” is corrosive whether it’s in war, politics, software licensing, or any other realm.
rapnie超过 3 年前
There&#x27;s another HN submission [0] of Drew Devault&#x27;s take [1] on the license change: &quot;Breaking down Apollo Federation&#x27;s anti-FOSS corporate gaslighting&quot;.<p>[0] <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=29116938" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=29116938</a><p>[1] <a href="https:&#x2F;&#x2F;drewdevault.com&#x2F;2021&#x2F;11&#x2F;05&#x2F;Apollo-federation-2-gaslighting.html" rel="nofollow">https:&#x2F;&#x2F;drewdevault.com&#x2F;2021&#x2F;11&#x2F;05&#x2F;Apollo-federation-2-gasli...</a>
jensneuse超过 3 年前
Here are 2 MIT alternatives: <a href="https:&#x2F;&#x2F;github.com&#x2F;jensneuse&#x2F;graphql-go-tools" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;jensneuse&#x2F;graphql-go-tools</a>, written in Go, I&#x27;m the author. <a href="https:&#x2F;&#x2F;github.com&#x2F;mercurius-js&#x2F;mercurius" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;mercurius-js&#x2F;mercurius</a>, written in NodeJS. Here&#x27;s a benchmark comparing the two with Apollo: <a href="https:&#x2F;&#x2F;wundergraph.com&#x2F;blog&#x2F;benchmark_apollo_federation_gateway_v1_vs_v2_vs_wundergraph" rel="nofollow">https:&#x2F;&#x2F;wundergraph.com&#x2F;blog&#x2F;benchmark_apollo_federation_gat...</a>
评论 #29117667 未加载
评论 #29121400 未加载
mythz超过 3 年前
&gt; A call for a standard open license<p>If Elastic wants to see this sustainable licensing model adopted as the norm, it&#x27;s in their interest to rename the license so it&#x27;s not branded to a single company.
评论 #29116176 未加载
评论 #29115628 未加载
VoxPelli超过 3 年前
The only reasonable commercial license to have on an open source friendly project is the Business Source License which MariaDB created and which eg. Sentry has adopted as well.<p>That license will always to resolve to a GPL-compatible license after at most 4 years after release, ensuring that even if the creator goes out of business, the code will always be forkable eventually.<p>More info: <a href="https:&#x2F;&#x2F;perens.com&#x2F;2017&#x2F;02&#x2F;14&#x2F;bsl-1-1&#x2F;" rel="nofollow">https:&#x2F;&#x2F;perens.com&#x2F;2017&#x2F;02&#x2F;14&#x2F;bsl-1-1&#x2F;</a>
评论 #29117540 未加载
EdwardDiego超过 3 年前
&gt; Many successful companies built on open-source technology (such as Elastic, MongoDB, and Confluent) have followed the path we’re taking to protect their communities<p>I&#x27;m pretty sure Confluent&#x27;s licensing isn&#x27;t to protect the Kafka community.
janikvonrotz超过 3 年前
Aka the anti AWS licensing.
评论 #29120358 未加载