Bridging Hierarchies and Open Collectives via Open Collective

Source: What is Open Collective? — Open Collective https://youtu.be/IBU5fSILAe8 other highly relevant video: https://youtu.be/ubfYuAMm3_c?si=-RMkkPFwM54SRtbj

Summary

The video illustrates the organizational mismatch between traditional hierarchical institutions (triangles) and decentralized, open-source communities (circles). Open Collective serves as an operational and fiscal bridge, providing open communities with financial, administrative, and legal infrastructure without requiring them to incorporate into rigid corporate hierarchies.

Aspects

Hierarchical Organizations as Triangles (00:00-00:10)

Traditional organizations such as corporations operate as rigid, top-down, and inflexible hierarchical triangles designed for traditional legal and financial systems.

Emergence of Networked Circles (00:11-00:41)

The internet facilitated the rise of decentralized, flexible collectives working collaboratively on software, community projects, and activism without centralized ownership.

The Institutional Friction (00:42-01:05)

Decentralized circles encounter friction when interfacing with triangular legacy systems that demand legal bank accounts, tax filings, and corporate invoicing for funding.

End-results and Core Aspect

Core Aspect — Fiscal Host and Infrastructure Bridge (01:06-01:20)

Open Collective acts as a fiscal and operational proxy, enabling open collectives to manage finances legally within traditional frameworks while retaining decentralized governance.

Results

Frictionless Fundraising and Invoicing (01:13-01:20): Collectives can seamlessly accept corporate sponsorships, generate compliant invoices, and collect contributions without incorporating as formal commercial entities.
Real-Time Financial Transparency (01:21-01:27): All income, contributor payouts, and expense reimbursements are tracked on a transparent, publicly accessible ledger accessible anytime to supporters.
Automated Back-Office Operations (01:28-01:43): Taxes, reporting, accounting, and compliance administration are abstracted away, allowing developers and contributors to focus exclusively on community and code.

Academics

Organizational Studies

Examines how hierarchical firms differ from networked collectives, including structure, coordination, authority, and institutional fit.

Sociology

Studies how communities organize, build trust, and coordinate action without centralized ownership or traditional corporate forms.

Political Economy

Analyzes how money, labor, and governance flow through open communities and the institutions that support them.

Nonprofit Management

Focuses on fiscal hosting, compliance, sponsorship, accounting, and the practical administration of mission-driven groups.

Law

Covers legal entity status, liability, contracts, tax reporting, and the role of a fiscal host in enabling lawful financial operations.

Accounting

Addresses transparent ledgers, expense tracking, budgeting, reimbursements, and financial recordkeeping for collectives.

Information Systems

Studies the digital infrastructure that connects funding, governance, and project tooling across distributed communities.

Open Source Studies

Explores sustainability models for open-source projects, including sponsorship, donor relations, and maintenance funding.

Platform Cooperativism

Investigates platforms that support shared ownership, community governance, and collective economic coordination.

Science and Technology Studies

Looks at how technical systems and social institutions shape each other, especially in decentralized online collaboration.

Main Contact Channels

Open Source Project Support: For your specific open-source project or fund, email the dedicated fiscal host directly. As stated by Open Source Collective, “The best way to get in touch with Open Source Collective (OSC) is by emailing us at hello@oscollective.org.
General Platform Support: If you have general questions about the platform, you can reach out via the Open Collective Contact Page. According to Open Collective, “Our support team is available from Monday to Friday. Please expect a response within 3 business days.” https://docs.oscollective.org/about-osc/contact
Community Chat: You can also join their community channels or Discord to chat with other project maintainers and staff.

—— Podcast with Mia and Ava ——

Mia: Today, we’re breaking down how to fund the Medicine Wheel Packages project using Open Collective.

Ava: Right, so what is Open Collective, Mia?

Mia: It’s a platform that lets community projects collect and manage money without creating a separate legal entity. They also provide fiscal hosts, which handle your funds, taxes, and payouts. Everything is transparent—budgets, expenses, and donor visibility.

Ava: So if I’m running an open-source project like Medicine Wheel Packages, where do I start?

Mia: First, create an account at opencollective.com. Then, start a new Collective for your project, choosing the “For Open Source projects” option. That will prompt you to apply to the Open Source Collective as your fiscal host.

Ava: And after you apply?

Mia: You’ll fill in a short form with your Collective name, a URL slug, a brief description, links to your GitHub repos, and your contact details. Submit it, and wait for approval.

Ava: Once approved, what’s next?

Mia: Configure your Collective page. Add an About section explaining what the project does and why it matters. Set funding goals, define your expense rules, and connect your payout methods, like Stripe or PayPal.

Ava: And how do people actually find our Collective to donate?

Mia: Link it directly in your code and repos. In package.json, add a funding field pointing to your Open Collective URL. On GitHub, add a .github/FUNDING.yml file and a badge in your README. There’s even a CLI tool to automate these updates.

Ava: So, once we’re live, how do we bring in funding?

Mia: Open Collective supports recurring donations from individuals, sponsorships from companies, grants from institutions, and one-off donations. You can set up tiers to show donors exactly what they’re supporting.

Ava: Sounds straightforward. Can you sum up the minimal steps?

Mia: Sure. One: register on Open Collective. Two: create your Collective, apply to the Open Source Collective. Three: prepare your project name, description, and repo links. Four: after approval, set up your page and link it in your packages and repos. Once that’s done, your Medicine Wheel Packages project will have a live, public funding channel.

Ava: Perfect. A simple path to start receiving community support.

Mia: Exactly. But going live is only the first step. The next part is making the Collective feel trustworthy and alive.

Ava: What do you mean by “alive”?

Mia: I mean people should understand where the money goes, who maintains the project, and what kind of progress their support makes possible. A funding page should not feel like a donation box sitting in the corner. It should feel like an open invitation.

Ava: So we need more than just a button that says “Donate.”

Mia: Right. Start with a clear mission statement. For Medicine Wheel Packages, explain that the project supports open-source tools, cultural-interface experiments, documentation, package maintenance, and future community-facing resources.

Ava: Should we list practical costs too?

Mia: Definitely. Transparency is the strength of Open Collective. You can say funding may support development time, hosting, documentation, accessibility work, testing, community support, design, and release maintenance.

Ava: That makes it easier for donors to see the real work behind the package.

Mia: Exactly. Open-source projects often look effortless from the outside, but every stable release represents invisible labor: debugging, documentation, compatibility checks, security updates, issue triage, and user support.

Ava: What about sponsor tiers? Should we create them right away?

Mia: Yes, but keep them simple at first. You could create tiers like Community Supporter, Sustaining Sponsor, Project Partner, and Institutional Backer. Each tier should describe what the contribution helps sustain, not just what the donor gets in return.

Ava: So instead of making it transactional, we frame it as shared stewardship.

Mia: Precisely. For example, a small monthly tier might support documentation and maintenance. A larger sponsor tier might support new package development, educational material, or dedicated work on roadmap items.

Ava: Should we promise features to sponsors?

Mia: Be careful with that. Sponsors can help guide priorities, but the project should keep its integrity. It’s better to say sponsors support the public roadmap, ongoing sustainability, and community benefit. Avoid turning donations into private feature contracts unless you intentionally want that structure.

Ava: That makes sense. How do we help people trust that their money is handled responsibly?

Mia: Publish a basic expense policy. Say who can submit expenses, what kinds of expenses are valid, who approves them, and how decisions are documented. Even a short policy builds confidence.

Ava: Something like: expenses must directly support development, maintenance, infrastructure, documentation, or community operations?

Mia: Yes. And include examples: domain costs, hosting, development tools, design assets, contributor compensation, workshops, or documentation work. Also say what is not covered, such as unrelated personal expenses.

Ava: Should we connect this to GitHub issues?

Mia: That’s a strong move. You can label issues as “funding-needed,” “sponsor-supported,” or “roadmap.” Then donors can see the relationship between support and real project movement.

Ava: I like that. It turns funding into visible momentum.

Mia: Exactly. And when work is completed, update the Collective. Post short updates: what was released, what changed, what support made possible, and what comes next.

Ava: So communication matters as much as setup.

Mia: More than people think. A quiet funding page can look abandoned, even if the project is active. Monthly or quarterly updates keep the signal warm.

Ava: What should the first update say?

Mia: Something simple. Announce that Medicine Wheel Packages now has an Open Collective, explain the purpose of the fund, name the first funding goals, and invite contributors, users, and sponsors to participate.

Ava: Could we also add it to the README?

Mia: Absolutely. Add a short “Support the Project” section. Include the Open Collective badge, the donation link, and one paragraph explaining why support matters.

Ava: And package-level funding fields help package managers detect the funding link automatically.

Mia: Yes. That makes the support path visible wherever the package travels. GitHub, npm, and other tooling can surface the funding information when configured correctly.

Ava: What about companies using the package internally?

Mia: That’s an important audience. Many companies depend on open-source tools without realizing how fragile maintenance can be. A sponsor message can say: “If your organization benefits from Medicine Wheel Packages, consider sponsoring its continued development.”

Ava: Clear, respectful, and direct.

Mia: Exactly. No guilt. Just structural reality: if people rely on a tool, supporting it helps keep it healthy.

Ava: What would be a good first funding goal?

Mia: Start with something concrete and modest. For example: “Reach $500/month to support maintenance, documentation, and release stability.” Then later, you can add larger goals for new modules, educational guides, or contributor compensation.

Ava: So the first goal should prove the system works.

Mia: Yes. Don’t overbuild the funding structure before there is movement. Start clear, start honest, and let the Collective evolve as the project grows.

Ava: What about governance? Should we define who makes decisions?

Mia: Yes, even lightly. Name the maintainers, explain how funds are approved, and state that major funding changes will be documented publicly. This prevents confusion later.

Ava: So the core pieces are: mission, budget, tiers, expense rules, updates, GitHub integration, and governance.

Mia: Exactly. And one more thing: gratitude.

Ava: Gratitude?

Mia: Yes. Thank supporters visibly. Add a sponsor section, publish acknowledgments, and make people feel part of the project’s continuity. Funding is not just money. It is relationship.

Ava: That changes the tone. It becomes less like “please donate” and more like “help sustain this living system.”

Mia: That’s the right framing. Medicine Wheel Packages is not only a codebase. It is a structure people can use, extend, learn from, and gather around. Open Collective gives that structure a public channel for support.

Ava: Then the next step is to draft the actual Collective page.

Mia: Yes. Start with a title, a short description, a longer mission section, funding goals, sponsor tiers, and expense guidelines. Once those are ready, the technical setup becomes easy.

Ava: And after launch?

Mia: Share it intentionally. Add it to the README, package metadata, GitHub funding file, release notes, project website, and community posts. Then keep updating it as work happens.

Ava: So the Collective is not a finish line.

Mia: No. It’s an infrastructure layer. A public rhythm for sustaining the work.

Ava: Good. Then we’re not just opening a funding page. We’re creating a visible support system.

Mia: Exactly. And that is what makes the project stronger over time.

Citations:

[1] What Is Fiscal Hosting? - https://opencollective.com/fiscal-hosting
[2] Choosing a Fiscal Host - https://documentation.opencollective.com/collectives/choosing-a-fiscal-host
[3] Fiscal Hosts FAQ - Old Open Collective Docs - https://docs.opencollective.com/help/fiscal-hosts/fiscal-hosts
[4] Fiscal Hosting Options - Open Collective - https://blog.opencollective.com/fiscal-hosting-options/
[5] Add Fiscal Host | Open Collective Docs - https://docs.opencollective.com/help/collectives/add-fiscal-host
[6] Fiscal Hosting FAQs | OCE - https://docs.opencollective.com/oceurope/faq/fiscal-hosting-faqs
[7] Make your community sustainable. Collect and spend money ... - https://opencollective.com/collectives
[8] News for Fiscal Hosts - https://blog.opencollective.com/news-for-fiscal-hosts/
[9] What We Offer | OCE - https://docs.opencollective.com/oceurope/what-we-offer
[10] A Speculative Sketch of a DAO, with Open Collective - https://www.radicalxchange.org/updates/blog/a-speculative-sketch-of-a-dao-with-open-collective/
[11] Becoming a Fiscal Host | Old Open Collective Docs - https://docs.opencollective.com/help/fiscal-hosts/become-a-fiscal-host
[12] Open Collective: Raise, manage and disburse money with full ... - https://opencollective.com/
[13] Fiscal sponsorship has never been easier - https://opencollective.com/become-a-host
[14] Creating a Fiscal Host | Old Open Collective Docs - https://docs.opencollective.com/help/fiscal-hosts/create-a-fiscal-host
[15] Open Collective Docs: Welcome - https://documentation.opencollective.com/

[FUNDING] Bridging Hierarchies and Open Collectives via Open Collective