Naming and responsabilities

[bilboquet]

@aoudiamoncef @ASAPSegfault

We agreed that this repo should be named mass-proto and aim to centralize and factorize ou .proto files.

We agreed that the bindings for different languages we support should be in separate repositories.

I would like to suggest that we use the following convention for the repositories that contain the bindings (that's very close to what we discussed):
massa-proto-bindings-rs for Rust bindings
massa-proto-bindings-go for Go bindings
massa-proto-bindings-asfor AssemblyScript bindings

I just added bindings, but I found it better this way.

I have a question:
At least on the Rust side (and probably on the AS side too) we will soon have bindings both for the public API and for the node ABI.
Do you agree that they should both go into massa-proto-bindings-rs in different folders? Or do you think we should separate them?

[ASAPSegfault]

Regarding the name I have no problem with massa-proto-bindings-xxx.

I think the Rust ABIs should go in the same repository, only in different folders.

[bilboquet]

Overall organization

After some discussions today, we are unsure that bindings is a good name but we haven't found a better alternative so we go for massa-proto-bindings, at least for the moment.

We (@aoudiamoncef and I) aim to organize massa-proto-bindings so it provides the "generation scripts" and the generated bindings for the languages we support in dedicated directories in the suited format for the target language.
Hence, as an example for Rust we should have something like:

massa-proto-bindings/rust/
				 + Cargo.toml
				 + build.rs
				 + src/...

This way a client project for this bindings should be able to depends on it the cargo way. We're looking forward to see if it's ok for other languages (we're hoping for now). If it does not work we'll have to switch to the original proposition of one repository per language.

massa-proto-bindings should be automatically updated and tagged on event on massa-proto (push to main or tag).

About the dependencies

One aim of massa-proto and massa-proto-bindings is to have unambiguous versioning for projects that depends on each other via the proto definitions.
Below are represented some of those dependencies (not complete, not fully up to date or may represent what we aim).

Main focus here is given to the ABI and massa-sc-runtime. At the time of writing, the yellow links does not really exist, at least they are weak (wasm files used for tests are "hard wired" in massa-sc-runtime).
If I'm correct, .wasm originated from https://github.com/massalabs/massa-unit-tests-src we should make massa-sc-runtime tests depend directly onto the tests sources. This way we should ensure that at a point in time massa-sc-runtime and massa-*-sdk that depends upon a version of the .proto files are in sync.

Same scheme should apply the API side but I don't know well this part.

@damip @ASAPSegfault @AurelienFT feel free to share your thoughts :)

[bilboquet]

Updated version of the dependencies (at compile time).
Still not perfect but more precise.
Yellow link (that does not currently) still appears as a good way to ensure coherence of the system.

[bilboquet]

@Leo-Besancon @Eitu33 for reference purpose