Hi Supun, Yes please, for now just create a new module in top level and submit a patch. We need to integrate it soon, hoping you will hang in after gsoc and lead those discussions.
When you take a patch, make sure your commits are preserved, so your contributions are recognized. Suresh On Aug 26, 2014, at 1:42 PM, Supun Nakandala <[email protected]> wrote: > Hi Suresh, > > I don't have a ICLA. > > The code I developed is a new implementation. It does not have any code level > relation to the current Airavata code base. Is it ok if I put it in the top > level directory of the Airavata code base and take patch? > > > On Tue, Aug 26, 2014 at 10:57 PM, Suresh Marru <[email protected]> wrote: > Hi Supun et al, > > I forgot to clarify one thing in this document (which I will do), if there is > a ICLA on file, we can use the github pull request branch approach. > > If you do not have a ICLA on file, we still require you to submit patches to > JIRA so the contributions to apache are explicit. > > You can check if you have preciously submitted a ICLA to ASF covering your > contributions at the website - http://people.apache.org/committer-index.html > under Unlisted CLAs. > > Suresh > > On Aug 26, 2014, at 12:58 PM, Marlon Pierce <[email protected]> wrote: > > > Suresh wrote a nice summary at > > http://airavata.apache.org/community/how-to-contribute-code.html > > > > Marlon > > > > On 8/26/14, 12:54 PM, Supun Nakandala wrote: > >> Hi all, > >> > >> What is the preferred way of contributing my GSOC work to the main code > >> base. Currently it is available at > >> https://github.com/scnakandala/airavata-userapi. > >> > >> Thank you > >> Supun > >> > > > > > > > -- > Thank you > Supun Nakandala > Dept. Computer Science and Engineering > University of Moratuwa
