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

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