惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Y
Y Combinator Blog
B
Blog
S
SegmentFault 最新的问题
Vercel News
Vercel News
博客园 - 聂微东
宝玉的分享
宝玉的分享
C
Check Point Blog
有赞技术团队
有赞技术团队
IT之家
IT之家
V
V2EX
爱范儿
爱范儿
GbyAI
GbyAI
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
Microsoft Azure Blog
Microsoft Azure Blog
P
Proofpoint News Feed
博客园 - 司徒正美
博客园_首页
Last Week in AI
Last Week in AI
博客园 - 叶小钗
量子位
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
F
Fortinet All Blogs
腾讯CDC
J
Java Code Geeks

Danb Blog

August 2026: What I've Been Working On · Danb Blog Great Tech: Intel 2500k CPU · Danb Blog July 2026: What I've Been Working On · Danb Blog My Experience with Ubuntu Desktop 26.04 · Danb Blog Thumbnails for Orca 3MF in GNOME Files · Danb Blog Cheaper Sodastream Gas with a Big Tank · Danb Blog June 2026: What I've Been Working On · Danb Blog Running Snyk On Forgejo/Codeberg Actions · Danb Blog Tuta & Proton: An Open Source Client Does Not Result in an Open Source Service · Danb Blog May 2026: What I've Been Working On · Danb Blog 3D Printing Parts for my Greenhouse, Round 2 · Danb Blog Great Devices: Nexus 7 2013 · Danb Blog R36S Console RetroArch Stuck Menu Issue · Danb Blog April 2026: What I've Been Working On · Danb Blog Basic OpenCode Sandboxing with Docker · Danb Blog Games Played in 2025 · Danb Blog March 2026: What I've Been Working On · Danb Blog Shivam Mathur's "node-docker" Images are Awesome for PHP CI · Danb Blog February 2026: What I've Been Working On · Danb Blog Your BookStackApp project was assigned as a project for my Software Architecture course · Danb Blog My Sovol SV08 3D Printer Setup in 2026 · Danb Blog January 2026: What I've Been Working On · Danb Blog Epson Printer: The administrator password you entered was not recognized · Danb Blog Pressure to Follow Process · Danb Blog Online Shopping Email Notifications · Danb Blog My HomeLab Setup in 2026 · Danb Blog Linux Label Printing with the Phomemo D30 · Danb Blog Reporting to the CMA: Google Android Developer Verification · Danb Blog OPNsense & Dnsmasq: Responding with specific DNS servers · Danb Blog An Impromptu Introduction to ZFS Drive Replacement at 1am · Danb Blog
Redefining Open Source via "Commercial Open Source" · Dan...
2023-02-10 · via Danb Blog

As i’ve written about before, I think the term “Open Source” is quite important but it’s not uncommon to see the term stretched or misrepresented, often for business benefit. For the last year I’ve been recording such scenarios and a frequent character in those records has been Runa Capital, a venture capital firm founded in 2010 that has a focus on tech.

Runa often like to publish lists like their “Awesome open-source alternatives to SaaS” repo or “The fastest-growing open-source startups in 2022”, the latter of which is part of their “ROSS (Runa Open Source Startup) Index” series where they provide quarterly and annual top lists according to their own methodology. I believe this is all to establish themselves within the open source space and market their firm; They often push for those in their lists to add their “ROSS Badges” to their pages and they propagate their content through news sites.

Nothing wrong with any of that, but within these lists they often stretch the definition of open source quite far, and they do this quite consistently. As an example, here’s 4 projects from their “fastest-growing open-source startups in 2022” list that wouldn’t typically be considered open source:

This isn’t a one-off case. Here’s an issue I raised querying 14 projects listed on their awesome-oss-alternatives list. Here’s me querying their Q4 2022 ROSS list, and for their Q2 2022 list.

For their 2022 list I received a response from a general partner at Runa:

There are two approaches to open source: orthodox and commercial. As a VC, we stick to the latter and consider e.g. Elastic and MongoDB as COSS companies, despite SSPL is not approved by the OSI. The same for @OpenReplayHQ and many others.

Personally, I can’t help feeling gaslit from this response. Never have I heard someone use the term “orthodox” open source but it’s being positioned here like a common equivalent to “commercial” open source, allowing them to fence the existing commonly understood definition of open source into “orthodox” so they can define the latter “commercial” open source as desired. The idea that open source, with the “commercial” categorization, should allow for a more open interpretation is an insult to those people, and companies, that have managed to make commercial success in the open source space. Additionally, their “As a VC, we stick to the latter” feels like an insult to all VCs that do considerately fund open source projects & start-ups.

I followed up their response with this:

But then where do you draw the line for what open source is? Some of those project’s licenses are quite restrictive. Obsidian isn’t even source available. This kind of thing is commonly seen as attempting to stretch the open source definition for marketing and business benefit

As of writing, I’ve yet to hear a response.

Even if they did feel it’s fine to use and redefine open source by sticking “commercial” before it, that’s not something they do most of the time. “Commercial” rarely sits in front of open source in their titles or content. Or maybe they expect everyone else to start using “orthodox” open source as a differentiator.

I understand not everyone will have the same viewpoint as me, and many don’t see reason to be so strict with the definition & use of open source; Fair enough. But it’s kind of frustrating to me that it’s almost always stubbornly mis-used in cases where that entity benefits from doing so. Here, for marketing and strategy of their own investments. This kind of thing gives me “Embrace, extend, and extinguish” vibes. They’ve embraced open source to establish themselves in the space, they’ve extended the term and it’s definition, which eventually helps to extinguish its original use.