Lightning Talk Better Communication
summary
A real case: a production gem needs an update, a pull request with passing tests gets no response, so the maintainer is effectively forced to make my own gem or fork and deploy off of GitHub; the recommendation is to categorize issues, post simple status replies like "on vacation", link to docs, invite junior devs to help, and ask contributors to include context (inputs, expected outputs, assumptions); cites fog repository as an example of responsive issue handling.
AI-written summary · about
related talks
06mLightning Talk: Undefined Behavior - Toolkit to Improve Communication With Clients
32mCommunicate Like You're Remote
31mWe All Make Mistakes: Learning from Gaffes in the Ruby Community
23mCommunication is just as important as Code
34mHow to effectively communicate to Developers/PMs - A guide for developers and project managers
06mLightning Talk: Refactoring of Self
17mWelcoming People (and Other Hard Problems)
23mMake Your and Other People's Life Easier: Do Support!