TheOdinProject
Add new command (!scope ?) for questions outside the scope of TOP
Checks
- [X] I have thoroughly read and understand The Odin Project Contributing Guide
- [X] The title of this issue follows the
command name: brief description of requestformat, e.g./help: add optional @user parameter
Do you want to be assigned to this issue?
- [X] I would like to be assigned this issue to work on it
Description of the Feature Request
The Discord server gets a lot of general programming questions, outside the scope of TOP, which per the rules aren't answered. It would be neat to have a command that outputs a boilerplate message about how this isn't server for their questions. While I am aware that for the most part this bot is migrating to slash commands, I would propose that in this instance a text command version is also added, given I could see it being used (mostly) in a running message
Acceptance Criteria
- [ ] A new slash command is created which when used prints a message about what questions are in scope (proposed name `/scope`)
- [ ] A new text command is created which uses the same message (proposed name `!scope`)
Additional information
No response
This is fantastic! May I also suggest including a link to the following section in Community Rules
Ask questions about content or projects in our curriculum The purpose of this server is to support people when they run into issues doing our curriculum. This allows our volunteers to know the exact scope of your problem and correct any poor advice. In addition, this limited scope helps us identify areas in our curriculum that we need to improve.
Do not ask for advice/help on homework or personal projects, even if the topic is covered by our curriculum. Instead, research other servers/communities that offer general programming help.
Only just spotted this got proposed in the discord suggestions a few weeks ago: https://discord.com/channels/505093832157691914/1277817788467122237. Willing to step aside if they still want to do it
Thanks @Asartea for raising this issue. I understand where you are coming from. But for now, we are not going to pursue this specific slash (or inline) command.
