Transform it into a Cookiecutter Template

[JoaoCarabetta]

The Cookiecutter template is already an established way in the community to do project templates.

The advantages are:

• We will be able to publish this template in their template index and get more users
• It allows us to work within a framework. So we will not need to worry about how to install it into the system etc. We'll be able to focus on the template project structure.

Disadvantages:

• We will lose control on what is installed and how. So, the auto-installation of the local env will not be possible.
• It will not be something that we have installed on our computer that we can just call, e.g start_project. This will change to cookiecutter gh:JoaoCarabetta/project-templates or something like that. (we might create a group just to have a better name, like cookiecutter gh:start/data-science-template)

[fernandascovino]

It's nice to have more people using and collaborating, but I not comfortable about losing control of installed packages/tools. Although that from what I saw, the general folder structure is pretty much the same, isn't it? I think we can aggregate mostly with content / utilities (and probably this is what you meant by structure).

[JoaoCarabetta]

Maybe we can do a hybrid. I think it is possible to keep our command-line functionalities and to be a cookiecutter.