+1, keeping code on your laptop and not using an online code repo like
GitHub is a terrible practice.
More generally, you should be submitting patches to Airavata with your
work as it moves along. We do not want 1 big patch at the end of the
GSOC. Break your project up into ~2 week chunks and submit patches
frequently.
Marlon
On 6/16/14, 2:25 PM, Lahiru Gunathilake wrote:
Never keep code in your laptop, if your laptop crash at last minute you
will fail the GSOC project.
On Mon, Jun 16, 2014 at 2:09 PM, Nipun Udara <[email protected]> wrote:
Hi lahiru
Thanks for the advice. still in my machine.i will keep it on git hub and
send a mail
Regards
Nipun
On Mon, Jun 16, 2014 at 11:17 PM, Lahiru Gunathilake <[email protected]>
wrote:
Hi Nipun,
Thanks for the update and I can see a progress in your work.
Where are you keeping the code ? I suggest you to keep it in your own git
hub and please write some readme how to setup your handlers in airavata or
atleast how to test your code by running a test case and send an email to
the list. So we can test your code.
Once your finish the GSOC we can commit the code to apache github repo.
Regards
Lahiru
On Mon, Jun 16, 2014 at 1:25 PM, Nipun Udara <[email protected]>
wrote:
Hi all
So far i have write handlers and provider to run jobs on ec2 with string
type and S3type input and looking to add URI type
Regards
Nipun Udara
--
System Analyst Programmer
PTI Lab
Indiana University
--
Nipun Udara
*Undergraduate*
*Department of Computer Science & Engineering*
*University of Moratuwa*
*Sri Lanka*
