GDK Stability, Reliability, Usability, Performance and Maintainership
Overview
The stability, reliability, usability and performance of GDK has been quite an issue lately.
With @ashmckenzie moved to pastures new I suspect there will be even less capacity to focus on the GDK.
I have raised similar concerns in the past but this remains an issue.
I believe this is the number 1 problem preventing us from attracting new contributors and retaining existing ones.
Let's see if we can come up with any ideas/way forward
Impacted categories
The following categories relate to this issue:
-
gdk-reliability - e.g. When a GDK action fails to complete. -
gdk-usability - e.g. Improvements or suggestions around how the GDK functions. -
gdk-performance - e.g. When a GDK action is slow or times out.
Steps to replicate (optional)
Proposal (optional)
Environment (optional)
- Operating system name:
<!-- output ofuname -acommand --> - Architecture:
<!-- output ofarchcommand --> - The contents of your
gdk.yml(if any) - Ruby version:
<!-- output ofruby --versioncommand --> - GDK version:
<!-- output ofgit rev-parse --short HEADcommand -->