Expert Persona: Senior Open Source Ecosystem Strategist & Non-Profit Director
Review Group: This material is best reviewed by Open Source Software (OSS) Stakeholders and Community Advocates, specifically CTOs of companies utilizing the Erlang/Elixir stack, lead maintainers of core libraries, and community organizers focused on technology sustainability.
Abstract
In "How to Be an Elixir Champion," Dan Janowski, Chair of the Erlang Ecosystem Foundation (EEF) Sponsorship Working Group, outlines a strategic roadmap for moving the Elixir ecosystem from a volunteer-driven "alt brand" to a professionally sustained technology pillar. Janowski argues that because Elixir lacks the massive commercial backing of entities like Google or Microsoft, its survival and growth depend on "coordinated use of limited resources."
The talk addresses three critical pillars: advocacy, infrastructure, and sustainability. Janowski highlights the "hidden costs" of choosing a niche language—such as the need for constant persuasion of MBA-driven decision-makers—and proposes "confidence" as the core value proposition. He provides case studies on the precarious nature of critical infrastructure, including OpenTelemetry maintenance and the urgent need for a permanent Chief Information Security Officer (CISO) to navigate emerging international regulations like the EU Cyber Resiliency Act. The session concludes with a call for pooled financial resources via the EEF to fund essential tools like LSP and Rebar3, shifting the community's mindset from individual "micro-donations" to strategic, collective investment.
How to be an Elixir Champion: Strategic Ecosystem Roadmap
0:16 Being a Champion: Defining a "Champion" as a community member with the awareness of collective needs, a commitment of resources (time, money, or expertise), and the intent to serve via coordinated action.
1:41 The "Alternate Reality" Benchmark: A comparison between Elixir’s self-funded status and a hypothetical world where Erlang was the ubiquitous web runtime (like JavaScript). This context highlights that Elixir's progress is entirely dependent on its community rather than tool vendors or big industry players.
3:05 The Cost of an "Alt Brand": Choosing Elixir incurs "hidden costs," including the necessity for volunteers to maintain core components and the constant need to persuade decision-makers (MBAs) that the technology's benefits outweigh the perceived risks of a smaller ecosystem.
3:36 The Messaging Strategy: Effective advocacy requires "tuning" the story for different audiences (Business, Beginner, Elevator Pitch). Janowski identifies "Confidence" as the singular word that describes the Elixir experience regarding code reliability, OTP certainty, and ecosystem trust.
5:33 Marketing & Outreach Projects: Announcement of a new web resource project aimed at those with no Elixir exposure. This project focuses on explaining how Elixir is fundamentally different for both technical developers and commercial decision-makers.
6:32 Industry Vertical Outreach: A strategy to move beyond the Elixir community "bubble" by targeting specific verticals like healthcare, aerospace, and energy. Mentioning Elixir's role in successful projects in these forums builds awareness and curiosity among future C-suite leaders.
7:55 "Inreach" and Global Presence: The importance of regional conferences (Alchemy Conf, Gig City Elixir, etc.) and the challenge of restarting local meetups to build localized community energy.
8:49 Renovating Digital Presence: Identifying the need to unify the fragmented Elixir internet presence—spanning Slack, Discord, forums, and YouTube—into a cohesive, professional image that reflects a 10-year-old mature language.
10:49 The Open Source Sustainability Crisis: Reference to a Mercedes-Benz/EU study warning that the OSS success story is at risk because commercial consumers do not participate enough in upstream projects, leaving the burden on unpaid volunteers.
11:49 Case Study: OpenTelemetry (Otel): Highlighting the vulnerability of critical modules. Many Otel instrumentation modules are currently unmaintained because casual contribution is impractical without deep standards-context, creating risk for the entire ecosystem.
13:12 Case Study: Security and the CISO Role: Overview of the EEF’s Chief Information Security Officer (CISO) role. Janowski notes that increasing global regulations (EU Cyber Resiliency Act, NIS2) require dedicated staff to manage certifications and vulnerability disclosures (CNA) that cannot be handled by part-time volunteers.
15:37 The Power of Pooled Resources: Advocacy for the EEF as a "rally point" for funding. Successful examples include the LSP project (funded by Fly.io, River, and Todospaces) and the upcoming Rebar3 Kickstarter for a modernized, parallelized build process.
Join the EEF: Active participation in the Foundation is the primary way to coordinate finances and human resources.
Commercial Sponsorship: Decision-makers are urged to sponsor, while developers should advocate for corporate sponsorship to their management.
Content Creation: For those uncomfortable with public speaking, creating advocacy materials (slides, white papers) is a vital contribution to support those doing outreach.
Sustainable Funding: Transitioning from micro-payments (GitHub Sponsors) to pooled, strategic foundation funding is necessary for long-term project viability.