Developers ≠ Users: A Blueprint for Building an Open Source User Group Based on...
summary
Open-source EV charging stack Everest reaches roughly half a million charges in the field and faced a four‑year chicken‑and‑egg problem: users won’t engage until they can buy and operate chargers. A CPO forum (monthly, under LF Energy antitrust rules) is launched to gather operational pain — onboarding failures, inconsistent error codes, poor docs — and it yields concrete changes: a free tier of the virtual charger park aspyx for testing, adoption signals from a 25,000‑charger tender, and public meeting archives on YouTube.
AI-written summary · about
chapters (8)
- 0:00Introduction and Everest overview
- 7:02Why the CPO forum was created
- 10:35Identifying target users and challenges
- 14:51Structure and first meeting insights
- 19:08Key learnings and user pain points
- 23:44Blueprint for building a user group
- 25:34Outcomes and next steps
- 26:18Q&A session
related talks
40mHow to Open Source a Project and Possibly Not Fail While Trying
40mOpen Source Community Building
29mCharging developer batteries and sparking joy
16mDesigning open source tools for Citizen Coders
20mOpen up to Open Source
40mThree Cs to an Open Source Program Office
17mBuilding a culture of curiosity at your company
16mThe Open Source Community Playbook: What Works, What Doesn’t, and Why