I wish there was a community workflow for issue escalation.
~99% of GitHub issues for Keras are user errors, making it quite difficult to surface any potential bug.
-
-
-
wouldn't labels work for marking actual bugs, so one can filter them
- Show replies
New conversation -
-
-
how many do you get mentioned on? Maybe good mention etiquette could surface the bugs.
-
we would need manual triaging from people who understand Keras well. It would be quite work-intensive.
End of conversation
New conversation -
-
-
isn't that a bug?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I bet it is. It’s because this is non-trivial stuff. You guys are doing such an incredible job with Keras, though. Love it!
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Use labels to tag dev related issues. Close the others and refer to google groups. And: Find maintainers who take care of this.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I lkd at 10 pages yest. 2 easy steps:1. @ Original Post, is your issue resolved? no. Close. 2: use Gitter for qs, not issues
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
are there any common patterns? If so, why not improve documentation/apis to minimize those errors?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
users errors can reflect API bugs to Documentation bugs.
-
"Keras has a bad API" or "Keras has bad documentation" isn't something I ever hear. You overestimate users' ability to read docs.
- Show replies
New conversation -
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.