Restrict a Slack channel topic to 250 characters

[turbot] / TODO

diff --git a/TODO b/TODO
index da13ce62b1e02a1169e08d823e433136eaded615..34d5a36df807196a92c787cdf538ea3504e35cb5 100644 (file)
--- a/TODO
+++ b/TODO
@@ -3,27 +3,13 @@ Recently-proposed ideas (not yet prioritized)
 • Set-up an announcements Slack channel that's auto fed by email to a
   particular email address.
 
-Low-hanging fruit
------------------
-
-[These are not highest priority, but are so easy that they are worth
-not delaying until after bigger features below.]
-
-• Fix /puzzle dialog to reject a puzzle with the same URL as an
-  existing puzzle.
-
-• Make /solved clear the state string for a puzzle.
-
 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.
+• Group the puzzles in the Turbot home view by round
 
-• 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.
@@ -106,13 +92,6 @@ Un-prioritized items
 • 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