Dear @NLeSC/python-template-nlesc-team,

As you might know in the last couple of weeks a few of us (Patrick, Sander and myself) were actively engaged with the python template trying to address some of the points that we have discussed in our last meeting. Namely,

• template"versions";
• possible migration tocopier while remaining feature complete;
• possible collaboration with SS-NES project.

About SS-NES.
SS-NES project team is currently developing a new python template that originates from our template. After the meeting with them, Sander nicely summarised the main reasons as following:

• The current NLeSC template is not 'modular' and contains a number of features whose use may not be clear to novice users. Such features should be optional.
• Such optionality also works more easily withcopier instead ofcookiecutter, which is what the NLeSC template uses.
• By usingcopier, the user can upgrade their project later using the same template, another feature the NLeSC template does not support.
• A later addition is that they want to use the machine-readable output of the SMP (Software Management Plan) decision tree tool to setup up as much of the template as possible: this already asks for the name of your software, which license you choose, whether you will be setting up certain kinds of documentation, etc.

Since SS-NES project goals largely overlap with our goals we consider collaboration with them as a feasible option. Patrick has already discussed the above with the TLs, and the consensus was that it might be a good idea to work with SS-NES as in addition to addressing template issues it will also help us to build momentum, broaden community and achieve long term sustainability.

Now, we are wondering how you feel about it and if there are any major objections?