Giving and Getting Technical Help in Open Source Without Being Scared!

### Overview In this presentation delivered at Open Source Summit 2021, Sonia Singla discusses the practical dynamics and mindset behind giving and receiving technical help within open source communities. Drawing on early personal experiences from college practical labs and initial open source interactions—where questions were often asked without context or met with systemic biases and unconscious prejudice—the talk outlines concrete techniques for junior and senior engineers to collaborate effectively, communicate clearly, and foster welcoming technical environments.

### Key Topics - **Mindset of Asking for Help**: Acknowledging that not knowing everything is a normal part of working with fast-evolving technologies, whether one is a newcomer or a senior contributor. - **Preparation and Effective Question Asking**: Moving away from vague direct messages toward structured public inquiries supported by prior research and context. - **Mentorship and Inclusive Community Dynamics**: Addressing representation, visibility, and unconscious bias in tech while building supportive spaces for underrepresented contributors. - **Guidelines for Giving Technical Assistance**: Fostering healthy collaboration without fostering over-reliance or toxicity.

### Technical Details Singla provides practical frameworks for both seeking and delivering technical support:

1. **Best Practices for Asking for Help**: - *Check the Environment*: Choose suitable public channels, forums, or issue trackers rather than unsolicited private messages, and observe community communication norms. - *Do Initial Homework*: Search existing resources such as Stack Overflow, GitHub, and documentation to avoid asking repetitive questions. - *The 15-Minute Rule*: Spend roughly 15 minutes attempting to understand and debug the issue independently before reaching out. This ensures the asker can provide full context and error details. - *Explain the Big-Picture Goal*: State clearly what objective is being pursued rather than solely focusing on a broken step. - *Share What Has Been Tried and Avoid Ambiguity*: Explicitly document commands run, error messages received, and avenues explored. Avoid ambiguous phrases like "I think" when describing concrete technical behavior. - *Say Thanks and Close the Loop*: Return to the thread to acknowledge help, share the final working solution, and provide feedback.

2. **Best Practices for Giving Help**: - *Be Welcoming and Curious*: Encourage questions and respond with patience rather than dismissing issues as trivial. - *Maintain a Healthy, Non-Toxic Environment*: Avoid derogatory phrases such as "you don't even know this," which discourage contributors. - *Explain the Process and Reasoning*: Instead of just giving the final answer, explain the underlying logic, decision-making steps, and link relevant documentation. - *Help Them Grow (Avoid Grabbing the Keyboard)*: Do not take over someone's keyboard or fix issues directly on their behalf; guide them so they develop independent problem-solving skills. - *Use Inclusive and Constructive Language*: Avoid words like "easy," "simple," or "just," as concepts that seem obvious to an experienced maintainer may not be obvious to a learner.

### Takeaways Asking questions constructively and providing compassionate, process-oriented guidance creates a sustainable culture in open source projects. By balancing supportive mentoring with independent troubleshooting, communities can guide contributors into future maintainers and leaders.