Re:How We Write Github Issues
by julianlam on Wednesday January 08, 2014 @08:26AM
(#7023298)
Definitely good advice, but bad issues will always be present, no matter how many articles are written about it. I fully expect in 10 years to still have to deal with people pasting entire stack traces in github titles ;)
[ Parent
| on HN ]
I think it's a matter of peer pressure. You can't necessarily guarantee this on a OSS project, but between colleagues you should be able to set expectations; "I'm taking the time to properly explain what I'm working on, and so should you. Especially if you want me to help".
Doing so is also drastically reducing the amount of misunderstandings and the length of your Scrum meetings.