Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Funding Ruby Infrastructure as a Non-Profit

Funding Ruby Infrastructure as a Non-Profit

Delivered at RubyConf Taiwan 2025 in Taipei

https://www.youtube.com/watch?v=V8O1CbGpDfI

Avatar for Samuel E. Giddins

Samuel E. Giddins

August 09, 2025
Tweet

More Decks by Samuel E. Giddins

Other Decks in Programming

Transcript

  1. Your Presenter Samuel Giddins @segiddins → RubyGems, Bundler, RubyGems.org maintainer

    → Long-time bug author → Security Engineer in Residence @ Ruby Central RubyGems.org
  2. Your Presenter Samuel Giddins @segiddins → Has opinions that are

    his own, → and not necessarily those of his employer. RubyGems.org
  3. Ruby Central → 501(c)(3) non-profit founded in 2001 → Organizes

    RubyConf (USA) → Previously RailsConf → Operates RubyGems.org → Mission: Sustain and grow the Ruby ecosystem RubyGems.org
  4. The Mission To sustainably provide high-quality and secure infrastructure through

    RubyGems to reliably build Ruby software that enables businesses and the community to thrive. Dedicated to supporting impactful open source projects on behalf of the Ruby community and fostering the growth of open source contributors to ensure the continuity of the Ruby ecosystem. RubyGems.org
  5. Ruby Ecosystem is Open Source → RubyGems.org - Package registry

    → Bundler - Dependency management → Ruby - MRI, standard library → Rails, Sinatra, Hanami - Web frameworks → RSpec, Minitest - Testing frameworks → Puma, Unicorn - Application servers RubyGems.org
  6. Who's Involved? Maintainers → Write and maintain code, docs, and

    designs → Handle issues and PRs → Set project priorities → Click the "Release" button Consumers → Use the software → Report bugs → Benefit from the work RubyGems.org
  7. For-Profit: Simple Math Revenue → Development + Operations → Companies

    pay developers → Companies pay for infrastructure → Customers pay companies RubyGems.org
  8. On the Other Hand RubyGems has: → 0 revenue →

    Expensive operations (40+ billion downloads/year) → Complex development needs (security, performance, features) RubyGems.org
  9. How Engineering Time Gets "Paid" Companies Pay Employees work on

    OSS as part of their job Money Appears Somehow funding materializes to pay maintainers No One Gets Paid Maintainers essentially pay with their time RubyGems.org
  10. Infrastructure Can Be Donated → Cloud credits → Hosting infrastructure

    → CDN → SaaS products But someone still needs to manage it RubyGems.org
  11. Historical Maintenance → Volunteer-driven development and operations → Best-effort availability

    and security → Individual maintainers without backup → Frustration-driven feature development RubyGems.org
  12. Infrastructure is more than Code Writing code vs Operating infrastructure

    → Code contribution: Creative, flexible timing, done when motivated → Operations/oncall: Stressful, immediate response required, disrupts life → Volunteers willing to code on weekends → Far fewer willing to handle 3am outages (and carry a laptop 24/7) RubyGems.org
  13. Why Funding Matters More Than Ever → Supply chain security

    is now a critical business concern → Regulatory requirements (CRA, etc.) make that concern a legal requirement → Increased focus goes hand in hand with increased vulnerability exploitation of open source → These become asks of open source projects RubyGems.org
  14. Scale & Visibility In May 2025: 4.05B GEMS DOWNLOADED 1.15PB

    TOTAL BANDWIDTH 431MB /s AVG TRAFFIC 1514 GEM DOWNLOADS/S → Scale of usage requires expensive infrastructure → Visibility requires quick remediation of vulnerabilities → 2025 demands more than 2005 RubyGems.org
  15. Immediate Impact → All gem install commands fail globally →

    All bundle install commands fail globally → CI/CD pipelines break for Ruby projects → New deployments blocked without vendored gems or prebuilt container images RubyGems.org
  16. Cascading Effects → Development teams paralyzed across thousands of companies

    → Production deployments blocked globally → Open source contributions halt → Ruby's reputation damaged as a production-grade ecosystem RubyGems.org
  17. Ruby Central: A Model → 501(c)(3) non-profit since 2001 →

    Originally organized RubyConf and RailsConf RubyGems.org
  18. The Evolution → Now maintains RubyGems.org infrastructure → Natural actor

    to match funding with work → Neutral steward with aligned incentives → Not a competitor to any company RubyGems.org
  19. Key Turning Points → 2001: Founded for conference organization →

    2009: Took over RubyGems.org hosting → 2022: Ruby Together merger, paying for open source development → 2023: Full-time security employee RubyGems.org
  20. Structuring for Sustainability → Professional governance and operations with board

    oversight → Transparent financials and reporting → Multiple revenue streams reduce risk → Community input in major decisions RubyGems.org
  21. 2024 Ruby Central Funding 15% DONATED SERVICES 62% PROGRAM- SPECIFIC

    8% MEMBERSHIPS 15% CORPORATE SPONSORSHIPS RubyGems.org
  22. Ruby Central Funding Programs → Infrastructure Donations: AWS, Fastly, Datadog,

    others donate services → Grants (60% of budget): Alpha-Omega, Sovereign Tech Agency, AWS → The Alpha-Omega grant covers my residency → Corporate Sponsorship: $10K+ annually for overall support of the organization → Shopify's Ruby Shield program is $1MM over four years → Open Source Supporter Program: $2,500-$5,000 annually specifically for open source → Individual Membership: Low-dollar community support (launching soon) → One-Time Donations: Flexible, no-strings-attached support RubyGems.org
  23. Why Non-Profits Work for Open Source The Fundamental Truths →

    Open source continues to grow in importance → Open source will always require resources to maintain → Largest projects require a "steward" → Someone needs to be responsible for the commons Non-Profits as the Solution → Formalize "the community" as a legal entity → Not a competitor to any company → Not a government making sweeping mandates → Aligned incentives to improve ecosystem for everyone RubyGems.org
  24. Other Role Models Python Software Foundation → PyPI infrastructure →

    Multiple full-time staff → Conference revenue + donations Rust Foundation → Corporate members → Clear governance → Diverse funding sources RubyGems.org
  25. Emerging Challenges → Growing scale requires more resources → Security

    threats are increasingly sophisticated → Compliance requirements add operational complexity → Community expectations for reliability increase RubyGems.org
  26. New Opportunities → Corporate awareness of supply chain risks →

    Government funding for critical infrastructure → Foundation support for open source sustainability → Community willingness to contribute financially RubyGems.org
  27. Reasons for Optimism → Proven models exist and are working

    → Corporate understanding of OSS value is growing → Funding sources are diversifying → Community engagement is increasing → OSS is stronger than ever RubyGems.org
  28. How the Community Can Help Individuals → Monthly donations →

    Advocate at work → PRs welcome Companies → Sponsor at appropriate level → Provide infrastructure → Allow employee contributions RubyGems.org
  29. The Ruby We Want → Reliable infrastructure that never goes

    down → Fast security responses to protect all users → Professional maintenance → State-of-the art features → Sustainable funding for decades to come RubyGems.org
  30. Questions? Samuel Giddins • @segiddins Funding Ruby Infrastructure as a

    Non-Profit [email protected] https://rubycentral.org/support RubyConf Taiwan 2025 RubyGems.org