+Ordered punch-list (aiming to complete by 2021-01-08)
+-----------------------------------------------------
+
+• Add an "archive channel" button that is provided out after a puzzle
+ has been solved.
+
+• Add tags to the puzzle edit interface
+
+• Make the /hunt command drop from the database any rounds that have 0
+ puzzles in them
+
Recently-proposed ideas (not yet prioritized)
---------------------------------------------
+• 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.
+
+• Fix all message posting in Slack to avoid limits, (breaking big
+ messages (is it 100 blocks? need to check) into multiple smaller
+ messages).
+
• Set-up an announcements Slack channel that's auto fed by email to a
particular email address.
(since the implicit report from settting the abbreviated topic won't
have the whole message).
-• 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).
+• Allow a hunt (and perhaps a round) to have multiple URLs
-Round management
-----------------
+• Provide an "Archive channel" button in the channel when outputting
+ the message that results from /solved.
-• Select round fields by default based on the round of the puzzle for
- the channel in which `/puzzle` is invoked.
+• Would it be helpful to have some sort of "tools" command to collect
+ pointers to useful tools and allow for searching of them?
-• Consider putting a round prefix into the channel name to group a
- round's puzzles in the channel list.
+• Investigate what from snap2 we could incorporate into our sheets:
-Meta-puzzle support
--------------------
+ https://github.com/kevinychen/snap2
-• 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?
+• Watch the recent hunt workshop that had some recommendations on
+ tools and see what from that we should incorporate
-Hunt overview commands and filters
-----------------------------------
+• Think about writing some custom solving tools, (like Qat, or
+ Nutrimatic, or Snap2, etc.)
-• Implement a /hunt command for giving an overview of the entire hunt,
- (like the Turbot "home" view but available in any channel)
+• 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).
-• For "/hunt" display only unsolved puzzles by default, but also allow
- for "/hunt all" to display all puzzles
+• Hunt creation and editing should set the hunt channel's topic
-• 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.
+• There should be a state string in the hunt (and support for the
+ /state command) so that there's a supported way to edit the hunt
+ channel's topic without destroying its links.
-• Figure out what we want for tagging and searching on tags (beyond
- what's already possible with the state strings).
+• 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).
-Editing puzzle fields
----------------------
+Round management
+----------------
-• Implement a command to display the status of the current puzzle
- within the channel. Need a name for this command.
+• Select round fields by default based on the round of the puzzle for
+ the channel in which `/puzzle` is invoked.
-• Extend the in-channel puzzle display to also allow editing of all
- puzzle fields
+Hunt overview commands and filters
+----------------------------------
-• 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 allow a dropdown for Unsolved/Solved/All
+ puzzles
-• Ensure that both spreadsheet and channel are updated in response to
- any changes.
+• 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
------------
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
Sheet-related fixes
-------------------
-• Have linked spreadsheets go into a specific Google Drive folder
+• Add the solution to the sheet name on solved: "[TITLE] - Solved [ANSWER]"
-• 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.
+• Use a hunt-specific Google Drive folder for creating all the
+ sheets. (This way, we can share out the "mh2021" folder to all team
+ members so that people can browse the sheets that way if wanted, and
+ have backup access to all of them on the off chance of Slack not
+ being available.)
• Do something to make it more clear which tabs exist just as
backup/reference from the original template vs. any new tab a user
• Add support for recording/displaying those who have current roles
+ 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
projects / turbot / blobdiff