1 Recently-proposed ideas (not yet prioritized)
2 ---------------------------------------------
3 • Set-up an announcements Slack channel that's auto fed by email to a
4 particular email address.
9 [These are not highest priority, but are so easy that they are worth
10 not delaying until after bigger features below.]
12 • Fix /puzzle dialog to reject a puzzle with the same URL as an
15 • Make /solved clear the state string for a puzzle.
20 • Group the puzzles in the Turbot home view by round
22 • Select round fields by default based on the round of the puzzle for
23 the channel in which `/puzzle` is invoked.
25 • Consider putting a round prefix into the channel name to group a
26 round's puzzles in the channel list.
31 • Figure out a good mechanism for linking puzzles to a meta-puzzle
32 that they feed into. Is this different or the same as the round
33 mechanism described above?
35 Hunt overview commands and filters
36 ----------------------------------
38 • Implement a /hunt command for giving an overview of the entire hunt,
39 (like the Turbot "home" view but available in any channel)
41 • For "/hunt" display only unsolved puzzles by default, but also allow
42 for "/hunt all" to display all puzzles
44 • On the Turbot home screen allow a dropdown for Unsolved/Solved/All
47 • For both "/hunt" and the Turbot home screen allow for a search
48 string that will search through puzzle names, puzzle IDs, puzzle
49 URLs, and state strings.
51 • Figure out what we want for tagging and searching on tags (beyond
52 what's already possible with the state strings).
57 • Implement a command to display the status of the current puzzle
58 within the channel. Need a name for this command.
60 • Extend the in-channel puzzle display to also allow editing of all
63 • Implement an /archive command to allow for easy archiving of a
64 channel for a solved puzzle (but make sure archived puzzles still
65 show up in global hunt/round views).
70 • Incorporate puzzle file uploads into the database state for each
71 puzzle. Any file uploaded to the Slack should get included
72 initially, but when editing a puzzle users can drop irrelevant files
73 or label relevant files.
75 Opt-out of channel invitations
76 ------------------------------
78 • Consider adding a user option to allow a user to opt-in to auto
79 invitation for all newly-created puzzle channels
84 • Have linked spreadsheets go into a specific Google Drive folder
86 • Come up with a better sheet template
88 • Put the puzzle's name into the primary tab of the sheet
90 • When copying tabs from the spreadsheet template, don't leave the
91 default "Copy of " text in place.
93 • Do something to make it more clear which tabs exist just as
94 backup/reference from the original template vs. any new tab a user
95 has created during the hunt. (Perhaps color the reference tabs
101 • Add support for recording/displaying those who have current roles
103 • Decide a good plan for audio/video calls for puzzles and integrate
106 • Inspect the CloudWatch logs for our Turbot AWS Lambda during the time
107 period of the active hunt, (October 24-31), find and diagnose any
108 errors that occurred during that period. Users reported seeing
109 "Trouble connecting" (probably during new-puzzle dialog submission)
110 as well as "dispatch_failed during /state command (perhaps due to a
111 state string that was very long).
113 • Think about some way to express solve priority
118 • Implement code to close out an entire hunt after the fact
121 • Figure out what tool we want to use for shared drawing on a puzzle
122 and integrate that into Turbot, (give a command that will generate a
123 new URL and will insert that URL into the Slack topic and the list
124 of links at the top of the sheet).