The project currently has a lot of files that are generally unorganized and messy. They make sense due to proper naming by Poro but we should organize things a little.

Proposing this file structure:

.github/
src/
   # Contains the Python files (Config.py, FarmThread.py, etc) and the pip files (if possible), poro icon, any sound files, etc
config/ 
   # Contains config.json / config.yaml and the 'bestStreams.txt' 
setup/ 
   # Various pre-made setup scripts (for docker, deployment in other hosting services or OSes, as well as 'self build' tools) 
LICENSE
README.md
CONDUCT.md

This isn't the best structure, frankly the current is just fine, but I believe if we can organize the project better and with subfolders, developing and maintaining it will become a piece of cake.

This shouldn't affect the end user as they download the build version anyways, but rather developers that wish to jump in the project, so it's definitely beneficial!