Contributions to MFT related issues: Firstly thank you for these fine contributions. Please note that you are contributing to a code base which has a quick path to production, so we need to ensure quality over quantity. Seems like there are contributions but are waiting for Dimuthu’s review. Looking at the PR’s, most of the reviews seems to be for basic code quality and best practices as opposed to deeper architectural concerns. Instead of waiting for Dimuthu, may be you guys can help each other out and record these reviews as a contribution part of your projects?
Here are PR’s which need review, please volunteer: https://github.com/apache/airavata-mft/pull/10 <https://github.com/apache/airavata-mft/pull/10> https://github.com/apache/airavata-mft/pull/11 <https://github.com/apache/airavata-mft/pull/11> https://github.com/apache/airavata-mft/pull/12 <https://github.com/apache/airavata-mft/pull/12> In addition, please consider contributing the following: * Documentation on how to configure various transports. Because of the variance of the cloud storages and multiple ways to work with them, it is important to capture which approach is being used in the contributed implementation. * Examples on using each of these transports as a stand alone as well as examples covering multiple transports. Lastly, please do not restrict yourself to the transport you contributed, do try examples with other contributions, thats a good way to review and critique as well. Thanks for all your efforts, MFT is shaping nicely and now all of you should be proud of being part of its developer community, Suresh
