Join Pallavi Sharma as she shares her journey in open source and demonstrates how contributing can fuel professional growth, from collaboration and networking to visibility and skill development.
Discover practical ways to start contributing, explore opportunities beyond code, and learn from real-life examples in automation and testing.
Don’t miss out, book your free spot now
What’s the best way for someone new to open source to make a meaningful first contribution?
Could you outline 2–3 small, beginner-friendly ways testers and automation engineers can contribute to open source without writing large chunks of code?
Many people experience ‘imposter syndrome’ and worry their contribution isn’t good enough. What’s your advice for overcoming that initial fear and making that very first contribution to an open source project?
How is “free” software distinct from “open source,” and why is clarifying this distinction essential for appreciating tools such as Appium?
What are the first steps for beginners to start contributing to open source projects?
In what ways do the concepts of “free” and “open source” diverge, and how does that difference shape our understanding of the value Appium provides?
What common mistakes should new contributors avoid in their first pull requests?
How do you identify the right open source project that matches your skills and interests?
What role does documentation play in sustaining healthy open source communities?
How do maintainers manage security, code quality, and trust in open source collaborations?
What are the key distinctions between “free” and “open source,” and why is this difference important for understanding the value proposition of tools such as Appium?
Should contributors focus on code, documentation, or both when starting out?
As a tester, how do you see your role shaping open source quality?
As AI-generated code becomes more common, what role do you see it playing in shaping the future of open-source contributions?
What are some common misconceptions or barriers that prevent professionals from actively contributing to open source?
In what ways can contributing to open source help individuals stay abreast of current industry trends and technologies, effectively “shining out in a crowd” of professionals?
Is your AI helping you test better or just faster?
Beyond writing code, which contributions (docs, testing, community support) have the biggest impact for projects like Selenium or Appium?
What strategies help overcome the intimidation factor when contributing to large, established projects?
