Adding some guidelines for making patch_files/templates for developers/maintainers
It would be nice idea to have a workflow to create patch files (compatible with taurus) if user wants to install a new software.
If we need to add a new framework to the repository
Step 1 - Create an easybuild file with name: <framework>.eb
Step 2 - Create a patch file with name: <framework>.patch
Step 3 - Create a test example for the framework.
Don't forget to change set the permissions to "755"
Step 4 - Update Makefile
Step 5 - Update CI file and update Makefile target for CI job