Pathways for Open Collective’s “Exit to Community”

<!DOCTYPE html> <html lang="en"> <head> <title>Pathways for Open Collective’s “Exit to Community”</title> <meta charset="utf-8" /> <meta http-equiv="X-UA-Compatible" content="IE=edge" /> <meta name="HandheldFriendly" content="True" /> <meta name="viewport" content="width=device-width, initial-scale=1.0" /> <link rel="preload" as="style" href="https://blog.opencollective.com/assets/built/screen.css?v=4b4d6947a3" /> <link rel="preload" as="script" href="https://blog.opencollective.com/assets/built/casper.js?v=4b4d6947a3" /> <link rel="stylesheet" type="text/css" href="https://blog.opencollective.com/assets/built/screen.css?v=4b4d6947a3" /> <link rel="icon" href="https://blog.opencollective.com/content/images/size/w256h256/2019/08/opencollectivelogo-sq.png" type="image/png"> <link rel="canonical" href="https://blog.opencollective.com/exit-to-community-part-2/"> <meta name="referrer" content="no-referrer-when-downgrade"> <link rel="amphtml" href="https://blog.opencollective.com/exit-to-community-part-2/amp/"> <meta property="og:site_name" content="Open Collective"> <meta property="og:type" content="article"> <meta property="og:title" content="Pathways for Open Collective’s “Exit to Community”"> <meta property="og:description" content="(Stay up to date on our journey here.) How might we free Open Collective for the commons? Part 2 of … The not-so-secret dream of our strange beast called Open Collective is to be infrastructure for the commons, owned by our community, which I talked about in part one. Open Collective"> <meta property="og:url" content="https://blog.opencollective.com/exit-to-community-part-2/"> <meta property="og:image" content="https://blog.opencollective.com/content/images/size/w1200/2021/11/pexels-rodolfo-quir-s-2219024.jpg"> <meta property="article:published_time" content="2021-11-24T10:19:49.000Z"> <meta property="article:modified_time" content="2024-06-20T12:54:20.000Z"> <meta property="article:tag" content="news"> <meta property="article:tag" content="e2c"> <meta name="twitter:card" content="summary_large_image"> <meta name="twitter:title" content="Pathways for Open Collective’s “Exit to Community”"> <meta name="twitter:description" content="(Stay up to date on our journey here.) How might we free Open Collective for the commons? Part 2 of … The not-so-secret dream of our strange beast called Open Collective is to be infrastructure for the commons, owned by our community, which I talked about in part one. Open Collective"> <meta name="twitter:url" content="https://blog.opencollective.com/exit-to-community-part-2/"> <meta name="twitter:image" content="https://blog.opencollective.com/content/images/size/w1200/2021/11/pexels-rodolfo-quir-s-2219024.jpg"> <meta name="twitter:label1" content="Written by"> <meta name="twitter:data1" content="Pia Mancini"> <meta name="twitter:label2" content="Filed under"> <meta name="twitter:data2" content="news, e2c"> <meta name="twitter:site" content="@opencollect"> <meta property="og:image:width" content="1200"> <meta property="og:image:height" content="800"> <script type="application/ld+json"> { "@context": "https://schema.org", "@type": "Article", "publisher": { "@type": "Organization", "name": "Open Collective", "url": "https://blog.opencollective.com/", "logo": { "@type": "ImageObject", "url": "https://blog.opencollective.com/content/images/2022/07/03--Logotype.png" } }, "author": { "@type": "Person", "name": "Pia Mancini", "image": { "@type": "ImageObject", "url": "https://blog.opencollective.com/content/images/2019/08/0_8_gxhV1zl0LV28KY--1-.jpeg", "width": 640, "height": 640 }, "url": "https://blog.opencollective.com/author/pia/", "sameAs": [] }, "headline": "Pathways for Open Collective’s “Exit to Community”", "url": "https://blog.opencollective.com/exit-to-community-part-2/", "datePublished": "2021-11-24T10:19:49.000Z", "dateModified": "2024-06-20T12:54:20.000Z", "image": { "@type": "ImageObject", "url": "https://blog.opencollective.com/content/images/size/w1200/2021/11/pexels-rodolfo-quir-s-2219024.jpg", "width": 1200, "height": 800 }, "keywords": "news, e2c", "description": "(Stay up to date on our journey here.)\n\nHow might we free Open Collective for the commons? Part 2 of …\n\nThe not-so-secret dream of our strange beast called Open Collective is to be infrastructure for the commons, owned by our community, which I talked about in part one.\n\nOpen Collective is committed to making that dream a reality. But ownership can be tricky. How can a for-profit company be owned by everyone? To pull it off, we need a legal structure that allows the community to become stewards ", "mainEntityOfPage": "https://blog.opencollective.com/exit-to-community-part-2/" } </script> <meta name="generator" content="Ghost 5.101"> <link rel="alternate" type="application/rss+xml" title="Open Collective" href="https://blog.opencollective.com/rss/"> <script defer src="https://cdn.jsdelivr.net/ghost/sodo-search@~1.5/umd/sodo-search.min.js" data-key="6fa7e95c2c5c499f17a4faea1d" data-styles="https://cdn.jsdelivr.net/ghost/sodo-search@~1.5/umd/main.css" data-sodo-search="https://opencollective.ghost.io/" data-locale="en" crossorigin="anonymous"></script> <link href="https://blog.opencollective.com/webmentions/receive/" rel="webmention"> <script defer src="/public/cards.min.js?v=4b4d6947a3"></script> <link rel="stylesheet" type="text/css" href="/public/cards.min.css?v=4b4d6947a3"> <script defer src="/public/comment-counts.min.js?v=4b4d6947a3" data-ghost-comments-counts-api="https://blog.opencollective.com/members/api/comments/counts/"></script><style>:root {--ghost-accent-color: #0C2D66;}</style> <style> /* Hide the feature image */ figure.post-full-image { display: none; } .article-image { display: none; } /* Display "mixtape" cross-linking embeds correctly */ .mixtape { box-shadow: 0 1px 4px rgba(0, 0, 0, 0.1), inset 0 0 0 1px rgba(0, 0, 0, 0.1); width: 100%; } a.mixtape-url { display: flex; justify-content: space-between; align-items: center; width: 100%; box-shadow: none; padding: 1px; } a.mixtape-url:hover { color: inherit; } .mixtape-title { line-height: 1.5em; } .mixtape-content{ padding: 16px 44px; font-size: 1.7rem; } .mixtape-description { line-height: 1.5em; opacity: 0.8; } .gh-head-menu { color: black; } .has-cover .site-description { color:black; } .has-cover:not(.home-template) .gh-head { background-color: #cbddf8; } </style> <script defer data-domain="blog.opencollective.com" src="https://plausible.io/js/plausible.js"></script> </head> <body class="post-template tag-news tag-e2c is-head-left-logo has-cover"> <div class="viewport"> <header id="gh-head" class="gh-head outer"> <div class="gh-head-inner inner"> <div class="gh-head-brand"> <a class="gh-head-logo" href="https://blog.opencollective.com"> <img src="https://blog.opencollective.com/content/images/2022/07/03--Logotype.png" alt="Open Collective"> </a> <button class="gh-search gh-icon-btn" aria-label="Search this site" data-ghost-search><svg xmlns="http://www.w3.org/2000/svg" fill="none" viewBox="0 0 24 24" stroke="currentColor" stroke-width="2" width="20" height="20"><path stroke-linecap="round" stroke-linejoin="round" d="M21 21l-6-6m2-5a7 7 0 11-14 0 7 7 0 0114 0z"></path></svg></button> <button class="gh-burger" aria-label="Main Menu"></button> </div> <nav class="gh-head-menu"> <ul class="nav"> <li class="nav-website"><a href="https://opencollective.com">Website</a></li> <li class="nav-case-studies"><a href="https://blog.opencollective.com/tag/case-studies/">Case Studies</a></li> <li class="nav-news"><a href="https://blog.opencollective.com/tag/news/">News</a></li> <li class="nav-how-to"><a href="https://blog.opencollective.com/tag/how-to/">How-To</a></li> <li class="nav-help"><a href="https://docs.opencollective.com">Help</a></li> </ul> </nav> <div class="gh-head-actions"> <button class="gh-search gh-icon-btn" aria-label="Search this site" data-ghost-search><svg xmlns="http://www.w3.org/2000/svg" fill="none" viewBox="0 0 24 24" stroke="currentColor" stroke-width="2" width="20" height="20"><path stroke-linecap="round" stroke-linejoin="round" d="M21 21l-6-6m2-5a7 7 0 11-14 0 7 7 0 0114 0z"></path></svg></button> </div> </div> </header> <div class="site-content"> <main id="site-main" class="site-main"> <article class="article post tag-news tag-e2c "> <header class="article-header gh-canvas"> <div class="article-tag post-card-tags"> <span class="post-card-primary-tag"> <a href="/tag/news/">news</a> </span> </div> <h1 class="article-title">Pathways for Open Collective’s “Exit to Community”</h1> <div class="article-byline"> <section class="article-byline-content"> <ul class="author-list instapaper_ignore"> <li class="author-list-item"> <a href="/author/pia/" class="author-avatar" aria-label="Read more of Pia Mancini"> <img class="author-profile-image" src="/content/images/size/w100/2019/08/0_8_gxhV1zl0LV28KY--1-.jpeg" alt="Pia Mancini" /> </a> </li> </ul> <div class="article-byline-meta"> <h4 class="author-name"><a href="/author/pia/">Pia Mancini</a></h4> <div class="byline-meta-content"> <time class="byline-meta-date" datetime="2021-11-24">Nov 24, 2021</time> <span class="byline-reading-time"><span class="bull">•</span> 6 min read</span> </div> </div> </section> </div> <figure class="article-image"> <img srcset="/content/images/size/w300/2021/11/pexels-rodolfo-quir-s-2219024.jpg 300w, /content/images/size/w600/2021/11/pexels-rodolfo-quir-s-2219024.jpg 600w, /content/images/size/w1000/2021/11/pexels-rodolfo-quir-s-2219024.jpg 1000w, /content/images/size/w2000/2021/11/pexels-rodolfo-quir-s-2219024.jpg 2000w" sizes="(min-width: 1400px) 1400px, 92vw" src="/content/images/size/w2000/2021/11/pexels-rodolfo-quir-s-2219024.jpg" alt="Pathways for Open Collective’s “Exit to Community”" /> </figure> </header> <section class="gh-content gh-canvas"> <p><em>(Stay up to date on our journey </em><a href="http://opencollective.com/e2c?ref=blog.opencollective.com"><em>here</em></a><em>.)</em></p><p><em>How might we free Open Collective for the commons? Part 2 of …</em></p><p>The not-so-secret dream of our strange beast called Open Collective is <strong>to be </strong><a href="http://opencollective.com/e2c?ref=blog.opencollective.com"><strong>infrastructure for the commons, owned by our community</strong></a>, which I talked about in<strong> </strong><a href="https://blog.opencollective.com/exit-to-community/">part one</a><strong>.</strong></p><p>Open Collective is committed to making that dream a reality. But ownership can be tricky. How can a for-profit company be owned by everyone? To pull it off, we need a <strong>legal structure</strong> that allows the community to become stewards of Open Collective <em>on behalf of</em> the commons. </p><p>This is where the fun part begins! This blog series, and an upcoming video series, will discuss how on earth we can make this work. </p><p>In this post, first I'll provide a high-level overview of a few interesting structures, along with some categories we are using to think them through. Then, I'll go a bit deeper on two structures that I feel are <em>not</em> right for Open Collective, to transparently share my thinking process. </p><h3 id="making-sense-of-what-we-need">Making sense of what we need</h3><p>At Open Collective, we use technology to bend legal structures and entities to fit the needs of communities, all over the world. We push the limits of what is doable to enable the biggest number of communities to successfully access and manage funding. </p><p>We want to engage you to co-create an ownership structure for the commons, which can fund itself for the future. The structure we choose will integrate our purpose and values into our legal DNA, future-proofing Open Collective for the long term.</p><p>We need to future-proof our purpose and mission with cultural, legal, financial, and technological structures that can provide:</p><ol><li><strong>Multi-stakeholder community governance</strong><br>Gives power to the community while (1) maintaining our efficiency, adaptability, resilience, and sustainability, and (2) accounting for a variety of stakeholders spread across disciplines and geographies, including employees, Fiscal Hosts, Collectives, funders, investors and individual contributors.</li><li><strong>Purpose protection</strong><br>Safeguards Open Collective’s integrity and purpose, protecting against sale, co-option, and subversion.</li><li><strong>Liquidity</strong><br>Harnesses capital (i.e., money) so that our impact-driven investors, founders, and employees can eventually exit confidently and reinvest in new social enterprises.</li><li><strong>Long term vision</strong><br>Orients Open Collective toward the long-term needs of our community and the world.</li></ol><p>That's a big mouthful, I know. We need to roll up our sleeves and get real with the thinking to land this. Here we go. </p><h3 id="where-do-we-look-for-ideas">Where do we look for ideas? </h3><p>Selling to workers and diverse users is what is known as an “Exit to Community”. While many brick-and-mortar companies have been <a href="https://www.owner2owners.nyc/success-stories?ref=blog.opencollective.com">successfully sold to their workers</a>, there is no clear roadmap for tech start-ups like Open Collective. </p><p>But we’re not afraid to get creative! <a href="https://www.colorado.edu/lab/medlab/2020/08/31/exit-community-community-primer?ref=blog.opencollective.com">New pathways are emerging</a>, and one of them—or some combination of them—may provide the answer we need.</p><p>Here are some ideas - and mostly questions - as we learn in public:</p><p><strong>Purchase by a federation of Fiscal Hosts</strong></p><p>We could be purchased by <a href="https://opencollective.com/hosts?ref=blog.opencollective.com">our Fiscal Hosts</a>, perhaps in the form of a federation like the <a href="https://en.wikipedia.org/wiki/Associated_Press?ref=blog.opencollective.com#Governance">Associated Press</a>. Fiscal Hosts already play an important role for the platform, and tend to have some key governance and community building capacities. This one was one of the first ideas that came to mind. </p><p>The questions we have are: Does it provide for community governance or ownership involving our full community of Collectives, funders, users, and employees? Can it provide the needed liquidity? Does is optimize for long term vision and future needs? Practically, coordinating of a consortium of that size, made up of many different types of organizations (not all of which are nonprofits), that spans multiple countries, means a level of complexity that could grind to a halt. Plus, it's not clear that Fiscal Hosts can provide the liquidity necessary to buy the company, or that this would the best use of their limited resources. </p><p>There's also another set of issues that are long term vision-related. If the platform that Collectives use to organize themselves is owned by Fiscal Hosts, we would be locking them into a certain power structure, a system where Fiscal Hosts hold control over the infrastructure Collectives rely on. </p><p><strong>Multi-stakeholder platform cooperative</strong></p><p>A cooperative is a democratically governed and jointly owned organization. "Multi-stakeholder" means that multiple types of members are involved in the ownership and governance of the platform.</p><p>In this model, both users and employees make decisions about the platform. For example, Fiscal Hosts and Collectives could elect a board of directors, who then hire management, who in turn hire the staff that create the Open Collective tech platform. The mission is held by a balance of groups. It seems it solves for community control, but how do we bake in the structure the purpose for the future? How do we accommodate ownership across thousands of individuals and communities around the world? </p><p><strong>Decentralized autonomous organization (DAO)</strong></p><p>Decentralized autonomous organizations, or DAOs, are organizations that are governed on the blockchain via the distribution of tokens (think shares that give you voting power). The “blockchain” refers to a secure, distributed ledger that verifies and stores information transparently, for all to see.</p><p>In a DAO, <a href="https://insight.openexo.com/daos-are-novel-but-not-new/?ref=blog.opencollective.com">like a cooperative</a>, every token holder has voting power. Different from a cooperative, this power is tied to the number of tokens a person holds. Tokens can be shared based on any method for assigning value or weighing contributions. . Because it's tech-enabled, it can more easily involve a large number of people from all over the world, and handle more complex stakeholder relationships. Members can be a diverse community stakeholders and it solves for global ownership because location doesn't matter. DAOs allow members to make proposals and be directly involved in organizational decisions so it should solve better for the future. Liquidity in theory is easier to access. Questions are, it negatively impacts less tech connected community members, depending on the arrangement volatility is an issue. Finally, how do we securely protect the purpose of Open Collective? </p><p><strong>Foundation ownership</strong></p><p>In this model, a foundation created by Open Collective takes ownership of a company and ensures that it is independent, values-driven, and purpose-led in the long term.</p><p>Foundation ownership does not provide for a specific way that our community would engage in governance, but there are possibilities for a foundation board to represent our global community. However, how would we solve for a global community and protect the purpose of Open Collective? Even if we could hack the corporate board structure to include the community, the power dynamics are problematic, to say the least. Finally, liquidity is likely be a challenge in this model.</p><p><strong>Golden Share model</strong></p><p>This model spreads decision-making power amongst a set of individual stewards than can include a wide variety of stakeholders and can be elected by the community. It utilizes a special, valueless Golden Share, which gives a non-commercial entity veto power over major decisions, like the sale of the company.</p><p>There's a high degree of community control that could grow over time. Stewards would be selected by our community, and would govern the platform's long term strategy and vision. The Golden Share could be held by a trusted third party like the <a href="https://www.purpose-us.com/?ref=blog.opencollective.com">Purpose Foundation</a> who's only role is to prevent major decisions that can subvert the mission. This model solves very well for protecting the purpose of Open Collective and multi-stakeholder governance.</p><p><strong>Perpetual purpose trust (PPT)</strong></p><p>A trust that centers our purpose would own all or part of Open Collective Inc. and be governed by a Trust Stewardship Committee. The Purpose of the Trust would be Open Collective's mission and the Committee is tasked with protecting it from coopting, sale or subversion. </p><p>While there is flexibility in how appointment are made, the committee would be the primary way that stakeholders would be involved in governance. Beyond just electing representatives, we could explore integrating democratic spaces and governance. The Trust solves relatively well for purpose protection, long term vision and multi stake-holding. Finally, a global community ownership still need to be questioned here. </p><p><strong>What else? Did I miss any other options?</strong> <a href="https://opencollective.slack.com/archives/C02777CBKTP?ref=blog.opencollective.com"><em>We'd love to hear your ideas...</em></a></p><h3 id="next-steps-finding-better-models">Next steps: finding better models</h3><p>In the coming months, we will be learning in public about potential structures, as we knit together deeper relationships to hold this learning, and we'll practice spreading more wealth and power to our Collectives and Hosts. Future posts will dig deeper into the other structures mentioned above, to explore if they fit.</p><p>We're excited to engage in public conversation with experts in Exit to Community, the solidarity economy, steward-ownership, and non-traditional start-up financing. Stay tuned for our Public Conversations Series starting in January 2022! </p><p>As always we are chatting in our <a href="https://discord.opencollective.com/?ref=blog.opencollective.com" rel="noreferrer">Discord</a> E2C channel or just <a href="mailto:pia@opencollective.com">reach out to me</a>. </p><p>Thank you Nathan Hewitt and Caroline Woolard for writing this with me! <3</p> </section> <section class="article-comments gh-canvas"> <script defer src="https://cdn.jsdelivr.net/ghost/comments-ui@~0.21/umd/comments-ui.min.js" data-locale="en" data-ghost-comments="https://blog.opencollective.com/" data-api="https://opencollective.ghost.io/ghost/api/content/" data-admin="https://opencollective.ghost.io/ghost/" data-key="6fa7e95c2c5c499f17a4faea1d" data-title="null" data-count="true" data-post-id="61948d09dc5a87003b2b4192" data-color-scheme="auto" data-avatar-saturation="60" data-accent-color="#0C2D66" data-comments-enabled="all" data-publication="Open Collective" crossorigin="anonymous"></script> </section> </article> </main> <aside class="read-more-wrap outer"> <div class="read-more inner"> <article class="post-card post featured"> <a class="post-card-image-link" href="/the-open-collective-platform-is-moving-to-a-community-governed-non-profit/"> <img class="post-card-image" srcset="/content/images/size/w300/2024/10/Screenshot-2024-10-11-at-5.37.50-PM.png 300w, /content/images/size/w600/2024/10/Screenshot-2024-10-11-at-5.37.50-PM.png 600w, /content/images/size/w1000/2024/10/Screenshot-2024-10-11-at-5.37.50-PM.png 1000w, /content/images/size/w2000/2024/10/Screenshot-2024-10-11-at-5.37.50-PM.png 2000w" sizes="(max-width: 1000px) 400px, 800px" src="/content/images/size/w600/2024/10/Screenshot-2024-10-11-at-5.37.50-PM.png" alt="The Open Collective Platform is moving to a community governed non-profit!" loading="lazy" /> </a> <div class="post-card-content"> <a class="post-card-content-link" href="/the-open-collective-platform-is-moving-to-a-community-governed-non-profit/"> <header class="post-card-header"> <div class="post-card-tags"> <span class="post-card-featured"><svg width="16" height="17" viewBox="0 0 16 17" fill="none" xmlns="http://www.w3.org/2000/svg"> <path d="M4.49365 4.58752C3.53115 6.03752 2.74365 7.70002 2.74365 9.25002C2.74365 10.6424 3.29678 11.9778 4.28134 12.9623C5.26591 13.9469 6.60127 14.5 7.99365 14.5C9.38604 14.5 10.7214 13.9469 11.706 12.9623C12.6905 11.9778 13.2437 10.6424 13.2437 9.25002C13.2437 6.00002 10.9937 3.50002 9.16865 1.68127L6.99365 6.25002L4.49365 4.58752Z" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"></path> </svg> Featured</span> </div> <h2 class="post-card-title"> The Open Collective Platform is moving to a community governed non-profit! </h2> </header> <div class="post-card-excerpt">A group of fiscal hosts representing thousands of collectives have created a new independent, community-governed, non-profit organization and have reached an agreement with Open Collective Inc. to take over the Open Collective platform as it exists today.</div> </a> <footer class="post-card-meta"> <time class="post-card-meta-date" datetime="2024-10-11">Oct 11, 2024</time> <span class="post-card-meta-length">5 min read</span> <script data-ghost-comment-count="670901dc32b53400012cdaff" data-ghost-comment-count-empty="" data-ghost-comment-count-singular="comment" data-ghost-comment-count-plural="comments" data-ghost-comment-count-tag="span" data-ghost-comment-count-class-name="" data-ghost-comment-count-autowrap="true" > </script> </footer> </div> </article> <article class="post-card post featured"> <a class="post-card-image-link" href="/why-the-open-source-pledge-is-both-relevant-and-timely/"> <img class="post-card-image" srcset="/content/images/size/w300/2024/10/Screenshot-2024-10-08-at-12.30.40.png 300w, /content/images/size/w600/2024/10/Screenshot-2024-10-08-at-12.30.40.png 600w, /content/images/size/w1000/2024/10/Screenshot-2024-10-08-at-12.30.40.png 1000w, /content/images/size/w2000/2024/10/Screenshot-2024-10-08-at-12.30.40.png 2000w" sizes="(max-width: 1000px) 400px, 800px" src="/content/images/size/w600/2024/10/Screenshot-2024-10-08-at-12.30.40.png" alt="Why the Open Source Pledge is both relevant and timely" loading="lazy" /> </a> <div class="post-card-content"> <a class="post-card-content-link" href="/why-the-open-source-pledge-is-both-relevant-and-timely/"> <header class="post-card-header"> <div class="post-card-tags"> <span class="post-card-featured"><svg width="16" height="17" viewBox="0 0 16 17" fill="none" xmlns="http://www.w3.org/2000/svg"> <path d="M4.49365 4.58752C3.53115 6.03752 2.74365 7.70002 2.74365 9.25002C2.74365 10.6424 3.29678 11.9778 4.28134 12.9623C5.26591 13.9469 6.60127 14.5 7.99365 14.5C9.38604 14.5 10.7214 13.9469 11.706 12.9623C12.6905 11.9778 13.2437 10.6424 13.2437 9.25002C13.2437 6.00002 10.9937 3.50002 9.16865 1.68127L6.99365 6.25002L4.49365 4.58752Z" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"></path> </svg> Featured</span> </div> <h2 class="post-card-title"> Why the Open Source Pledge is both relevant and timely </h2> </header> <div class="post-card-excerpt">Today Sentry, in partnership with over 20 other organizations, launches the Open Source Pledge at https://opensourcepledge.com/. We at Open Source Collective think the timing couldn’t be better.</div> </a> <footer class="post-card-meta"> <time class="post-card-meta-date" datetime="2024-10-08">Oct 8, 2024</time> <span class="post-card-meta-length">1 min read</span> <script data-ghost-comment-count="670516328de8e9000169d64d" data-ghost-comment-count-empty="" data-ghost-comment-count-singular="comment" data-ghost-comment-count-plural="comments" data-ghost-comment-count-tag="span" data-ghost-comment-count-class-name="" data-ghost-comment-count-autowrap="true" > </script> </footer> </div> </article> <article class="post-card post"> <a class="post-card-image-link" href="/open-collective-update-july/"> <img class="post-card-image" srcset="/content/images/size/w300/2024/07/Background-1024x768.png 300w, /content/images/size/w600/2024/07/Background-1024x768.png 600w, /content/images/size/w1000/2024/07/Background-1024x768.png 1000w, /content/images/size/w2000/2024/07/Background-1024x768.png 2000w" sizes="(max-width: 1000px) 400px, 800px" src="/content/images/size/w600/2024/07/Background-1024x768.png" alt="Open Collective Update - July 2024" loading="lazy" /> </a> <div class="post-card-content"> <a class="post-card-content-link" href="/open-collective-update-july/"> <header class="post-card-header"> <div class="post-card-tags"> </div> <h2 class="post-card-title"> Open Collective Update - July 2024 </h2> </header> <div class="post-card-excerpt">Join our Discord and get involved in our redesigning our crowdfunding expereince. Plus News, Events and more</div> </a> <footer class="post-card-meta"> <time class="post-card-meta-date" datetime="2024-07-22">Jul 22, 2024</time> <span class="post-card-meta-length">6 min read</span> <script data-ghost-comment-count="669e8c9a4a066d0001a8c2b9" data-ghost-comment-count-empty="" data-ghost-comment-count-singular="comment" data-ghost-comment-count-plural="comments" data-ghost-comment-count-tag="span" data-ghost-comment-count-class-name="" data-ghost-comment-count-autowrap="true" > </script> </footer> </div> </article> </div> </aside> </div> <footer class="site-footer outer"> <div class="inner"> <section class="copyright"><a href="https://blog.opencollective.com">Open Collective</a> © 2024</section> <nav class="site-footer-nav"> </nav> <div class="gh-powered-by"><a href="https://ghost.org/" target="_blank" rel="noopener">Powered by Ghost</a></div> </div> </footer> </div> <div class="pswp" tabindex="-1" role="dialog" aria-hidden="true"> <div class="pswp__bg"></div> <div class="pswp__scroll-wrap"> <div class="pswp__container"> <div class="pswp__item"></div> <div class="pswp__item"></div> <div class="pswp__item"></div> </div> <div class="pswp__ui pswp__ui--hidden"> <div class="pswp__top-bar"> <div class="pswp__counter"></div> <button class="pswp__button pswp__button--close" title="Close (Esc)"></button> <button class="pswp__button pswp__button--share" title="Share"></button> <button class="pswp__button pswp__button--fs" title="Toggle fullscreen"></button> <button class="pswp__button pswp__button--zoom" title="Zoom in/out"></button> <div class="pswp__preloader"> <div class="pswp__preloader__icn"> <div class="pswp__preloader__cut"> <div class="pswp__preloader__donut"></div> </div> </div> </div> </div> <div class="pswp__share-modal pswp__share-modal--hidden pswp__single-tap"> <div class="pswp__share-tooltip"></div> </div> <button class="pswp__button pswp__button--arrow--left" title="Previous (arrow left)"></button> <button class="pswp__button pswp__button--arrow--right" title="Next (arrow right)"></button> <div class="pswp__caption"> <div class="pswp__caption__center"></div> </div> </div> </div> </div> <script src="https://code.jquery.com/jquery-3.5.1.min.js" integrity="sha256-9/aliU8dGd2tb6OSsuzixeV4y/faTqgFtohetphbbj0=" crossorigin="anonymous"> </script> <script src="https://blog.opencollective.com/assets/built/casper.js?v=4b4d6947a3"></script> <script> $(document).ready(function () { // Mobile Menu Trigger $('.gh-burger').click(function () { $('body').toggleClass('gh-head-open'); }); // FitVids - Makes video embeds responsive $(".gh-content").fitVids(); }); </script>  <script async src="https://www.googletagmanager.com/gtag/js?id=UA-147664506-1"></script> <script> window.dataLayer = window.dataLayer || []; function gtag(){dataLayer.push(arguments);} gtag('js', new Date()); gtag('config', 'UA-147664506-1'); </script> </body> </html>

CINXE.COM

Pathways for Open Collective’s “Exit to Community”