Dear Sébastien,
Considering the
version control repository and hosting service, we chose github for its widespread use for open-source projets, its simplicity and because it already includes essential tools for a developpement project.
We are open to integrate the tools into the standard python script (do you mean a subdirectory of the svn trunk?), if it is more relevant and if we do not loose the
required features.
Indeed, a migration would raise some questions:
* which Python version, coding conventions, dependencies... => in case of merging the scripts
* docstrings for automatic documentation generator (doxygen, sphinx?)
*
collaborative documentation => where to documentate the scripts. It is currently not possible in dokuwiki (see my post from last year left unanswered:
www.opentelemac.org/index.php/kunena/10-...cumentation-and-wiki) or in another way (
www.opentelemac.org/index.php/community-...python-scripts#23883)
* bug tracker
There is indeed efforts to be done to join forces in
Python scripts projects: python27 (python scripts in official telemac trunk), pputils, PostTelemac (based on python27), PyTelTools and many others (which are sometimes also not shared).
About the second point, I completely agree that most PyTelTools tools (in Classic interface) should be integrated in
PostTelemac plugin.
But for many reasons (mainly because we found QGIS/PostTelemac sometimes unstable and we had no solid experience on QGIS), we did not integrate them. The coming of QGIS3 (based on Python3 and Qt5) would raise the question again and facilitate its integration (as the code has to be revised/adapted).
Considering the workflow interface (to automate tasks), it should be kept outside a GIS environment as it is not dedicated to GIS visualization.
Finally, in my opinion, a set of Python scripts (at least most base classes/functions) for openTelemac should have their place in the official package library
pypi, in as much as it is documented and maintained. It should facilitate its usage and distribution.
Best Regards,
Luc