[bisq-network/projects] Establish support case tracking process (#5)

[Chris Beams]

Closing as dropped. Per https://github.com/orgs/bisq-network/teams/dao/discussions/13, I'll be stepping down from the role of Support Team Lead (bisq-network/roles#102), and rather than leave this open or try to hand it off to someone else (e.g. the new team lead), it's probably better to call the shot that this has, in the end, not been important enough to get done, and to just drop it. We are unable to really measure support activities without this kind of tracking, but user support is no longer a serious pain point for the project; it appears to be going pretty smoothly and perhaps the current process, e.g. coverage calendar and escalation process is "good enough" for the time being. The one thing that's really missing without this kind of tracking in place is getting good data about which critical bugs and issues are causing issues to land in support, but in practice, we know what most of these are anyway; it's just a matter of actually fixing / addressing them.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/projects/issues/5#issuecomment-640459896
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200608/3f0657f9/attachment-0001.html>