As our company production maintain policy. we split SDK with language
as their own git repository.
We have different group member maintain them.
Works well for more than 5 years.
Appreciate your time.
Netroby
Goson zhang 于2020年6月3日周三 上午11:10写道：
>
> This is also a
This is also a point of confusion:
If the internal integration method is adopted, the advantage is that the
code base is together, and related users can modify and update at any time;
the disadvantage is how to build and compile in multiple languages.
If the external repository is built, the
How about make every client a dedicated repository.
For long term open source project. you may face long terms evolutions.
For example, mysql client has python, java, cpp, even nodejs client.
they have there own repository.
Put them all in one repository, would make out a huge git repository.
Plan to organize SDK in different languages according to the following
scheme:
tubemq-client-twins
tubemq-client-twins/tubemq-client-python
tubemq-client-twins/tubemq-client-cpp
tubemq-client-twins/tubemq-client-rust
tubemq-client-twins/tubemq-client-go
Construct tubemq-client-twins under the
All,
Now many contributors have mentioned issues wanting to contribute SDK for
different languages for TubeMQ, then the question is coming: how do we
place these SDK contents?
Put one in each language under the root directory?
Or put it in a separate directory, and then create a directory under
