X-Git-Url: https://git.cworth.org/git?a=blobdiff_plain;f=TODO;h=9ea082ea1949249eb8cf09fdb5c33d77e3f227b8;hb=a1851eaee7e0f3312a370c9decbcc2e22ae214fa;hp=56fe24246ab6c0c52a48c904d441e8cc65f1275b;hpb=01ef7b71ad45338427c61722dbbee4fb19759661;p=turbot

diff --git a/TODO b/TODO
index 56fe242..9ea082e 100644
--- a/TODO
+++ b/TODO
@@ -1,24 +1,21 @@
-Low-hanging fruit
------------------
+Recently-proposed ideas (not yet prioritized)
+---------------------------------------------
+• Set-up an announcements Slack channel that's auto fed by email to a
+  particular email address.
 
-[These are not highest priority, but are so easy that they are worth
-not delaying until after bigger features below.]
+• Have Turbot explicitly report long state strings to the channel,
+  (since the implicit report from settting the abbreviated topic won't
+  have the whole message).
 
-• Fix /puzzle dialog to reject a puzzle with the same URL as an
-  existing puzzle.
-
-• Make /solved clear the state string for a puzzle.
+• In messages (like from /solved) don't use a raw user_name value from
+  the request, but instead some tagged version of a user ID (which
+  Slack will render as a display name).
 
 Round management
 ----------------
 
-• Add a /round command to create a new round. This is like a puzzle in
-  that it has its own channel, but different in that it doesn't accept
-  a solution, etc.
-
-• Add an (optional) drop-down at puzzle creation for selecting a known
-  round for a puzzle, (or creating a new round). Ensure this mechanism
-  allows for puzzles to exist in multiple rounds.
+• Select round fields by default based on the round of the puzzle for
+  the channel in which `/puzzle` is invoked.
 
 • Consider putting a round prefix into the channel name to group a
   round's puzzles in the channel list.
@@ -33,12 +30,6 @@ Meta-puzzle support
 Hunt overview commands and filters
 ----------------------------------
 
-• Implement a /hunt command for giving an overview of the entire hunt,
-  (like the Turbot "home" view but available in any channel)
-
-• For "/hunt" display only unsolved puzzles by default, but also allow
-  for "/hunt all" to display all puzzles
-
 • On the Turbot home screen allow a dropdown for Unsolved/Solved/All
   puzzles
 
@@ -62,6 +53,9 @@ Editing puzzle fields
   channel for a solved puzzle (but make sure archived puzzles still
   show up in global hunt/round views).
 
+• Ensure that both spreadsheet and channel are updated in response to
+  any changes.
+
 File uploads
 ------------
 
@@ -73,11 +67,6 @@ File uploads
 Opt-out of channel invitations
 ------------------------------
 
-• Drop the auto-invitation of all hunt members to every new channel.
-
-• Announce all newly-created puzzles in the main hunt channel, (so
-  that hunt members can easily click to join).
-
 • Consider adding a user option to allow a user to opt-in to auto
   invitation for all newly-created puzzle channels
 
@@ -103,16 +92,6 @@ Un-prioritized items
 
 • Add support for recording/displaying those who have current roles
 
-• Decide a good plan for audio/video calls for puzzles and integrate
-  that into Turbot.
-
-• Inspect the CloudWatch logs for our Turbot AWS Lambda during the time
-  period of the active hunt, (October 24-31), find and diagnose any
-  errors that occurred during that period. Users reported seeing
-  "Trouble connecting" (probably during new-puzzle dialog submission)
-  as well as "dispatch_failed during /state command (perhaps due to a
-  state string that was very long).
-
 • Think about some way to express solve priority
 
 Lower priority
@@ -120,8 +99,10 @@ Lower priority
 
 • Implement code to close out an entire hunt after the fact
 
-
 • Figure out what tool we want to use for shared drawing on a puzzle
   and integrate that into Turbot, (give a command that will generate a
   new URL and will insert that URL into the Slack topic and the list
   of links at the top of the sheet).
+
+• Think about using a URL shortener API for the sheet URLs (to leave
+  more room in a channel topic for state string content)