new fortean

[feisty_meow.git] / scripts / notes / info_overload_report.sh

diff --git a/scripts/notes/info_overload_report.sh b/scripts/notes/info_overload_report.sh
index 67283b71986ef7b32db806ba7dbb9fd2301d0680..3809113815856a698ff6ea55441d83543c6907b2 100644 (file)
--- a/scripts/notes/info_overload_report.sh
+++ b/scripts/notes/info_overload_report.sh
@@ -1,7 +1,7 @@
 
 # these metrics are how bogged down we are in to-do type items.
 
-REPORT_FILE="$HOME/cloud/overload_history.txt"
+REPORT_FILE="$HOME/cloud/fred_stats/overload_history.txt"
 
 # given a path, this will find how many items are under it, ignoring svn and git files, plus
 # other patterns we happen to notice are not useful.
@@ -101,13 +101,28 @@ full_report+="count\tcomplexity\tweight (kb)\tcategory\n\
 analyze_hierarchy_and_report ~/cloud/urgent "high priority"
 
 # notes are individual files of tasks, usually, although some are combined.
-analyze_hierarchy_and_report ~/cloud/grunty_notes "grunty notes"
+analyze_hierarchy_and_report ~/cloud/grunty_notes "grunty notes (external facing things?)"
 
 # feisty notes are about feisty meow(r) concerns ltd codebase development.
-analyze_hierarchy_and_report ~/cloud/feisty_notes "feisty meow notes"
+analyze_hierarchy_and_report ~/cloud/feisty_notes "feisty meow notes (code related)"
 
 # home notes are a new top-level category; used to be under the grunty.
-analyze_hierarchy_and_report ~/cloud/branch_road "hearth and home notes"
+analyze_hierarchy_and_report ~/cloud/branch_road "hearth and home notes (branch road, yo!)"
+
+# games and fun stuff.  not sure why these count as backlog, but whatever.
+analyze_hierarchy_and_report ~/cloud/games_yo "games, yo!"
+
+# some source code that needs to be sucked into other places, other codebases.  they are not
+# supposed to pile up here.  but they have, so we track them.
+analyze_hierarchy_and_report ~/cloud/scavenging_source "source scavenging"
+
+# and then count up the things that we think will be cleaned soon, but one thing we have learned
+# unsorted files haven't been categorized yet.
+analyze_hierarchy_and_report ~/cloud/disordered "unsorted files"
+
+# we now consider the backlog of things to read to be a relevant fact.  this is going to hose
+# up our weight accounting considerably.
+analyze_hierarchy_and_report ~/cloud/reading "reading list"
 
 # scan all the items declared as active projects.
 analyze_by_dir_patterns "active items" ~/cloud/active*
@@ -121,18 +136,6 @@ analyze_by_dir_patterns "job and work tasks" ~/cloud/job*
 # scan all the trivial project folders.
 analyze_by_dir_patterns "trivial items" ~/cloud/trivia*
 
-# source examples need to be sucked into other places, other codebases.  they are not
-# supposed to pile up here.
-analyze_hierarchy_and_report ~/cloud/example_source "source examples"
-
-# and then count up the things that we think will be cleaned soon, but one thing we have learned
-# unsorted files haven't been categorized yet.
-analyze_hierarchy_and_report ~/cloud/disordered "unsorted files"
-
-# we now consider the backlog of things to read to be a relevant fact.  this is going to hose
-# up our weight accounting considerably.
-analyze_hierarchy_and_report ~/cloud/reading "reading list"
-
 full_report+="================================================================\n\
 "
 full_report+="$(format_report_line "$total_overload" "$total_weight" "$total_complexity" "total overload")"