Start Contributing To OSS Projects On Your Way
summary
First commit to Appium happens in 2014 by fixing a small user-facing bug and contributions grow until they become routine, moving from fix a small issue to maintaining the Ruby binding and adding W3C spec support, server-side fixes, and cross-language work in Python and .NET; other easy-entry contributions include good first issue changes, documentation, localization and answering forum questions. Practical takeaway: start tiny, use the actual repos and tools (bindings, Selenium helpers, translators), iterate, and keep contributing.
AI-written summary · about
chapters (13)
- 0:00Start
- 1:25Topic
- 5:55my first commitment for Appium repo
- 8:21Maintain Ruby client
- 9:16Changes
- 9:53Step into server side further
- 12:27Only committing to the codebase?
- 12:57Features/Documentations
- 13:43Support users
- 14:25Use them and evolve automation
- 16:07Localisation
- 19:59Improve error messages
- 20:31Takeaway
related talks
31mCode It Forward: Making Your Mark in Open Source
15mHow Can Testers Contribute to Open-Source Projects
31mGetting Started with Open Source Contributions
35mYour First Open-Source Contribution
40mHarnessing Open Source Contributions for Modern Careers
11mContributing to Open Source
36mYour first contribution (and beyond)
27m"Getting Started with Open Source Contributions"