Why is UX so hard to contribute to FOSS
summary
A UX designer volunteers on three projects and finds no UX hooks; issue queues only request icons. Git and text‑only issues prioritize checkin‑friendly artifacts, creating a tyranny of ASCII that excludes flow diagrams, prototypes and discussion. A submitted motion study prompts a maintainer to threaten to quit. Practical fixes: publish a user study in the repo, add explicit UX priorities to the backlog, post animated GIFs of interactions, and use VC or virtual whiteboards to coordinate and build consensus.
AI-written summary · about
chapters (14)
- 0:00Introduction and context
- 3:35Icons as the only UX task
- 5:22Expanding UX definition and goals
- 8:51Understanding users and their tasks
- 11:15Tools like Git and UX workflows
- 13:46Tyranny of ASCII in FOSS
- 15:11FOSS culture and UX collaboration
- 16:57Saying no with UX perspective
- 18:21Three steps to improve UX in FOSS
- 20:06Q&A begins with culture questions
- 22:34Virtual war rooms and async work
- 24:44Consensus and UX in open source
- 26:54Applications vs desktop UX focus
- 27:57Misconceptions about UX in FOSS
related talks
22mWhy UX and FOSS clash and what we can do about it
25mSize matters: Why some projects can't do UX well
13mThe UX of UX - Behind the scenes of effectively designing in the open
24mCalling all UX Designers!
22mBridging the Gap Between Designers & Open Source Communities
34mUnderstanding UX (and UI) – a practitioner's perspective
40mNavigating engineering-focused environments
16mThe designer-contributor dilemma with FOSS