OpenChain - The Ramifications of ISO/IEC 5230 and ISO/IEC 18974 for Legal Pro...
Start contributing to OSS projects on your way
1. Start contributing to
OSS projects on your way
Kazuaki Matsuo
Senior Software Engineer, Device Automation
2. About me
• Kazuaki Matsuo
• from !, GitHub: KazuCocoa, Twitter: @Kazu_cocoa
• HeadSpin
• Software Engineer now, former was a test/QA engineer
• Maintain Appium project
• Five years after my first commit
3. Topic
• My experience in OSS world
• Start contributing to OSS
• How you can work in OSS Community
4. Takeaway
• Get an opportunity/motivation to contribute to Appium (OSS)
project
13. Maintain Ruby client
• Ruby was the primly language in Cookpad
• Decided to use Ruby
• Ruby lib status changed to “call for maintainers”
• https://github.com/appium/ruby_lib/issues/337
• I started to contribute it
14. Changes
• W3C support
• Separate core part
• https://github.com/appium/ruby_lib_core
• Collaboration
• https://github.com/watir/tap_watir
• https://github.com/watir project for mobile
15. Step into server side further
• Appium has:
• Clients: Not only for Ruby client
• Servers: For iOS/Android
• Languages
• NodeJS, Java/Kotlin, Objective-C/Swift, Ruby, Python, .NET
16. Nowadays
• As a part of my work at HeadSpin
• As a part of my private work
17. I talked…
• Fix issues I faced as a small start to contribute to OSS projects
• Leverage to other repositories/issues or more difficult issues
19. Only committing to the codebase?
• In various community, I heard this question frequently
• Exactly committing to the codebase is very important
• But other activities also very important as a community
31. Takeaway
• Start contributing from small changes
• get reviews
• leverage to other repositories
• OSS community needs you can work in
• Documentation
• Q&A
• Fixing issues / add new features (try to find an issue)