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. Day by day goes. it make huge history, take so much storage space. People will hard to work on it . too many conflicts . Appreciate your time. ---------------------------- Netroby Goson zhang <[email protected]> 于2020年6月2日周二 下午7:40写道： > > 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 project root directory as the > general directory of all multi-language SDKs, each language builds > sub-directories under tubemq-client-twins directory according to > tubemq-client-xxx (language name) for independent code storage and > management, to avoid too many problems in the root directory. > > Let's see if there is a problem, if there is no problem, we will follow > this idea to create an issue. > > Goson zhang <[email protected]> 于2020年5月29日周五 下午11:16写道： > > > 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 this > > separate directory for each language? > > Or is there a better solution? > > > > Welcome everyone to discuss this topic and post your suggestions! > > > > Thanks! > >
