You are right DuniterPy is a library and libs group could be a right place for it.
DuniterPy is currently only used by Python clients located into clients/python group, which also makes sense to have it there.
DuniterPy is sharing the same labels with the other projects located in clients/python group.
We can fine tune the permissions in case a new contributor join in.
I think this is more convenient for us to keep DuniterPy repository into clients/python group.
In definitive, I am against this path change. I will let @vtexier express his opinion on that.
Thanks for the suggestion.
Moulchanged title from repository migration ? to Repository move to 'libs' group?
changed title from repository migration ? to Repository move to 'libs' group?
Now that you put the subject on the table, I realize that DuniterPy is more a toolkit than a library.
It overloads crypto libs to ease their use and provides classes, but also helpers and examples. And the heart of it is a client to ease python connection to BMA, WS2P, Cesium+ pods.
Thanks to help us clarify how to consider DuniterPy in the eco-system. Let's say it is a client toolkit.
We should let the repository in the current client path.