<?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 on Open Source Funded</title>
    <link>https://ossfunded.com/tags/open-source/</link>
    <description>Recent content in Open Source on Open Source Funded</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 11 May 2026 09:00:00 +0000</lastBuildDate>
    <atom:link href="https://ossfunded.com/tags/open-source/index.xml" rel="self" type="application/rss+xml" />
    <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>
