VACATION ROUND-UP: New issues and bot's code refactor #32
Description
With the new school year starting, it is time to make some changes like normalize new issues and work schemes.
Due to the new semester starting from now on all new features or fixes will be documented with proper issues. This will help manage time and work done.
1. Issues normalization
With both web and bot processes running from the same repo ( not much point separating them now ), issues should be separated one from another.
I suggest using [ BOT ] in front of the new issue's name for ones bot related, and [ WEB ] for web ones. Use example in issue:
Also I'll make sure to keep issues well described and updated, with less issues too short for understanding.
2. More issues in sight
As mentioned before, there will be more issues made not only for fixes or things-to-fix. Every new feature ( commands, modes etc. ) should have issues with description of enhancement or addition. Well, it isn't necessary but can make adding new things more organized.
I will think more about it, all additions will be added in the comment below.
3. Old issues
With the bot's code refactor, its old issues are quite pointless right now. Will probably keep them for now, but guess will be utilized sooner or later.
Some of them may be transferred into one TO DO issue with summarization of these ideas.
Special thanks for everyone's help!
Hear you soon!