Return-Path: X-Original-To: apmail-airavata-dev-archive@www.apache.org Delivered-To: apmail-airavata-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EF76A1073D for ; Fri, 13 Sep 2013 16:09:57 +0000 (UTC) Received: (qmail 70579 invoked by uid 500); 13 Sep 2013 15:47:50 -0000 Delivered-To: apmail-airavata-dev-archive@airavata.apache.org Received: (qmail 68687 invoked by uid 500); 13 Sep 2013 15:46:43 -0000 Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@airavata.apache.org Delivered-To: mailing list dev@airavata.apache.org Received: (qmail 63092 invoked by uid 99); 13 Sep 2013 14:42:37 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Sep 2013 14:42:37 +0000 Received: from localhost (HELO 149-160-244-129.dhcp-bl.indiana.edu) (127.0.0.1) (smtp-auth username smarru, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Sep 2013 14:42:37 +0000 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Subject: Re: [GSOC] Status of integrated tutorial From: Suresh Marru In-Reply-To: Date: Fri, 13 Sep 2013 10:42:35 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <43AB5277-0C49-41AB-9C43-3AD465086E2B@apache.org> References: <58D260E2-5457-44AD-A630-8EA67494B4A6@apache.org> <834B71BA-7CD1-4B60-BD13-4AE33E361B03@apache.org> To: dev@airavata.apache.org X-Mailer: Apple Mail (2.1508) On Sep 13, 2013, at 2:42 AM, Danushka Menikkumbura = wrote: > I think the objective of tonight's hangout should be to decide on the = way forward to get a simple workflow running end-to-end ASAP. I don't = think it has to be a perfect solution, but something that demonstrates = feasibility of the underlying architecture. Presumably it may have = loopholes, a lot of room for optimization, may not work with = edge/extreme conditions, but would give the impression that we can make = it perfect when some additional effort put in. If we can get there, I = believe we can revisit and take it further from there easily (I mean = post GSoC). + 1. By no means its expected all of you will magically solve all the = challenging technical issues in 2 weeks. But it needs to get to place = where the code has to work with all known limitations and bring out next = TODO's.=20 Suresh >=20 > Thanks, > Danushka=20 >=20 >=20 > On Fri, Sep 13, 2013 at 6:30 AM, Suresh Marru = wrote: > Hi All, >=20 > If you recollect we had some key goals and pre-requite for Airavata = GSoC projects [1]. The key one is to have an integrated Masters projects = and a collective team responsibility to have a working project. I think = collectively the integration really fell through the cracks and got = deferred until the end. Inspite of the mid-term warning that we need to = have a big picture and how each components will play together, we really = unable to get a hello world end to end tutorial. Can we please get to = it? Its really hard to judge individual contributions. More over if the = integration does not come together, all of the code will RIP in sandbox. >=20 > Can you guys sprint the last mile and get the code integrated? We see = a small spike in discussion and nothing beyond that. Can we get all = patches in? In contrary to typical GSoC contributions, haven't seem = commits in last weeks. >=20 > Can you all have a hangout tonight (India/SL) Friday at a time which = works for all and summery clearly a day to day roadmap from now to the = firm pencil down data of Septmeber 23rd [3]? Please see the timeline = closely, the suggested pencil down date is 16th and a full code = documentation, test coverage and all should be done by 23rd. Every one = has to really work hard to pass the finals with all gsoc requirements. >=20 > Suresh >=20 > [1] - http://markmail.org/message/rmotieckqj3a4xxv > [2] - http://markmail.org/thread/rw2qzpukheow5aiy > [3] - http://www.google-melange.com/gsoc/events/google/gsoc2013 >=20 > On Sep 1, 2013, at 5:17 PM, Subho Banerjee = wrote: >=20 > > > > > > > > On Sun, Sep 1, 2013 at 12:51 PM, Danushka Menikkumbura = wrote: > > > > 1. Using the Registry API inside AngularJS. > > > > It would be great if Sanchit and Subho could help me on this. > > > > What exactly are we trying to solve here?. Maybe I can take a look = at it too. > > > > > > I am trying to figure out if we can somehow use the code Shameera = has written directly in the angular service. Till now I have been = unsuccessful at getting this to work. I have tried two techniques - > > > > 1. Use Shameera's object in an Angular service. This doesn't work at = all. > > 2. Edit Shameera's code to add the $promise values to update the = Angular models. This seems to work intermittently, I think it comes down = to whether a certain set of events fire in the right order. So on the = whole this method was unsuccessful. > > > > It will be great if you guys can suggest (and maybe help implement) = what else we can do to make Shameera's code work out of the box in an = Angular webapp. > > > > The last option we have would be to probably re-write most of the = registry API JS client into an Angular service. Now this creates a = problem that we will end up having two JS clients. Maintaining two of = these will not be easy. > > > > > > -- > > Cheers, > > Subho >=20 >=20