Open dsernst opened 10 years ago
I like issue because it's more general, but I think it's okay to use problem, task, etc., when the context warrants it.
On the other hand, I suppose problem is a more dramatic word, and therefore potentially more likely to inspire action.
In Introduction.md (home directory), I started switching most instances to 'Problem' for a formal context, i.e. Problem page, but issue etc in an informal context. The strongest reason is because "Solve Problems" feels more natural (/ widely accessible) than "solve issues".
Does this resonate?
On Saturday, July 12, 2014, iangilman notifications@github.com wrote:
I like issue because it's more general, but I think it's okay to use problem, task, etc., when the context warrants it.
On the other hand, I suppose problem is a more dramatic word, and therefore potentially more likely to inspire action.
— Reply to this email directly or view it on GitHub https://github.com/LetsFix/letsfix.net/issues/15#issuecomment-48801962.
Yeah, problem seems more concrete, which is probably a good thing for this audience.
I'm conflicted about when to use the word "issue" and when to use "problem". ( Particularly while editing this document: https://github.com/LetsFix/letsfix.net/blob/master/theprocess.md )
This website tries to show the "DifferenceBetween" -- http://www.differencebetween.net/language/difference-between-issue-and-problem/ -- but it didn't help all that much.
arguments for always using "problem"? or always using "issue"?