<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Open Source Funded</title>
		<link>https://ossfunded.com/</link>
		<description>Recent content on Open Source Funded</description>
		<generator>Hugo</generator>
		<language>en-US</language>
		
		
		
		
			<lastBuildDate>Mon, 22 Jun 2026 09:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://ossfunded.com/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Issue #13: funding, foundations, AI pressure, and open-source jobs</title>
				<link>https://ossfunded.com/posts/2026-06-22/</link>
				<pubDate>Mon, 22 Jun 2026 09:00:00 +0000</pubDate>
				<guid>https://ossfunded.com/posts/2026-06-22/</guid>
				<description>&lt;p&gt;This week in &lt;strong&gt;Open Source Funded&lt;/strong&gt;: grant and sponsorship news leads the issue, with EXANTE&amp;rsquo;s €1 million Gecko Fund, 67 new NLnet grants, OpenAI backing Rust, Django agencies funding an Executive Director search, and Mitchell Hashimoto pledging another $400,000 to Zig. There are also foundation and governance moves from Raku, DDEV, AgriOS, Dronecode, Commonhaus, CNCF, and others; open-source commercialization and licensing updates from xyflow, Prismatic, Flarum, ownCloud, and Synergy; and a heavy run of AI-related maintainer-capacity stories, from security report volume to AI-generated PR and patch noise. The jobs section has new roles across foundations, community work, commercial open source, and licensing.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Issue #12: Funding, EU policy, licensing scrutiny, maintenance strategy, and AI pressure</title>
				<link>https://ossfunded.com/posts/2026-06-15/</link>
				<pubDate>Mon, 15 Jun 2026 09:00:00 +0000</pubDate>
				<guid>https://ossfunded.com/posts/2026-06-15/</guid>
				<description>&lt;p&gt;This week in &lt;strong&gt;Open Source Funded&lt;/strong&gt;: standards participation showed up as maintainer infrastructure, fellowship, fundraising, donation appeals, and public-sector programs put money behind open source work, NSF announced a secure open-source ecosystem funding program, CNCF described OCI credit-funded Arm64 testing work across cloud-native projects, OpenAI opened a Codex support program for maintainers, Sovereign Tech-backed work reached Scala documentation and LLVM BOLT security, Rust, PHP, FSF, Ruby Central, FreeBSD, and Chainguard updates put maintenance, sustainability, free-software advocacy, ecosystem security funding, vulnerability remediation, and AI-assisted vulnerability discovery in the foreground, NLnet began shifting from NGI Zero toward Open Internet Stack programs, AI document and data interoperability work and European technology-sovereignty planning continued, Supabase and PgDog raised funding around open-source Postgres infrastructure, TensorZero archived its open-source repository after promoting seed funding, Intel ended development of BigDL, Snapmaker set aside community funding for an open-source 3D-printer ecosystem, European office-suite sovereignty and provenance arguments continued as Nextcloud described open source&amp;rsquo;s move into geopolitics, Conda packaging terms raised licensing-surprise questions, Akka.NET, Unleash, Fossorial, and Snowplow highlighted downstream and commercial-license decisions, Bambuddy put Bambu Lab cloud dependence and AGPL compliance back in view, commercial investment flowed into ecosystem security and core infrastructure patching, organizations joined open source foundations, coalitions, patent communities, research consortia, and standards efforts, LF Energy expanded its open-source grid portfolio, RedMonk, Jens Oliver Meiert, Gnuxie, and the Civil Infrastructure Platform mapped commercial and long-term maintenance tradeoffs, Vim Classic launched as an AI-free editor fork, curl prepared to pause vulnerability intake for a month while restating its human-review stance, and AI-assisted security and coding tools kept turning vulnerability discovery, disclosure, CVE-volume forecasts, remediation, legal compliance, contribution policy, developer tooling, FFmpeg zero-days, CI/CD abuse detection, Agentjacking, agent-generated pull requests, review culture and bottlenecks, ad-supported tool extensions, platform capacity, and maintainer boundaries into open source governance questions.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Issue #11: AI pressure, open source funding, and governance shifts</title>
				<link>https://ossfunded.com/posts/2026-06-08/</link>
				<pubDate>Mon, 08 Jun 2026 09:00:00 +0000</pubDate>
				<guid>https://ossfunded.com/posts/2026-06-08/</guid>
				<description>&lt;p&gt;This week in &lt;strong&gt;Open Source Funded&lt;/strong&gt;: commercial open source companies raised money, maintainers received new funding offers and security-audit support, governments kept tying open source to digital sovereignty, and AI-assisted development kept turning review, security, and provenance into governance questions.&lt;/p&gt;&#xA;&lt;h2 id=&#34;funding-sponsorship-and-sustainability&#34;&gt;Funding, sponsorship, and sustainability&lt;/h2&gt;&#xA;&lt;p&gt;&lt;strong&gt;Unleash&lt;/strong&gt; is moving its open-source feature-management repository from Apache 2.0 to &lt;strong&gt;AGPLv3&lt;/strong&gt; to keep the project sustainable. The company says its enterprise distribution remains commercially licensed, while official open-source Docker images and SDKs keep their existing licenses (&lt;a href=&#34;https://www.getunleash.io/blog/unleash-moving-to-agplv3&#34;&gt;Unleash&lt;/a&gt;).&lt;/p&gt;</description>
			</item>
			<item>
				<title>Issue #10: IBM and Red Hat&#39;s $5B pledge, F-Droid funding, and OpenAI&#39;s OSS credits</title>
				<link>https://ossfunded.com/posts/2026-06-01/</link>
				<pubDate>Mon, 01 Jun 2026 09:00:00 +0000</pubDate>
				<guid>https://ossfunded.com/posts/2026-06-01/</guid>
				<description>&lt;p&gt;This week in &lt;strong&gt;Open Source Funded&lt;/strong&gt;, &lt;strong&gt;IBM and Red Hat&lt;/strong&gt; announced &lt;strong&gt;Project Lightwell&lt;/strong&gt;, a &lt;strong&gt;$5 billion&lt;/strong&gt; commitment around securing open source software with AI (&lt;a href=&#34;https://newsroom.ibm.com/2026-05-28-ibm-and-red-hat-commit-5-billion-to-redefine-the-future-of-open-source-in-the-ai-era&#34;&gt;IBM&lt;/a&gt;). &lt;strong&gt;F-Droid&lt;/strong&gt; received &lt;strong&gt;$50,000&lt;/strong&gt; from &lt;strong&gt;FLOSS/fund&lt;/strong&gt; (&lt;a href=&#34;https://f-droid.org/en/2026/05/26/flossfund.html&#34;&gt;F-Droid&lt;/a&gt;), &lt;strong&gt;NLnet&lt;/strong&gt; opened new grant calls (&lt;a href=&#34;https://nlnet.nl/news/2026/20260601-call.html&#34;&gt;NLnet&lt;/a&gt;), the &lt;strong&gt;European Commission&lt;/strong&gt; reportedly looked to open source as part of its tech-sovereignty strategy (&lt;a href=&#34;https://agenceurope.eu/en/bulletin/article/13877/4/european-commission-seeks-to-harness-open-source-in-its-tech-sovereignty-strategy-and-develop-european-alternatives&#34;&gt;Agence Europe&lt;/a&gt;), &lt;strong&gt;OpenAI&lt;/strong&gt; offered Codex credits and tools to open source maintainers (&lt;a href=&#34;https://developers.openai.com/codex/open-source&#34;&gt;OpenAI&lt;/a&gt;), &lt;strong&gt;Packagist&lt;/strong&gt; detailed funded Composer and Packagist.org supply-chain work while launching sponsorships (&lt;a href=&#34;https://blog.packagist.com/an-update-on-composer-packagist-supply-chain-security/&#34;&gt;Packagist&lt;/a&gt;), &lt;strong&gt;Scala&lt;/strong&gt; completed a Sovereign Tech Fund-backed security audit (&lt;a href=&#34;https://www.scala-lang.org/blog/2026/06/01/first-part-security-audit.html&#34;&gt;Scala&lt;/a&gt;), &lt;strong&gt;RedMonk&lt;/strong&gt; highlighted hardened-image revenue models that share subscription income with maintainers (&lt;a href=&#34;https://redmonk.com/kholterhoff/2026/06/01/why-hardened-images-are-suddenly-everywhere/&#34;&gt;RedMonk&lt;/a&gt;), &lt;strong&gt;dbt Core v2&lt;/strong&gt; moved more commercial engine work into the Apache-licensed open source distribution as &lt;strong&gt;Fivetran&lt;/strong&gt; and &lt;strong&gt;dbt Labs&lt;/strong&gt; completed their merger (&lt;a href=&#34;https://docs.getdbt.com/blog/dbt-core-v2-is-here&#34;&gt;dbt Labs&lt;/a&gt;, &lt;a href=&#34;https://www.getdbt.com/blog/fivetran-dbt-labs-complete-merger-to-create-the-data-infrastructure-for-trusted-ai-agents&#34;&gt;Fivetran/dbt Labs&lt;/a&gt;), and &lt;strong&gt;Kefir&lt;/strong&gt; moved new compiler development private, citing sustainability concerns (&lt;a href=&#34;https://kefir.protopopov.lv/posts/announce2.html&#34;&gt;Kefir&lt;/a&gt;).&lt;/p&gt;</description>
			</item>
			<item>
				<title>Issue #9: pgBackRest funding, Bambu AGPL pressure, and AI disclosure load</title>
				<link>https://ossfunded.com/posts/2026-05-25/</link>
				<pubDate>Mon, 25 May 2026 09:00:00 +0000</pubDate>
				<guid>https://ossfunded.com/posts/2026-05-25/</guid>
				<description>&lt;p&gt;This week in &lt;strong&gt;Open Source Funded&lt;/strong&gt;, the most direct sustainability win came from &lt;strong&gt;pgBackRest&lt;/strong&gt;: after warnings that the PostgreSQL backup project could not continue on one sponsor alone, a coalition including AWS, Supabase, pgEdge, Tiger Data, Percona, and Eon.io stepped in to fund ongoing development.&lt;/p&gt;&#xA;&lt;p&gt;The licensing story of the week was still &lt;strong&gt;Bambu Lab&lt;/strong&gt;. Software Freedom Conservancy published a detailed AGPLv3 response, while coverage from Aftermath, The Verge, and Open Source For You showed how one fork dispute became a much broader fight over compliance, community trust, and control of 3D-printer software.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Issue #8: KDE funding, AI vulnerability pressure, and foundation homes</title>
				<link>https://ossfunded.com/posts/2026-05-18/</link>
				<pubDate>Mon, 18 May 2026 09:00:00 +0000</pubDate>
				<guid>https://ossfunded.com/posts/2026-05-18/</guid>
				<description>&lt;p&gt;This week in &lt;strong&gt;Open Source Funded&lt;/strong&gt;, European public-interest funding showed up in a big way: the Sovereign Tech Fund is investing more than €1.2 million in KDE over 2026 and 2027.&lt;/p&gt;&#xA;&lt;p&gt;The other big theme was AI pressure on open source security. Maintainers, public-sector teams, vendors, and lawmakers are all trying to respond to a world where vulnerability discovery and vulnerability reporting can scale faster than triage capacity.&lt;/p&gt;&#xA;&lt;p&gt;There was also plenty of governance activity: Zulip formed a nonprofit foundation, Block handed Goose to the Linux Foundation, Wikimedia joined the Digital Public Goods Alliance, and several organizations moved closer to Linux Foundation-hosted ecosystems.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Issue #7: AI pressure, funding, and foundation governance</title>
				<link>https://ossfunded.com/posts/2026-05-11/</link>
				<pubDate>Mon, 11 May 2026 09:00:00 +0000</pubDate>
				<guid>https://ossfunded.com/posts/2026-05-11/</guid>
				<description>&lt;p&gt;This week in &lt;strong&gt;Open Source Funded&lt;/strong&gt;, AI pressure kept showing up in open source governance: public repositories, vulnerability discovery, commit attribution, low-quality pull requests, and even unofficial ports using established project names.&lt;/p&gt;&#xA;&lt;p&gt;There was also important funding and foundation activity. CopilotKit raised $27 million, RadixArk launched with $100 million around SGLang, Dell and Lenovo became premier LVFS sponsors, Linea Stack moved into Linux Foundation Decentralized Trust governance, and Microcks became a CNCF incubating project.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Issue #6: funding rounds, foundation homes, and AI pressure on public code</title>
				<link>https://ossfunded.com/posts/2026-05-04/</link>
				<pubDate>Mon, 04 May 2026 09:00:00 +0000</pubDate>
				<guid>https://ossfunded.com/posts/2026-05-04/</guid>
				<description>&lt;p&gt;This week in &lt;strong&gt;Open Source Funded&lt;/strong&gt;, the strongest pattern was pressure: pressure to fund infrastructure, pressure to formalize governance, pressure to draw clearer boundaries around AI tooling, and pressure on public code repositories as security concerns rise.&lt;/p&gt;&#xA;&lt;p&gt;The money side was active. Cloudsmith, JuliaHub, Expo, ComfyUI, Orkes, and OpenObserve all raised new funding around commercial layers built near open source ecosystems. Foundation activity was also busy, with O-RAN moving under LF Networking, Symposium joining the Rust Innovation Lab, and the Tokenized Assets Standard becoming a new LF Decentralized Trust lab.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Issue #5: foundation moves, private turns, and sharper AI rules</title>
				<link>https://ossfunded.com/posts/2026-04-20/</link>
				<pubDate>Mon, 20 Apr 2026 09:00:00 +0000</pubDate>
				<guid>https://ossfunded.com/posts/2026-04-20/</guid>
				<description>&lt;p&gt;This week in &lt;strong&gt;Open Source Funded&lt;/strong&gt;, the pattern was consolidation under pressure.&lt;/p&gt;&#xA;&lt;p&gt;One project moved into a new foundation home. Another got a more explicit operating plan for long-term survival. A high-profile startup decided openness had become too risky and took its core product private. And on the AI side, projects kept tightening the line between tool use and human responsibility, with some communities allowing assisted work and others banning machine-generated contributions outright.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Issue #4: funding signals, foundation moves, and AI review strain</title>
				<link>https://ossfunded.com/posts/2026-04-13/</link>
				<pubDate>Mon, 13 Apr 2026 09:00:00 +0000</pubDate>
				<guid>https://ossfunded.com/posts/2026-04-13/</guid>
				<description>&lt;p&gt;This week in &lt;strong&gt;Open Source Funded&lt;/strong&gt;, projects kept moving into foundation structures just as the funding picture looked uneven again.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Apache&lt;/strong&gt; picked up a major donation and turned it into a bigger responsible-AI funding push. &lt;strong&gt;CPython&lt;/strong&gt; maintenance funding was extended. &lt;strong&gt;GitButler&lt;/strong&gt; and &lt;strong&gt;SiFive&lt;/strong&gt; landed fresh capital. But &lt;strong&gt;Session&lt;/strong&gt; warned it may only have about 90 days of runway left. Across the rest of the cycle, the AI story stayed familiar: better tools often meant more review, more policy, and more operational burden for maintainers. The sharper licensing questions moved toward AI model terms, provenance fights, and what &amp;ldquo;open&amp;rdquo; will mean in the next round of model releases. Meanwhile, the &lt;strong&gt;VeraCrypt / WireGuard&lt;/strong&gt; signing mess showed how much open source distribution still depends on third-party chokepoints.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Issue #3: foundation handoffs, office-suite drama, and AI review pressure</title>
				<link>https://ossfunded.com/posts/2026-04-06/</link>
				<pubDate>Mon, 06 Apr 2026 09:00:00 +0000</pubDate>
				<guid>https://ossfunded.com/posts/2026-04-06/</guid>
				<description>&lt;p&gt;This week in &lt;strong&gt;Open Source Funded&lt;/strong&gt;, open source kept getting more formal structure at exactly the moment its human support systems looked shakier.&lt;/p&gt;&#xA;&lt;p&gt;Several projects moved into foundation homes or foundation-run structures. But the rest of the week was rougher: office-suite communities fell into public licensing and governance fights, security funding paused in visible ways, maintainer succession remained fragile, and AI kept pushing more cost into review queues instead of removing it.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Issue #2: Foundation moves, sustainability pressure, and AI governance friction</title>
				<link>https://ossfunded.com/posts/2026-03-30/</link>
				<pubDate>Mon, 30 Mar 2026 09:00:00 +0000</pubDate>
				<guid>https://ossfunded.com/posts/2026-03-30/</guid>
				<description>&lt;p&gt;This week in &lt;strong&gt;Open Source Funded&lt;/strong&gt;, the clearest pattern is institutionalization.&lt;/p&gt;&#xA;&lt;p&gt;Several projects moved under foundation governance or advanced inside existing foundation maturity ladders. Around that, the rest of the week&amp;rsquo;s stories kept returning to the same questions: who is paying for the commons, what kinds of support actually matter, and how much extra policy and review work AI is now creating for open source projects.&lt;/p&gt;&#xA;&lt;h2 id=&#34;projects-joining-a-foundation&#34;&gt;Projects joining a foundation&lt;/h2&gt;&#xA;&lt;p&gt;Per this issue&amp;rsquo;s editorial rules, this section also includes projects advancing to a new stage inside an existing foundation.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Issue #1: Security grants, maintainer funding, and support for open source commons</title>
				<link>https://ossfunded.com/posts/2026-03-23/</link>
				<pubDate>Mon, 23 Mar 2026 09:00:00 +0000</pubDate>
				<guid>https://ossfunded.com/posts/2026-03-23/</guid>
				<description>&lt;p&gt;Welcome to the first issue of &lt;strong&gt;Open Source Funded&lt;/strong&gt;, a weekly roundup of grants, sponsorships, endowments, and other financial support for open source projects and the institutions around them.&lt;/p&gt;&#xA;&lt;p&gt;This opening issue reflects one clear editorial bias: we are prioritizing &lt;strong&gt;pure open source projects, foundations, and shared infrastructure&lt;/strong&gt; over startup fundraising rounds.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-strongest-project-focused-funding-signals-this-week&#34;&gt;The strongest project-focused funding signals this week&lt;/h2&gt;&#xA;&lt;h3 id=&#34;linux-foundation-openssf-and-alpha-omega-announced-125-million-for-open-source-security&#34;&gt;Linux Foundation, OpenSSF, and Alpha-Omega announced $12.5 million for open source security&lt;/h3&gt;&#xA;&lt;p&gt;The biggest headline in the source list is the &lt;strong&gt;$12.5 million grant funding announcement&lt;/strong&gt; tied to open source security. The Linux Foundation and OpenSSF positioned it as support for securing critical open source infrastructure, which makes it highly relevant to maintainers even if the money is being organized at the ecosystem level.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
