Split `massa-client` code between REPL abstractions (external crate) and our business commands (that relay on `massa-models`)

[AureliaDolo]

To make external contributions easier (the Russian client looks pretty)

[AureliaDolo]

@yvan-sraka @adrien-zinger I'm quite not sure on how to do that. Is it possible to fork only a part of a repo ?

[adrien-zinger]

There is multiple possibilities, maybe we want to keep the source code here because when we tag the CI builds a release for the client and for the node. A solution, for me, would be to use a submodule with git. But I want to check if the clone command wont be altered.

Maybe the CI can also build another repo on tagging. It would be better.

[yvan-sraka]

I vote for this! We could just have an external repo and use cargo install to make it available to CI :)

[damip]

sounds good but implies also splitting away "massa-models" which is a dependency the client shares with massa-node. I'm afraid we are heading for too much complexity with this. Marking it for refactoring discussion tho

[AureliaDolo]

@AurelienFT @yvan-sraka was this done ?

[AurelienFT]

@AurelienFT @yvan-sraka was this done ?

The PR is still open so I don't think

[damip]

This was done in massa-sdk I think. Closing ?