Something feels broken, confusing, or missing, and you say so. That’s often where contribution starts, but a drive-by complaint rarely lands. Feedback stalls for all kinds of reasons: a message that didn’t quite land, a maintainer too busy to follow up, or a reporter who never answered when asked for more detail.
I’ve seen small contributions such as a bug report, a translation fix, or a forum question turn into real improvements, especially for languages and cultures that core developers can’t fully understand on their own. This talk shares what makes feedback actually land: observe first, keep it small but concrete, stay in the conversation, and know that AI can draft a report but a human still has to stand behind it.
Not every path starts with frustration. I’ll share a case where self-interest brought in a contributor instead, and close with a few low-cost things any community can do to welcome newcomers.
