Let it go! or How to become a free software developer?
summary
A practical path from user to contributor: starts by reporting bugs, then submitting a first patch (often from a hackathon) and progressing to Eclipse committer status; tools and workflows are concrete — Git, Gerrit, bug trackers, code review and Mattermost — and examples include work on UML Designer / Sirius / EEF and a Buildroot Eclipse plugin. Contribution leads to paid roles: a remote hire at Obeo grows into technical director of a decentralized team of 10 working on dozens of Eclipse and GitHub projects; contributions reliably open opportunities.
AI-written summary · about
chapters (6)
- 0:00Intro
- 0:33What is an open source developer
- 2:27How to become an open source developer
- 8:48Being part of minority is an advantage
- 10:44What does it mean to be in opensource
- 13:36Conclusion
related talks
11mContributing to Open Source
36mWhat if you contribute to Eclipse ?
21mBecome Part of the Project
16mA Journey of Contribution and Collaboration in Open Source
36mDo Something Fantastic: Become an Open Source Developer
01h 10mCareers with Free/Libre and Open Source Software
01h 21mOpen Source Best Practices at Eclipse Foundation
37mThe Eclipse Development Process for Committers