Bugs, that is. I'd love to file hugs though
-
-
Replying to @wycats @dan_abramov
And a lot of maintainers don't do a lot to improve that perception.
1 reply 0 retweets 0 likes -
Replying to @wycats @dan_abramov
This is why I resist issue templates on my projects.
1 reply 0 retweets 1 like -
Replying to @wycats @dan_abramov
the issue reporters that clear our template are nearly always the ones we have to have a silly follow up "please provide a repro"
1 reply 0 retweets 1 like -
Replying to @jbogard @dan_abramov
1: a. I haven't found that. b. There are many different kinds of issues and follow-up questions by experts are easier on contributors than
1 reply 0 retweets 0 likes -
2/2: asking every possible follow-up question up front.
1 reply 0 retweets 0 likes -
Replying to @wycats @dan_abramov
What about basic stuff, like what version? And do you see much traffic that's better suited for stack overflow?
1 reply 0 retweets 0 likes -
Replying to @jbogard @dan_abramov
Version seems somewhat ok but I admit to often, as an issue filer, feeling flummoxed when asked to fill that in.
1 reply 0 retweets 0 likes -
The template should tell you exactly how to find it.
2 replies 0 retweets 0 likes -
Templates should also start with a free form way to describe what went wrong and end with minimal "template"y stuff.
2 replies 0 retweets 1 like
The more structured an issue template is, the less likely I am to file.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.