Hi Eric, Do you have suggestions on how ruby SDK’s should be distributed? Once Dinuka packages thrift generated ruby libraries and adds some higher order simplification API’s, can you please advise on what is the best practice for creating a gem and publishing it to a gem repo?
Thanks, Suresh > On Oct 21, 2020, at 3:02 PM, Dinuka Desilva <[email protected]> wrote: > > Hi Everyone, > > Following the other client sdks [1] available, I'm going to enable the ruby > sdk [2] for the airavata api. Meanwhile, I have a couple of points to discuss. > > 1) Should we follow a similar pattern for additional code (apart from what's > generated from thrift) introduced to the clients regardless of language? The > feasibility is also one aspect to be discussed. > > 2) What's the process of publishing the clients to public registries? > > Regards, > Dinuka > > [1] > https://github.com/apache/airavata/tree/master/airavata-api/airavata-client-sdks > > <https://github.com/apache/airavata/tree/master/airavata-api/airavata-client-sdks> > [2] https://github.com/apache/airavata/pull/265 > <https://github.com/apache/airavata/pull/265> >
