<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="3.10.0">Jekyll</generator><link href="https://blog.oscollective.org/feed.xml" rel="self" type="application/atom+xml" /><link href="https://blog.oscollective.org/" rel="alternate" type="text/html" /><updated>2026-11-18T16:21:02+00:00</updated><id>https://blog.oscollective.org/feed.xml</id><title type="html">Open Source Collective</title><subtitle>News and updates from Open Source Collective, the fiscal host for open source projects.</subtitle><entry><title type="html">OSC is bringing two questions to All Things Open</title><link href="https://blog.oscollective.org/2026/10/17/osc-is-bringing-two-questions-to-all-things-open/" rel="alternate" type="text/html" title="OSC is bringing two questions to All Things Open" /><published>2026-10-17T19:51:57+00:00</published><updated>2026-10-17T19:51:57+00:00</updated><id>https://blog.oscollective.org/2026/10/17/osc-is-bringing-two-questions-to-all-things-open</id><content type="html" xml:base="https://blog.oscollective.org/2026/10/17/osc-is-bringing-two-questions-to-all-things-open/"><![CDATA[<p>Next week Open Source Collective will be at All Things Open in Raleigh. Caitlin and I will be at our table (#2) near the Attendee Lounge on Monday, October 19, and Tuesday, October 20. As with last year, we’re not giving a talk; instead, we are coming to have conversations. </p>

<p>We have one question for maintainers and funders: what does it take for the software we all depend on to last?</p>

<p><strong>For maintainers: what would $1,000 do?</strong></p>

<p>Open Source Collective is a nonprofit fiscal host that provides the legal and financial infrastructure for 2,500+ open source projects, so maintainers can accept funds, pay people and vendors, sign contracts, and stay focused on the work. Every day we see something that rarely makes it into conference talks. Money matters, but what does sustainability look like?</p>

<p>So at our table we are asking maintainers a simple question. If your project received $1,000, what would you do with it? Pay a contributor for a week of issue triage? Cover hosting costs? Put it toward a documentation sprint, or help a new maintainer travel to their first conference? There is no wrong answer. We are giving $1,000 to one project as part of our time at ATO, and we want to hear how maintainers think about putting money to work.</p>

<p><strong>For funders: how do you decide what to fund?</strong></p>

<p>The second question is for the companies, foundations, and public bodies that want to support open source and aren’t sure where to start. You depend on thousands of packages, so which ones matter most? Do you fund the projects everyone recognizes, or the quieter ones underneath them? How much, how long, and through what process, so that procurement and legal can say yes?</p>

<p>Funding works best when it follows real use: the dependencies your organization actually runs on, including ones that don’t show up in a keynote. You can measure that now. Ecosyste.ms publishes open data and APIs that map software interdependencies, offering insights into usage, creation, and impact. It pulls together data from package registries, software repositories, vulnerability databases, containers, and operating systems, so you can see which projects are part of the critical software ecosystems that form the backbone of our digital infrastructure, and which of those keep your business running.</p>

<p>Funding also works best when it recurs. Infrastructure is not a one-time purchase. If your business would feel it when a project goes quiet, that project is already part of your continuity plan, whether or not it is in your budget.</p>

<p>At ATO we are offering one funder a funding intelligence session. We’ll start with a conversation about your organization, what you depend on, and what kind of support makes sense for you. Then we’ll walk you through how ecosyste.ms can map your dependencies and give you a report to take to your leadership. It’s the conversation we wish more funders had before they write the first check.</p>

<p><strong>Why both sides need the same home</strong></p>

<p>Maintainers and funders are working on the same problem from opposite ends.</p>

<p>Maintainers who get funding have to figure out how to receive it, pay the contributor who’s been triaging issues, and respond when a sponsor’s procurement team sends a vendor form. A funder who wants to support that maintainer needs someone who can sign the contract, take the payment, and show where the money went. </p>

<p>That’s the job of a fiscal host. Projects we host can take in money, pay contributors and vendors, and sign agreements without setting up their own legal entity. Every budget on Open Collective is public, so maintainers, funders, and anyone else can see what came in and where it went. Fiscal hosting is the middleware that lets money move cleanly in both directions. People are more important than code, and the people who maintain critical software deserve the same practical infrastructure the rest of the working world takes for granted. Accounting. Contracts. Employment pathways. Someone to call when the paperwork gets strange.</p>

<p>None of this gets solved at a conference, but it’s a good place to have these conversations. ATO brings together maintainers, community leaders, and the companies that build on open source. We want to hear what is working for you, what is getting in your way, and where a fiscal host could make your work easier. We’re there to listen.</p>

<p><strong>Come find us</strong></p>

<p>If you will be in Raleigh, stop by our table, #2 near the Attendee Lounge. Tell us what $1,000 would do for your project, or what is making your funding decisions hard. We will scan your badge, and you’ll be entered. No purchase is necessary. We’ll announce the winner afterward by email and on our social channels.</p>

<p>If you cannot make it to ATO, the conversation is still open. Projects can learn about our fiscal hosting and apply at oscollective.org. Organizations that want to fund the software they already depend on can start at oscollective.org or write to us at hello@oscollective.org.</p>

<p>See you in Raleigh.</p>

<p>Lauren Gardner</p>

<p>Executive Director, Open Source Collective</p>]]></content><author><name>Lauren Gardner</name></author><summary type="html"><![CDATA[Next week Open Source Collective will be at All Things Open in Raleigh. Caitlin and I will be at our table (#2) near the Attendee Lounge on Monday, October 19, and Tuesday, October 20. As with last year, we’re not giving a talk; instead, we are coming to have conversations. ]]></summary></entry><entry><title type="html">Why OSC is Moving Forward with Optional Tips</title><link href="https://blog.oscollective.org/2026/10/15/why-osc-is-moving-forward-with-optional-tips/" rel="alternate" type="text/html" title="Why OSC is Moving Forward with Optional Tips" /><published>2026-10-15T15:46:28+00:00</published><updated>2026-10-15T15:46:28+00:00</updated><id>https://blog.oscollective.org/2026/10/15/why-osc-is-moving-forward-with-optional-tips</id><content type="html" xml:base="https://blog.oscollective.org/2026/10/15/why-osc-is-moving-forward-with-optional-tips/"><![CDATA[<p><strong>Where things stand</strong></p>

<p>In our <a href="https://opencollective.com/opensource/updates/tips-an-independent-sustainable-future-for-the-open-collective-platform1">last post</a>, we shared that we were testing an optional tip on contributions to OSC-hosted Collectives. We are doing this because OSC’s funding commitment to support the platform’s transition to a nonprofit is ending, and because tips have proven to be the most reliable way to keep the Open Collective platform independent and sustainable.</p>

<p>That test has now run for five weeks, and across nearly 2,000 contributions, we saw no meaningful reduction in the amount of money donated to collectives when we included a tip request. Based on these findings, we’ll roll out tips across all incoming donations today, October 15th, 2026. </p>

<p>Here’s what we found and what happens next.</p>

<p><strong>What we found</strong> </p>

<p>Since August 27, we’ve randomly assigned a percentage of contributors to an OSC-hosted Collective to one of two groups. One group saw an optional tip at checkout, with a 15% suggested tip preselected, and the other group did not see a tip option. We then compared the resulting donation amounts going to Collectives to ensure that transactions with tips enabled were not negatively impacted. </p>

<p>Across 1,984 contributions, the group that saw the tip directed $27,941 to Collectives, compared with $28,886 in the group that didn’t. That’s 3.3% lower, or $945 over five weeks. It’s a small difference, and within the range we’d expect from statistical variance. </p>

<p>The tip-shown group also completed more contributions (1,015 vs 969), and the median contribution is $10 in both groups. If tips did harm, we would expect fewer contributions or a lower median in the tip-shown group.</p>

<p><strong>Next Steps</strong></p>

<p>The test showed what we hoped for: an optional tip did not materially affect the donation amount the collective received. Contributions completed went up, not down, and the median contribution was identical in both groups. Based on these findings, you’ll see a request for an optional tip on all donations to OSC-hosted Collectives starting today (October 15th, 2026).</p>

<p>Finally, based on feedback, we’ve updated the tip UX to make it easier for donors to opt out or set their preferred tip amount. We will continue to improve our donation flow and user experience.</p>

<p>[<img src="https://opencollective-production.s3.us-west-1.amazonaws.com/update/945af418-2fc4-458a-9cd8-decf08cc232e/Screenshot%202026-10-14%20at%2012.12.10%E2%80%AFAM.png" alt="" /></p>

<p>](https://opencollective-production.s3.us-west-1.amazonaws.com/update/945af418-2fc4-458a-9cd8-decf08cc232e/Screenshot%202026-10-14%20at%2012.12.10%E2%80%AFAM.png)</p>

<p>**We’re still watching
**</p>

<p>Ending the test doesn’t mean we stop paying attention. We’ll continue to monitor the rollout. If we see these numbers fall, we’ll act immediately to ensure contributions to our collectives aren’t affected.</p>

<p>And as always, we are here to answer any questions or concerns you may have. Please feel free to write to us at hello@oscollective.org</p>]]></content><author><name>Lauren Gardner</name></author><summary type="html"><![CDATA[Where things stand]]></summary></entry><entry><title type="html">Update: Bank payments via Wise are available again</title><link href="https://blog.oscollective.org/2026/08/20/update-bank-payments-via-wise-are-available-again/" rel="alternate" type="text/html" title="Update: Bank payments via Wise are available again" /><published>2026-08-20T22:08:57+00:00</published><updated>2026-08-20T22:08:57+00:00</updated><id>https://blog.oscollective.org/2026/08/20/update-bank-payments-via-wise-are-available-again</id><content type="html" xml:base="https://blog.oscollective.org/2026/08/20/update-bank-payments-via-wise-are-available-again/"><![CDATA[<p>Hi all, a quick update on the Wise account review that I shared with you on the 17th. </p>

<p>Wise has completed its review of Open Source Collective’s account, and outgoing bank payments are now operating as normal. You may submit expenses for payment by bank transfer as usual.</p>

<p>Thank you for your patience!</p>]]></content><author><name>Grace Powers</name></author><summary type="html"><![CDATA[Hi all, a quick update on the Wise account review that I shared with you on the 17th. ]]></summary></entry><entry><title type="html">OSC Community Update: July 2026</title><link href="https://blog.oscollective.org/2026/08/17/osc-community-update-july-2026/" rel="alternate" type="text/html" title="OSC Community Update: July 2026" /><published>2026-08-17T17:10:25+00:00</published><updated>2026-08-17T17:10:25+00:00</updated><id>https://blog.oscollective.org/2026/08/17/osc-community-update-july-2026</id><content type="html" xml:base="https://blog.oscollective.org/2026/08/17/osc-community-update-july-2026/"><![CDATA[<p>Hi OSC community, we hope August is treating you well! This month, we’re excited to introduce a new section to our monthly updates: “What We’re Reading.” We hope you enjoy it! Without further ado…</p>

<h3 id="-announcements">**📣 Announcements</h3>
<p>**</p>

<p><strong>Stripe virtual cards are back!</strong></p>

<p>At long last: Stripe virtual cards are once again available to OSC-hosted projects!</p>

<p>Some longtime hosted projects may remember that <a href="https://opencollective.com/opensource/updates/closing-our-virtual-card-program">we had to stop offering Stripe virtual cards in 2023</a> after a change to Stripe’s restricted-business policy meant that Stripe could no longer support the offering for us as a fiscal host.</p>

<p>Since then, we’ve regularly heard from hosted proejcts about how valuable the cards are and how much easier they make managing project expenses. Hearing from you reinforced how important it was for us to keep advocating for Stripe to restore this offering while also exploring other providers and potential solutions.</p>

<p>We’re very happy to share that those advocacy efforts have paid off: Stripe gave us the green light this week to begin offering virtual cards again!</p>

<p>Cards are approved on a case-by-case basis. Visit our updated docs to learn about eligibility, how to request a card, and the requirements for using one: <a href="https://docs.oscollective.org/for-hosted-member-projects/spending-money-and-getting-paid/virtual-cards">https://docs.oscollective.org/for-hosted-member-projects/spending-money-and-getting-paid/virtual-cards</a></p>

<p>With all that said, some projects were able to keep their Stripe cards throughout this period, and we know some received inactivity notices this weekend. These cards dates will be extended. Once they’re extended, be sure to update the expiration date with any vendors that have the card on file.</p>

<p><strong>Temporary pause on bank payments via Wise</strong></p>

<p>Outgoing bank payments are temporarily paused while Wise, our payment provider, completes a re-verification of Open Source Collective’s account.</p>

<p>What this means for expenses:</p>

<ul>
  <li>You can continue submitting expenses as normal</li>
  <li>Admin-approved expenses set to be paid by bank transfer will remain in OSC’s “Ready to Pay” queue until the verification is complete</li>
  <li>No action is required from collectives or payees at this time, unless payees prefer to use PayPal for disbursements.</li>
</ul>

<p>We’re hopeful that Wise completes this re-verification quickly, and our team is ready to process expenses using bank accounts as soon as we receive approval to resume them. We’ll let you know as soon as that happens.</p>

<p>PayPal remains available for payees who prefer not to wait. Please note that PayPal often does charges higher fees than bank transfer, so this may not be an option for all expenses depending on the project’s balance or the project’s preferences. To receive payment through PayPal, payees must connect their PayPal account through the PayPal authorization flow. More info on how to do that can be found here: <a href="https://documentation.opencollective.com/expenses-and-getting-paid/submitting-expenses#connecting-your-paypal-account">https://documentation.opencollective.com/expenses-and-getting-paid/submitting-expenses#connecting-your-paypal-account</a></p>

<p><strong>New documentation: admin financial responsibilities</strong></p>

<p>We’ve published a new Admin Financial Responsibilities guide in our docs to help project admins understand their role in responsibly managing project funds. You can find it here: <a href="https://docs.oscollective.org/for-hosted-member-projects/managing-project-funds/admin-financial-responsibilities">https://docs.oscollective.org/for-hosted-member-projects/managing-project-funds/admin-financial-responsibilities</a></p>

<p>It covers:</p>

<ul>
  <li>What admins should review before approving an expense</li>
  <li>How OSC’s review process complements admin approvals</li>
  <li>What to do if you’re ever unsure about an expense</li>
</ul>

<p>If you approve expenses, please take a few minutes to read through it. Your diligence helps ensure project funds are used responsibly, contributors can trust how donations are managed, and OSC remains compliant with the financial and legal requirements that make fiscal hosting possible.</p>

<p><strong>Add your project’s repository to your Open Collective page</strong></p>

<p>Please take a moment to make sure your project’s repository URL is listed on your project’s Open Collective page. Making your repository easy to find helps donors, community member, and the OSC team quickly access your project’s source code.</p>

<p>To update it:</p>

<p>Dashboard → Settings → Info</p>

<p>Add your repository URL under Website / Social Links. You can also add your website and other community links, such as Discord, LinkedIn, Mastodon, Slack, YouTube, and more.</p>

<h3 id="-community-highlights"><strong>✨ Community Highlights</strong></h3>

<p>Last month, we accepted 14 new collectives to OSC! Welcome to soybeanjs, DragonFruit, HideText, cpp-linter, Kova, LibrePods, NORA Workshop Series, Stratum, OpenSAK, Rockxy, Mantle Ui, Mnemosyne, Veryl, and Gungraun!</p>

<h3 id="what-we-are-reading">**📚What We Are Reading</h3>
<p>**</p>

<p>“What We’re Reading” is a new section featuring reads and conversations from OSC-hosted projects and their admins, friends of OSC, and others from across the open source ecosystem.</p>

<ul>
  <li>
    <p><strong>Open Source Must Be Fun (Or It Will Die)</strong> <a href="https://opencollective.com/redirect?url=https%3A%2F%2Fmikemcquaid.com%2Fopen-source-must-be-fun-or-it-will-die%2F">https://mikemcquaid.com/open-source-must-be-fun-or-it-will-die/</a>
“Stop doing the parts of your project that are not fun. Maybe that’s stable releases. Maybe that’s release notes. Maybe that’s backwards compatibility. Whatever it is: again, you <a href="https://opencollective.com/redirect?url=https%3A%2F%2Fmikemcquaid.com%2Fopen-source-maintainers-owe-you-nothing%2F">don’t owe anyone anything</a>.”</p>
  </li>
  <li>
    <p><strong>Andrew Nesbitt on AI, Transitive Dependencies, and the New Open Source Security Crunch:</strong> <a href="https://opencollective.com/redirect?url=https%3A%2F%2Fpodcast.sustainoss.org%2F290">https://podcast.sustainoss.org/290</a></p>
  </li>
</ul>

<p>Have you read, watched, listened to, or created anything yourself about open source lately? Lets keep the conversation going by sharing links below. You can also email us if you’d like us to consider featuring it in our next update!</p>

<h3 id="-upcoming">**📅 Upcoming</h3>
<p>**</p>

<ul>
  <li><strong>Open Technology Fund</strong> is accepting applications to the Information Controls Research Program (ICRP), which supports applied research into emerging threats to internet freedom and countering the most repressive digital authoritarianism. Researchers embed with a supportive host organization full-time for the duration of their project (3, 6, 9, or 12 months) and receive a monthly stipend of USD $7,000.</li>
</ul>

<p>****The 2026 application window will be open until September 7, 2026. More information at - <a href="https://opencollective.com/redirect?url=https%3A%2F%2Fwww.opentech.fund%2Fresearch-2%2Ficrp%2F">https://www.opentech.fund/research-2/icrp/</a></p>

<ul>
  <li><strong>Now Open: Applications for Session 5 of the GitHub Secure Open Source Fund.</strong> You can apply before August 24. For more information, please see: <a href="https://github.com/open-source/github-secure-open-source-fund">https://github.com/open-source/github-secure-open-source-fund</a></li>
</ul>

<p>Thanks for being part of the OSC community. As always, if you have any questions, feedback, or ideas for future updates, send us an email at <a href="https://opencollective.com/redirect?url=mailto%3Ahello%40oscollective.org">hello@oscollective.org</a>.</p>]]></content><author><name>Grace Powers</name></author><summary type="html"><![CDATA[Hi OSC community, we hope August is treating you well! This month, we’re excited to introduce a new section to our monthly updates: “What We’re Reading.” We hope you enjoy it! Without further ado…]]></summary></entry><entry><title type="html">Tips: an independent, sustainable future for the Open Collective platform</title><link href="https://blog.oscollective.org/2026/08/07/tips-an-independent-sustainable-future-for-the-open-collective-platform1/" rel="alternate" type="text/html" title="Tips: an independent, sustainable future for the Open Collective platform" /><published>2026-08-07T09:14:42+00:00</published><updated>2026-08-07T09:14:42+00:00</updated><id>https://blog.oscollective.org/2026/08/07/tips-an-independent-sustainable-future-for-the-open-collective-platform1</id><content type="html" xml:base="https://blog.oscollective.org/2026/08/07/tips-an-independent-sustainable-future-for-the-open-collective-platform1/"><![CDATA[<p>_You are receiving this message because you are an administrator of at least one project hosted by Open Source Collective on the Open Collective platform. We are letting you know that you may see a request for a ‘platform tip’ on a small proportion of donations to your Collective(s) over the coming weeks as we explore an independent way to sustain the platform on which we all depend. Read on for more…
_
<strong>Background</strong>
Open Source Collective (OSC) is the non-profit organisation that manages the financial, operational, and legal requirements on behalf of over 2,500 open source communities, including yours. In 2024, we led the acquisition of the Open Collective platform from Open Collective Inc. The Open Collective platform is now owned and operated by Open Finance Consortium (OFiCo): a non-profit consortium of its biggest users, all of whom are themselves non-profits.</p>

<p>Since the acquisition, OSC has provided significant financial support to OFiCo as it finds its feet and re-launches its core product. That support has come with a meaningful cost to OSC, limiting the services we can offer and our capacity to engage in initiatives that matter to our member projects. Now, as OSC reduces its financial commitment, OFiCo is taking steps to establish itself as a financially independent, sustainable non-profit by turning to the one funding source that can reliably make up the difference: optional tips.</p>

<p>Over the decade, optional tips have proven to be the most cost-effective, reliable, and sustainable way to cover the cost of maintaining the Open Collective platform. Open Source Collective is the only host organisation not to include a request for an optional tip in the contribution flow. We are also the largest host organisation on the platform, receiving US $6m in crowdfunding contributions per year on behalf of our member projects. Requesting an optional tip on those donations lowers the cost of using the platform for communities like yours and hosts like ours.</p>

<p><strong>What we’re doing</strong>
Over the past six weeks, we have tested tips with six of our largest open source communities. Our data shows that contributors tip with no statistically significant reduction in contributions to the receiving Collective. These findings align with data we see across the platform, including within open source communities hosted by other organisations. Most importantly, projections show that donors to OSC-hosted projects would collectively cover over half of the annual cost to develop and maintain the platform.</p>

<p><strong>Next steps</strong>
The next phase of our test will corroborate these results at scale, demonstrating to our member Collectives that requesting an optional tip is a near-zero-risk way of supporting the platform on which we all depend. Over the next few weeks, you may see a request for an optional tip on contributions to your Collective while we collect more data from a small proportion of donations across all our Collectives.</p>

<p><strong>Our promise to member projects</strong>
We are doing all we can to ensure that our member Collectives will not be adversely impacted by this change while still providing for an independent, sustainable future for the platform on which we all depend. If we see a demonstrable negative impact on donations to our projects, we will pursue alternative arrangements.</p>

<p>With this approach, the money OSC saves on platform costs will be reinvested in our mission: developing our services, investing significantly in our public policy, tools, support, and other initiatives intended to keep our collectives’ overhead low. That’s the outcome we’re aiming for, and it’s the primary reason we’re moving to tips.</p>

<p><strong>Feedback</strong>
If a tip in your donation flow is a genuine dealbreaker for you, one that would make you consider leaving Open Source Collective, please tell us. That’s not an outcome we want. We’d rather talk it through with you than lose you so please, email notips@opensourcecollective.org to discuss this with the team.</p>]]></content><author><name>Benjamin Nickolls</name></author><summary type="html"><![CDATA[_You are receiving this message because you are an administrator of at least one project hosted by Open Source Collective on the Open Collective platform. We are letting you know that you may see a request for a ‘platform tip’ on a small proportion of donations to your Collective(s) over the coming weeks as we explore an independent way to sustain the platform on which we all depend. Read on for more… _ Background Open Source Collective (OSC) is the non-profit organisation that manages the financial, operational, and legal requirements on behalf of over 2,500 open source communities, including yours. In 2024, we led the acquisition of the Open Collective platform from Open Collective Inc. The Open Collective platform is now owned and operated by Open Finance Consortium (OFiCo): a non-profit consortium of its biggest users, all of whom are themselves non-profits.]]></summary></entry><entry><title type="html">OSC Community Update: June 2026</title><link href="https://blog.oscollective.org/2026/07/16/osc-community-update-june-2026/" rel="alternate" type="text/html" title="OSC Community Update: June 2026" /><published>2026-07-16T19:34:56+00:00</published><updated>2026-07-16T19:34:56+00:00</updated><id>https://blog.oscollective.org/2026/07/16/osc-community-update-june-2026</id><content type="html" xml:base="https://blog.oscollective.org/2026/07/16/osc-community-update-june-2026/"><![CDATA[<p>Hi, OSC community! It’s been a few months since our last update while some of our team was out of the office, but we’re back and excited to reconnect through our monthly updates! We hope everyone is having a great July so far. Without further ado, let’s dive in! </p>

<h3 id="-announcements-"><strong>📣 Announcements 📣</strong> </h3>

<p><strong>Got a vendor or compliance questionnaire? We can help.</strong> </p>

<p>If you receive a risk assessment, vendor questionnaire, or compliance form from a company, feel free to forward it to us. These are common, but designed for traditional vendors and don’t map cleanly to fiscally-hosted open source projects. </p>

<p>Open Source Collective can complete the sections that relate to us as the legal and financial entity (e.g. organizational, financial, or compliance questions), and we can help clarify our relationship and how to position your project as an independent open source community. For technical or project-specific questions, we’ll coordinate with you as needed—or you can respond directly if you prefer. </p>

<p>When in doubt, just send it our way at <a href="https://opencollective.com/redirect?url=mailto%3Ahello%40oscollective.org">hello@oscollective.org</a> and we’ll take a look. </p>

<p><strong>ICYMI: updates to our terms of fiscal sponsorship</strong> </p>

<p>Back in April, we shared an update with hosted project admins about changes to our Protocols, the operational processes attached to our Terms of Fiscal Sponsorship. </p>

<p>These updates better reflect how we work with hosted projects today and provide additional clarity around our policies and processes. </p>

<p>If you’re a hosted project admin and missed the announcement, you can read it here (login required with an Open Collective account that has admin access to your OSC-hosted project): <a href="https://opencollective.com/opensource/updates/notice-of-update-to-protocols-part-of-our-terms">https://opencollective.com/opensource/updates/notice-of-update-to-protocols-part-of-our-terms</a> </p>

<p><strong>Anti-money laundering and financial integrity statement</strong> </p>

<p>We’ve rewritten and updated our public external policy on fraud prevention, now called our Anti-Money Laundering &amp; Financial Integrity Statement. </p>

<p>This document provides a high level overview for external audiences of our commitment to protecting the integrity of funds entrusted to Open Source Collective on behalf of our hosted member projects. It explains how we work to prevent the misuse of funds, detect suspicious activity, and comply with applicable laws and best practices. </p>

<p>You can read it here: <a href="https://docs.oscollective.org/about-osc/anti-money-laundering-and-financial-integrity-statement">https://docs.oscollective.org/about-osc/anti-money-laundering-and-financial-integrity-statement</a> </p>

<p><strong>UN Open Source week recap</strong> </p>

<p>It was great to see so many people from our hosted projects throughout the week. This conference is an important reminder of how much of the infrastructure conversation happening at the UN level connects to the day-to-day maintenance work we all support. </p>

<p>A few highlights: </p>

<ul>
  <li>The OSPOs for Good talks on Thursday are always inspiring. This is our third year attending this event, and there is growth in explicit reference to open source as a matter of national sovereignty among government OSPOs and ministries.</li>
  <li>A big shout out to <strong>Ruth Ikegah</strong>, who co-led the community track on capacity building. Capacity building doesn’t get the spotlight that AI or DPI policy does at events like this, but it’s the work that determines whether any of it is sustainable!</li>
  <li>Don’t forget to include a funding.yaml file in your repository to make getting paid easier. Hat tip - Andrew Nesbitt (<a href="https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/displaying-a-sponsor-button-in-your-repository">https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/displaying-a-sponsor-button-in-your-repository</a>)</li>
</ul>

<p>This year, our Executive Director, Lauren Gardner, joined a panel, “Public Investment for Open Source Infrastructure: The Sovereign Tech Agency Model in a Global Ecosystem” — alongside Tim Lehnen (Drupal Association), Qianqian Ye (Processing Foundation), and Bastien Guerry (Software Heritage), hosted by the Sovereign Tech Agency. We dug into what it actually takes to build institutional capacity for open source infrastructure: funding models, corporate contribution pathways, and the case for evidence-based policy. The throughline for us was that we shift the conversation from “why fund open source” to “how” — which is exactly the work we’re excited to be in.
 
As always, it was great to reconnect with people across the ecosystem and keep finding new ways we can be of help.
 
**Upcoming event: FOSSY in Vancouver Canada (August 6-9)
** 
<a href="https://opencollective.com/redirect?url=https%3A%2F%2F2026.fossy.ca%2F">FOSSY</a> is taking place in Vancouver, August 6-9, 2026. This is a community focused conference focused on the creation and impact of free and open source software, uplifting contributors of all experience.</p>

<p>As a reminder, Open Source Collective can help admins of hosted projects attend conferences like FOSSY. You can learn more about our conference support policy here: <a href="https://docs.oscollective.org/for-hosted-member-projects/conference-policy">https://docs.oscollective.org/for-hosted-member-projects/conference-policy</a>
 </p>

<h3 id="community-highlights-updates-and-announcements-"><strong>✨Community Highlights, Updates, and Announcements ✨</strong></h3>

<p> 
Between March - June, OSC accepted <strong>95</strong> new Collectives to OSC! Welcome to:
 </p>

<ul>
  <li>Abstract Play, AetherSDR, Agent Threat Rules, AnyCrawl, Apich Organization, arjun trivedi</li>
  <li>Batear, Born ML — Pure Go Machine Learning Framework</li>
  <li>CadQuery, chainlit, Chiri, Colibri Social, CoreGX — High-Performance Pure Go Libraries, Cpeak,</li>
  <li>Dale Study, Darling, DDLSim-Lab Research groupe, DevCard, Dispatcharr, DocsGPT, Draupnir</li>
  <li>Editor Code Assistant, Emissary,eXpertiZe</li>
  <li>FaFa Runner, fastlane, Fenn, fentas peers, Floatpane, Free Ink</li>
  <li>GlycemicGPT, GoGPU — Pure Go GPU Ecosystem, Grimmory, Gurujada</li>
  <li>heripo project, Hookprobe, HWUT - Unit Tests</li>
  <li>ImWeb, Innovation Information Initiative</li>
  <li>Kotlin User Group Chennai, Kubb</li>
  <li>Libre.fm, Lugaralgum</li>
  <li>Max Katz, MetAudits, moreSwift, Morphe</li>
  <li>Namastack Outbox, Nano Collective, Navidrome, NuvioMedia</li>
  <li>Octopus Code Review, OoTMM, OpenCut, OpenDCS, opengolfapi, OpenOSINT, OpenVersus</li>
  <li>PacaAI, Padding Labs, Paseo, PegaProx, PicGuard</li>
  <li>qdm12, QS DMSS</li>
  <li>Refferq, Rux Language</li>
  <li>Sable, Scryer Media, secureblue, SEM TECH, Shadcn Labs, single-spa-angular, Skforecast, Socketio4j, SourceBans++, sysprog21, SystemsDK</li>
  <li>TablePro, TaurusTLS Developers, Termix, The Hitchhiker’s Guide to Online Anonymity, Transmute</li>
  <li>UbuCon Latinoamérica 2026</li>
  <li>Writermark</li>
  <li>Your Cove</li>
  <li>zenithbuild, Ziex, and ZoneTree!</li>
</ul>]]></content><author><name>Grace Powers</name></author><summary type="html"><![CDATA[Hi, OSC community! It’s been a few months since our last update while some of our team was out of the office, but we’re back and excited to reconnect through our monthly updates! We hope everyone is having a great July so far. Without further ado, let’s dive in! ]]></summary></entry><entry><title type="html">Notice of update to Protocols (part of our Terms)</title><link href="https://blog.oscollective.org/2026/04/10/notice-of-update-to-protocols-part-of-our-terms/" rel="alternate" type="text/html" title="Notice of update to Protocols (part of our Terms)" /><published>2026-04-10T12:43:47+00:00</published><updated>2026-04-10T12:43:47+00:00</updated><id>https://blog.oscollective.org/2026/04/10/notice-of-update-to-protocols-part-of-our-terms</id><content type="html" xml:base="https://blog.oscollective.org/2026/04/10/notice-of-update-to-protocols-part-of-our-terms/"><![CDATA[]]></content><author><name>Benjamin Nickolls</name></author><summary type="html"><![CDATA[]]></summary></entry><entry><title type="html">On KYC checks and Persona</title><link href="https://blog.oscollective.org/2026/03/13/on-kyc-checks-and-persona/" rel="alternate" type="text/html" title="On KYC checks and Persona" /><published>2026-03-13T18:09:22+00:00</published><updated>2026-03-13T18:09:22+00:00</updated><id>https://blog.oscollective.org/2026/03/13/on-kyc-checks-and-persona</id><content type="html" xml:base="https://blog.oscollective.org/2026/03/13/on-kyc-checks-and-persona/"><![CDATA[<p>As a nonprofit fiscal host, OSC supports over 2,500 open-source projects worldwide. Last year, as part of ongoing improvements to our risk and compliance processes, we began verifying the identity of users requesting payments when:</p>

<ul>
  <li>When we cannot verify that the person requesting payment is the holder of an account</li>
  <li>When a payment involves a nation sanctioned by the US government</li>
  <li>When a payment provider requires additional verification</li>
</ul>

<p>We identified users once and stored the results as ‘pass’ or ‘fail’. We do <strong>not send user data from our platform to Persona</strong>, we do not store identity documents, we performed these checks on a fraction of a percentage of the payments we process, and only in the cases listed above. </p>

<p>Like all organizations that transfer money, we are subject to the U.S. Anti-Money Laundering (AML) regulations and sanction requirements set by the <a href="https://opencollective.com/redirect?url=https%3A%2F%2Fofac.treasury.gov%2F">Office of Foreign Assets Control</a> (“OFAC”) of the US Department of the Treasury. These rules require organizations to verify the identity of recipients in certain cases to reduce the risk of fraud, identity theft, sanctions violations, or other financial crimes.</p>

<p>Last year we paid maintainers in 96 countries, including maintainers in active warzones where our primary payment providers refuse to operate. As a team of five, we do not have the resources to validate the identities across such a wide range of nations. We chose a service provider to help streamline our operations. After a review of available solutions, we chose Persona, predominantly for its customer-defined data retention policy, which we set to delete identifying documents once we verify a result. </p>

<p>**
On Persona**</p>

<p>Persona has answered questions regarding their data sharing, their government contracts, and their relationship with Peter Thiel and Palantir. We are not here to parrot their responses. Our review did not extend to Persona’s investors and the stakeholders in those investment vehicles. While that is our error, and an error we will correct, we feel it’s necessary to point out that most providers in this space <em>will</em> most likely offer their services to government agencies, and may also be funded by institutions we do not wish to support. Capitalism is a complex web, and we will do our best to select tools that align with our values, however, we cannot always guarantee we will achieve that outcome.</p>

<p>**What we are doing
**</p>

<p>Most of our requests to verify identities come from requests to pay PayPal addresses. PayPal operates its own verification program, which we will utilize for those who cannot accept payments by bank transfer. </p>

<p>In addition, we will be identifying alternative providers for identity verification services, both in the US and in Europe, in order to give our European users the additional peace of mind that their identity documents do not pass into American processors. </p>

<p>Finally, we will halt the use of Persona for identity verification until we are able to implement the alternative arrangements described above. </p>

<p>Thank you to everyone in our community who shared their perspective. We hear you, and we are grateful to be a part of a community that cares so deeply about transparency and accountability. Openness is at the heart of everything we do.</p>

<p>The folks at OSC</p>

<p>-Lauren, Ben, Grace, Sourav, and Caitlin</p>

<p>Helpful link:</p>

<ul>
  <li>What is fiscal hosting - <a href="https://docs.oscollective.org/welcome-and-introduction-to-osc/what-is-fiscal-hosting">https://docs.oscollective.org/welcome-and-introduction-to-osc/what-is-fiscal-hosting</a></li>
</ul>]]></content><author><name>Lauren Gardner</name></author><summary type="html"><![CDATA[As a nonprofit fiscal host, OSC supports over 2,500 open-source projects worldwide. Last year, as part of ongoing improvements to our risk and compliance processes, we began verifying the identity of users requesting payments when:]]></summary></entry><entry><title type="html">February Update for OSC</title><link href="https://blog.oscollective.org/2026/03/09/february-update-for-osc/" rel="alternate" type="text/html" title="February Update for OSC" /><published>2026-03-09T19:30:32+00:00</published><updated>2026-03-09T19:30:32+00:00</updated><id>https://blog.oscollective.org/2026/03/09/february-update-for-osc</id><content type="html" xml:base="https://blog.oscollective.org/2026/03/09/february-update-for-osc/"><![CDATA[<h3 id="-from-osc">🟣 <strong>From OSC</strong> </h3>

<p><strong>Berlin</strong>: <strong>FOSS Backstage Discount, OSC Pizza Party and Team Offsite (Mar 16–21)</strong></p>

<p>OSC will be at <a href="https://opencollective.com/redirect?url=https%3A%2F%2F26.foss-backstage.de%2F">FOSS Backstage</a>, in Berlin Mar 16th and 17th. We have a limited number of discount codes available for projects hosted by OSC. If you’re interested in attending, please email us and we’ll share a code with you while they last.</p>

<p>We’re also going to be having a Friends of OSC Pizza Party on Tuesday the 17th and would love to invite  OSC admins, maintainers, and anyone else in our community! If you’re in or around Berlin, please let us know here so we can invite you: <a href="https://opencollective.com/redirect?url=https%3A%2F%2Foscollective.fillout.com%2Ft%2FtRVBmxhqLous">https://oscollective.fillout.com/t/tRVBmxhqLous</a></p>

<p>The OSC team will also be using this opportunity for an OSC team offsite for the rest of that week, which is always a joy since we’re spread across the world. We’ll still process expenses and respond to tickets, but responses and processing times may be slightly slower.</p>

<p><strong>Meshtastic 101</strong>
Last month, part of the <a href="https://opencollective.com/meshtastic">Meshtastic</a> crew joined our Spotlight call to chat about the mesh networking ecosystem built on LoRa, enabling long-distance, low-bandwidth communication for things like messaging, location tracking, and sensor data. </p>

<p>Additionally, they talked about some very interesting real-world use cases from their community, how they handle community development, and how they manage AI-generated pull requests.</p>

<p>If you missed it, you can watch the recording here: <a href="https://opencollective.com/redirect?url=https%3A%2F%2Fyoutu.be%2FpiFssDbffMQ">https://youtu.be/piFssDbffMQ</a></p>

<p> </p>

<h3 id="-community-highlights-updates-and-announcements">**🌍 Community Highlights, Updates, and Announcements</h3>
<p>**</p>

<p>In February, we accepted <strong>19</strong> new Collectives to OSC! Welcome to Antdv Next, ApeWorX, Booming Music, CompNeuroSociety, Devi &amp; Muna, Django bolt, getbindu, invokevirtual, LLM4S, Margin, ngx-lottie, nutriverse, Papra, PlainHub Open Source, PurrNet, Telegem, Vuepont, WlxTeam, and Xcode Releases.</p>

<h3 id="-opportunities-funding-and-resources">✨ <strong>Opportunities, Funding, and Resources</strong></h3>

<p><em>These opportunities are not managed by OSC. Some may involve us in some way or come from organizations we work with, while others are resources shared with us and we cannot vouch for. Please review the details and do your own due diligence before applying or participating.</em>
 </p>

<ul>
  <li>
    <p>Applications are open for Session 4 of the <strong>GitHub Secure Open Source Fund</strong>, which supports projects working to improve the security of the open source ecosystem. Projects and maintainers working on open source security are invited to apply. Session 4 begins <strong>April 2026</strong>. Learn more and apply here: <a href="https://github.com/open-source/github-secure-open-source-fund">https://github.com/open-source/github-secure-open-source-fund</a></p>
  </li>
  <li>
    <p>Claude is offering <strong>6 months of free Claude Max access</strong> for eligible open source projects. If your project is looking for AI tooling, you can learn more and apply here: <a href="https://opencollective.com/redirect?url=https%3A%2F%2Fclaude.com%2Fcontact-sales%2Fclaude-for-oss">https://claude.com/contact-sales/claude-for-oss</a></p>
  </li>
  <li>
    <p><strong>Open Source Endowment</strong> has launched to support funding for open source projects through an endowment model. Projects can be nominated for funding through this program. Learn more here: <a href="https://opencollective.com/redirect?url=https%3A%2F%2Fendowment.dev%2F">https://endowment.dev/</a></p>
  </li>
  <li>
    <p>Applications are open for the <strong>Sovereign Tech Fellowship</strong>, which supports maintainers and contributors working on critical open source infrastructure. This year, community managers and technical writers are also eligible. Learn more here: <a href="https://opencollective.com/redirect?url=https%3A%2F%2Fwww.sovereign.tech%2Fnews%2F2026-fellowship-applications-open">https://www.sovereign.tech/news/2026-fellowship-applications-open</a></p>
  </li>
</ul>

<p>That’s all for this month! As always, if you’d like to get in touch about any of the above or anything else, feel free to email us at hello@oscollective.org.</p>]]></content><author><name>Grace Powers</name></author><summary type="html"><![CDATA[🟣 From OSC ]]></summary></entry><entry><title type="html">January Update for OSC</title><link href="https://blog.oscollective.org/2026/02/13/january-update-for-osc/" rel="alternate" type="text/html" title="January Update for OSC" /><published>2026-02-13T18:31:16+00:00</published><updated>2026-02-13T18:31:16+00:00</updated><id>https://blog.oscollective.org/2026/02/13/january-update-for-osc</id><content type="html" xml:base="https://blog.oscollective.org/2026/02/13/january-update-for-osc/"><![CDATA[<h3 id="-announcements-"><strong>📣 Announcements 📣</strong></h3>

<h3 id="happening-next-week-meshtastic-101"><strong>Happening Next Week: Meshtastic 101</strong> </h3>

<p>There’s been a bit of chat about mesh networks lately, so we thought it’d be nice to sit down with <a href="https://opencollective.com/redirect?url=https%3A%2F%2Fmeshtastic.org%2F">Meshtastic</a> and learn more!</p>

<p>Curious and want to learn more? Come hang out.</p>

<p><strong>Thursday, February 19, 2026</strong>
<strong>9am PT / 12pm ET / 5pm / 10:30pm IST</strong>
(Need another timezone? You can check here: <a href="https://opencollective.com/redirect?url=https%3A%2F%2Feverytimezone.com%2Fs%2F06dff4af">https://everytimezone.com/s/06dff4af</a>)</p>

<p><a href="https://opencollective.com/opensource/events/intro-to-meshtastic-b23970f0"><strong>RSVP here</strong></a> 
Once you RSVP, you’ll receive the link to join. If you’d like a calendar invite, just let us know.</p>

<p>###
<strong>GitHub Sponsors Payout Update</strong></p>

<p>If you receive GitHub Sponsorsors funding through Open Source Collective, you may have noticed a smll additional amount reflected in your project’s balance. This deposit was due to an issue GitHub Sponsors experienced on their end with payouts to OSC in July and September 2025, which resulted in a small number of Collectives receiving slightly less than their expected payout amounts for those months. OSC identified the issue and raised it with the Github Sponsors team, who resolved the issue. The missing funds have since been allocated.
 
We appreciate the GitHub Sponsors team for resolving the issue. If you have any questions, please reach out.</p>

<h3 id="invoices-and-supplier-portals"><strong>Invoices and Supplier Portals</strong> </h3>

<p>As your Collective plans their 2026 funding strategy, please note that OSC can issue formal invoices and submit invoices through a variety of supplier and procurement portals. Being able to meet these requirements can help unlock funding from organizations that are only able to pay via invoice or require vendors to go through formal procurement systems. If you’re speaking with a potential funder who has requested either of these requirements, or think it might open up an opportunity for your project, please reach out. </p>

<h3 id="icymi-repurposing-stranded-funds-in-support-of-critical-open-source-infrastructure"><strong>ICYMI: Repurposing Stranded Funds in Support of Critical Open Source Infrastructure</strong> </h3>

<p>We’ve wrapped up our outreach to projects that had been inactive or were no longer within the scope of our hosting agreement, and have completed the redistribution of those funds to ensure alignment with our mission. We wrote a post outlining how we approached the process here: <a href="https://opencollective.com/opensource/updates/activating-stranded-funds-to-support-critical-open-source">https://opencollective.com/opensource/updates/activating-stranded-funds-to-support-critical-open-source</a></p>

<h3 id="fosdem-talk"><strong>FOSDEM Talk</strong></h3>

<p>At FOSDEM, our very own Benjam joined the wonderful Shannon from Open Collective to share the story of how the Open Collective platform transitioned from a for-profit company to a nonprofit, and where we, OSC, fit into that equation. </p>

<p>People often assume OSC and Open Collective are one and the same, but that’s not quite the case. The talk does a great job unpacking the different entities and how they relate to one another. </p>

<p>If you’ve ever wondered who does what, the governance models at play, how we collaborate while remaining distinct orgs, and what changed with the new model, this session should help connect the dots.</p>

<p>You can watch here: <a href="https://opencollective.com/redirect?url=https%3A%2F%2Fmirror.cyberbits.eu%2Ffosdem%2F2026%2Fud2218a%2FUQUCFW-the_buyout_how_the_open_source_community_liberated_its_own_platform.av1.webm">https://mirror.cyberbits.eu/fosdem/2026/ud2218a/UQUCFW-the_buyout_how_the_open_source_community_liberated_its_own_platform.av1.webm</a></p>

<p>[<img src="https://opencollective-production.s3.us-west-1.amazonaws.com/update/bc9b595b-ee57-4f61-8c18-c2c90c6f7389/image.png" alt="" /></p>

<p>](https://opencollective-production.s3.us-west-1.amazonaws.com/update/bc9b595b-ee57-4f61-8c18-c2c90c6f7389/image.png)</p>

<h3 id="foss-backstage--ticket-discount-and-osc-collective-meetup"><strong>FOSS Backstage – Ticket Discount and OSC Collective Meetup</strong></h3>

<p>OSC will be at one of our favorite events, <a href="https://opencollective.com/redirect?url=https%3A%2F%2F26.foss-backstage.de%2F">FOSS Backstage</a>, in Berlin next month. We have a limited number of discount codes available for projects hosted by OSC. If you’re interested in attending, please email us and we’ll share a code with you while they last. </p>

<p>We’re also gauging interest in an OSC meetup during the week of the conference. If you’re interested in attending, please fill out this quick form so we can plan accordingly:  <a href="https://opencollective.com/redirect?url=https%3A%2F%2Foscollective.fillout.com%2Ft%2FuiMGWggT9fus">https://oscollective.fillout.com/t/uiMGWggT9fus</a> </p>

<h3 id="staying-up-to-date-on-the-cra"><strong>Staying Up To Date on</strong> <strong>The</strong> <strong>CRA</strong></h3>

<p>With ongoing discussion about the <a href="https://opencollective.com/redirect?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FCyber_Resilience_Act">Cyber Resilience Act</a> (CRA), OSC is closely monitoring how things evolve and having ongoing conversations with folks across ecosystem. If you’d like to be involved in a potential OSC-community working group about the CRA, let us know via email and we’ll keep you in the loop.
 </p>

<h3 id="community-highlights-updates-and-announcements-"><strong>✨Community Highlights, Updates, and Announcements ✨</strong></h3>

<p>In January, we welcomed <strong>20</strong> new projects: Cloud Native Santo Domingo, drawnix<strong>,</strong> Eslint Config Airbnb Extended, Forge SQL ORM, Listenarr, Lodash<strong>,</strong> Mapterhorn, NetCord, npmx, Nylo<strong>,</strong> oAuthlib, Rust Compressed Archive Collective, Sonicjs, Stack Trace Decoroutinator, Steam Deck Homebrew, UnRS, Upstream RPM Distributions, vue zone, worm-blossom, z-libs! </p>

<p>Want to get in touch with us about anything above? Reach out to our team at hello@oscollective.org.</p>]]></content><author><name>Grace Powers</name></author><summary type="html"><![CDATA[📣 Announcements 📣]]></summary></entry></feed>