X-Git-Url: https://git.cworth.org/git?p=turbot;a=blobdiff_plain;f=TODO;h=a163fc8a9f261680c30a40c5248a37783422789f;hp=edbafc5489a9de38a7900716e07846a403339262;hb=HEAD;hpb=00f6c963b93d717a415d53933784f20c963375f9 diff --git a/TODO b/TODO index edbafc5..a163fc8 100644 --- a/TODO +++ b/TODO @@ -1,68 +1,65 @@ +Ordered punch-list (aiming to complete by 2021-01-08) +----------------------------------------------------- + +• Make the /hunt command drop from the database any rounds that have 0 + puzzles in them + Recently-proposed ideas (not yet prioritized) --------------------------------------------- -• Set-up an announcements Slack channel that's auto fed by email to a - particular email address. +• Need a more direct way to ask for help and to find who needs + help. Something like /state but with announcements in the main + channel and maybe a periodic "Here's where people need help" post or + something like that. -Low-hanging fruit ------------------ +• Fix all message posting in Slack to avoid limits, (breaking big + messages (is it 100 blocks? need to check) into multiple smaller + messages). -[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. +• Allow a hunt (and perhaps a round) to have multiple URLs -• Make /solved clear the state string for a puzzle. +• Would it be helpful to have some sort of "tools" command to collect + pointers to useful tools and allow for searching of them? -Round management ----------------- +• Investigate what from snap2 we could incorporate into our sheets: -• Group the puzzles in the Turbot home view by round + https://github.com/kevinychen/snap2 -• Select round fields by default based on the round of the puzzle for - the channel in which `/puzzle` is invoked. +• Watch the recent hunt workshop that had some recommendations on + tools and see what from that we should incorporate -• Consider putting a round prefix into the channel name to group a - round's puzzles in the channel list. +• Think about writing some custom solving tools, (like Qat, or + Nutrimatic, or Snap2, etc.) -Meta-puzzle support -------------------- +• Fix slash commands to pass off processing to a separate Lambda and + then return immediately (removing the annoying "operation timeout" + complaints from Slack even when the command works exactly as it + should). -• Figure out a good mechanism for linking puzzles to a meta-puzzle - that they feed into. Is this different or the same as the round - mechanism described above? +• Hunt creation should set the hunt channel's topic (we recently added + this for hunt editing at least) -Hunt overview commands and filters ----------------------------------- +• The Turbot Home view and the /hunt output should emit the hunt links + and state string (similar to how puzzle links and state strings are + already implemented). -• Implement a /hunt command for giving an overview of the entire hunt, - (like the Turbot "home" view but available in any channel) +Round management +---------------- -• For "/hunt" display only unsolved puzzles by default, but also allow - for "/hunt all" to display all puzzles +• Select round fields by default based on the round of the puzzle for + the channel in which `/puzzle` is invoked. + +Hunt overview commands and filters +---------------------------------- • 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 what we want for tagging and searching on tags (beyond - what's already possible with the state strings). - -Editing puzzle fields ---------------------- - -• 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 - -• Implement an /archive command to allow for easy archiving of a - channel for a solved puzzle (but make sure archived puzzles still - show up in global hunt/round views). +• On the Turbot home screen add a text box for a search hstring (to + work like the search string now available in "/hunt"). File uploads ------------ @@ -72,24 +69,17 @@ File uploads initially, but when editing a puzzle users can drop irrelevant files or label relevant files. -Opt-out of channel invitations +Opt-in for channel invitations ------------------------------ -• Consider adding a user option to allow a user to opt-in to auto - invitation for all newly-created puzzle channels +• Consider adding a user option to allow a user to opt-out of the auto + invitation for all newly-created puzzle channels, (we have a + hard-coded list inside Turbot right now called + AUTO_INVITE_DENY_LIST) Sheet-related fixes ------------------- -• Have linked spreadsheets go into a specific Google Drive folder - -• Come up with a better sheet template - -• Put the puzzle's name into the primary tab of the sheet - -• 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 @@ -100,25 +90,18 @@ 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). + Maybe this should just be a "Post" in the main hunt channel, (and + need not have any direct Turbot support?) • Think about some way to express solve priority 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)