This repository has been archived by the owner on Mar 27, 2020. It is now read-only.

Design a process to systematic collect data about hardware differences in trigger #180

Open

jmatsushita opened this issue Jan 13, 2016 · 0 comments

Assignees

Labels

help wanted next question

Milestone

Member

jmatsushita commented Jan 13, 2016

For instance:

Off by one problem
Confirmation buzz halting on press.
Different system events triggering a potential false alert situation

jmatsushita assigned niccs

jmatsushita added this to the v1.6.x milestone

jmatsushita added question help wanted next labels

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.