1.
Introduction
❱
1.1.
Resources
1.2.
Terms
1.3.
Uncurled
2.
Experience
❱
2.1.
Dancer
2.2.
curl
2.3.
Rockbox
2.4.
c-ares
2.5.
libssh2
2.6.
Firefox
3.
Start
❱
3.1.
Your project
3.2.
On license
3.3.
Attracting developers and community
3.4.
Contributing
4.
People
❱
4.1.
Negative feedback
4.2.
Insulting attitude
4.3.
People use your code without telling
4.4.
Paid developers ask unpaid volunteers to do work
4.5.
Contributors will not stick around
4.6.
Newcomers can be awesome
4.7.
The know-it-best people
4.8.
People hide their origins
4.9.
People assume everything is well motivated
4.10.
People will contact you privately about the project
4.11.
People will provide feedback on irrelevant places
4.12.
Contributors are mostly male white westerners
4.13.
Lower the bar to attract more contributions
4.14.
Code of Conduct
5.
Project
❱
5.1.
Just a bunch of people
5.2.
People come and go
5.3.
Over time, maintenance grows
5.4.
Documentation is never good enough
5.5.
If not alive, it is dead
5.6.
The world is full of projects
5.7.
Old versions never die
5.8.
Keep. On. Improving.
5.9.
Clean up your backyard
5.10.
Help your neighbors
5.11.
Open standards are your friends
5.12.
The project is "we"
5.13.
Contributor License Agreement
5.14.
What is success?
5.15.
A good contribution
6.
Money
❱
6.1.
Volunteers make things different
6.2.
Companies pay for features
6.3.
Many companies rather not say
6.4.
Donations
6.5.
You get what you pay for
6.6.
Starting to charge is difficult
6.7.
Should companies pay?
6.8.
Rights to the money
7.
Source
❱
7.1.
Distributors absorb reports
7.2.
Do not accept undocumented code
7.3.
Many bugfixes address symptoms
7.4.
Only releases get tested
7.5.
Once merged, you own it
7.6.
Given enough eyeballs, all bugs are shallow
7.7.
Code quality
8.
Security
❱
8.1.
Security problems will appear
8.2.
Review, test, scan, verify
8.3.
Bug Bounty
8.4.
Responsible disclosure
9.
Maintainer
❱
9.1.
BDFL
9.2.
Security issues
9.3.
Release management
9.4.
Website admin
9.5.
Mailing list admin
9.6.
Patch reviewing
9.7.
User support
9.8.
Blogging about it
9.9.
Debugging
9.10.
Merging
9.11.
Feature development
9.12.
Write documentation
9.13.
Event planning
9.14.
Getting stickers
9.15.
Doing talks
9.16.
World monitoring
10.
Evolution
❱
10.1.
Production
10.2.
Consumption
10.3.
Infrastructure
10.4.
Tools
10.5.
Languages
10.6.
Funding
11.
Life
❱
11.1.
Days are 24 hours for all of us
11.2.
We are all differently privileged
11.3.
Health and life come first
11.4.
How to stay sane
11.5.
How to maintain motivation
12.
Emails
❱
12.1.
The Instagram and Spotify hacking ring
12.2.
I have Toyota Corola
12.3.
Drift gamepad on PS5
12.4.
I will slaughter you
12.5.
How I respond
13.
Epilogue
Light
Rust
Coal
Navy
Ayu
Uncurled
Life
Something about how to maintain a life and family while doing Open Source.
Days are 24 hours for all of us
We are all differently fortunate
Health and life come first
How to stay sane
How to maintain motivation