summaryrefslogtreecommitdiff
path: root/sifterapp/complete/bugs-issues-notes.txt
diff options
context:
space:
mode:
authorluxagraf <sng@luxagraf.net>2018-10-14 16:15:13 -0500
committerluxagraf <sng@luxagraf.net>2018-10-14 16:15:13 -0500
commit0c7dc15f893341577a88f692eade137bbcc568e3 (patch)
tree75810bda182570c5fed314291be4d4bdfa740d9f /sifterapp/complete/bugs-issues-notes.txt
initial commitHEADmaster
Diffstat (limited to 'sifterapp/complete/bugs-issues-notes.txt')
-rw-r--r--sifterapp/complete/bugs-issues-notes.txt18
1 files changed, 18 insertions, 0 deletions
diff --git a/sifterapp/complete/bugs-issues-notes.txt b/sifterapp/complete/bugs-issues-notes.txt
new file mode 100644
index 0000000..120f2f4
--- /dev/null
+++ b/sifterapp/complete/bugs-issues-notes.txt
@@ -0,0 +1,18 @@
+What a task "is"
+Thus,
+
+Best-guess order of magnitude. 1 minute. 1 hour. 1 day. 1 week. 1 month. (Anything longer than
+a month, and the task hasn't been sufficiently broken down into smaller
+pieces.)
+
+
+
+> More often than not, the goal of classifying things along those lines isn't
+> about *what* the individual issue is, but whether it's in or out of
+> scope. Whether something is in out of scope is a worthwhile facet for
+> classification, but using bug vs. feature as a proxy for that confuses the
+> issue. More often than not, in or out of scope is best handled through
+> discussion, not simply reclassifying the issue. When that happens,
+
+ Think "separate but equal".
+>