Add a TODO file

With all the ideas gathered during the recent Teammate Hunt.

diff --git a/TODO b/TODO
new file mode 100644 (file)
index 0000000..f2f86f1
--- /dev/null
+++ b/TODO
@@ -0,0 +1,74 @@
+• Make links to puzzle and channel within sheet be actual links
+
+• Make /solved report to the main hunt channel
+
+• Make /solved rename the puzzle's sheet to indicate its solved status
+
+• Make /solved clear the state string for a puzzle.
+
+• Implement an /archive command to allow for easy archiving of a
+  channel for a solved puzzle
+
+• Implement code to close out an entire hunt after the face
+
+• 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
+
+• For both "/hunt" and the Turbot home screen allow for a search
+  string that will search through puzzle names, puzzle IDs, puzzle
+  URLs, and state strings.
+
+• Figure out a good mechanism for linking puzzles to a meta-puzzle
+  that they feed into.
+
+• Implement a command to display the status of the current puzzle
+  within the channel. Need a name for this command.
+
+• Extend the in-channel puzzle display to also allow editing of all
+  puzzle fields
+
+• Fix /puzzle dialog to reject a puzzle with the same URL as an
+  existing puzzle.
+
+• Allow a per-user option to opt out of being auto-invited to all
+  newly-created puzzle channels.
+
+• Figure out what we want for tagging and searching on tags (beyond
+  what's already possible with the state strings).
+
+• Decide a good plan for audio/video calls for puzzles and integrate
+  that into Turbot.
+
+• Inspect the CloudWatch logs for our Turbot AW 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).
+
+• Incorporate puzzle file uploads into the database state for each
+  puzzle. Any file uploaded to the Slack should get included
+  initially, but when editing a puzzle users can drop irrelevant files
+  or label relevant files.
+
+• 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).
+
+• Come up with a better sheet template
+
+• When copying tabs from the spreadsheet template, don't leave the
+  default "Copy of " text in place.
+
+• Do something to make it more clear which tabs exist just as
+  backup/reference from the original template vs. any new tab a user
+  has created during the hunt. (Perhaps color the reference tabs
+  differently.)
+