Empowering users by asking them for money
summary
Argues that users gain real freedom when they can pay for directed development and shows practical channels: bartering fixes, contracting, and micro‑subscriptions via Patreon or Librepay (example: a workshop pledging $100/month). Describes concrete outputs — weekly patron video demos and many small Inkscape “paper‑cut” fixes — and institutional options like the Software Freedom Conservancy or donations (Red Hat $20k) to keep decisions public. Warns of risks and suggests separate admin for paid work and project public‑interest policies.
AI-written summary · about
chapters (21)
- 0:00Intro
- 0:29Welcome
- 2:29Focus on users
- 3:13Free software freedoms
- 4:25Small projects
- 5:26Charitable paternalism
- 6:50dentured responsibility
- 7:44introducing money
- 8:19what is money
- 9:24support contract
- 10:28directed creation
- 11:07bartering
- 11:55contracting
- 13:54micro subscriptions
- 19:02cautions problems
- 20:01social economic discrimination
- 21:22internal competition
- 21:55project corruption
- 22:47conclusions
- 29:57inkscape
- 33:02Sweden
related talks
24mContributor engagement and monetization opportunities
29mFlourishing FLOSS: Making Your Project Successful
24mFlourishing FLOSS: Making Your Project Successful
29mMyths and Metaphors of Open Source
42mWhy Funding Open Source is Hard
53m.NET Rocks Live: Making OpenSource Work for Everyone
15mFostering Innovation in IT Businesses through Open Source Software Involvement
34mFOSS like a Boss!