Every Good Open Source Product Starts with Scratching a Shared Itch
Producing Excellent Open Source Products
- NZer (now in SF)
- starter of things including - FLOSS Manuals, Booktype, BookJS, Coko (coFounder), Book Sprints, Cabbage Tree Method and more
- Shuttleworth Fellow
- Ex Artist and stuff
- Solving scholarly publishing problems with open source
- Building good faith networks
- Building infrastructure eg: PubSweet, INK, Editoria, XSweet
Itch to Scratch
The fact that it is your itch is important
The developer is:
the use case specialist
the code specialist
Knowing your itch gives you insights and motivations. It is an important qualitative and experiential factor.
What is it good for?
✓ Developer Tools
x User-facing solutions
Why is it failing open source in the 'user space'
...because we are scratching someone else's itch
a developer is
a code specialist
a user is
a use case specialist
Scratching someone else's itch
If we want to 'solve the users problem (itch)' they must be central to designing the solution.
Design with the User
The Cabbage Tree Method
- Building platforms
- Working with orgs
- Fixing workflows
Users Use Case Specialists
Use case Speciaists Designing Their Own Software