On Jul 25, 2012, at 11:35 AM, Raminderjeet Singh wrote: > What is that location? I think it should be close to Airavata API as API's > may change with time.
The web version is currently in sandbox area [1]. The reason I suggest sandbox to start with is to follow the process for all new incumbent major features/components. I noticed that when developing API's there was major code shipping with the releases which did not have good test coverage among other unproven aspects. I was getting uncomfortable during releases but since we were well underway into the development I did not bring out a discussion. I fully acknowledge the fact that even the main core components still do not have good test coverage and we all should address it. With API's stabilizing now and highlighting with the current 0.4 RC, I suggest we should start following a process hence forth. So the sandbox projects can liberally be developed getting feedback as we mature than and finally focus on packaging and integrating with a unified build. Once the components mature, we can move them into an appropriate place in trunk. Cheers, Suresh [1] - https://svn.apache.org/repos/asf/incubator/airavata/sandbox/xbaya-web/ > Raminder > > On Jul 25, 2012, at 10:14 AM, Suresh Marru wrote: > >> I think they should go along side web version of XBaya to start with. >> >> Suresh >> >> On Jul 24, 2012, at 6:04 PM, Raminderjeet Singh wrote: >> >>> Hi Dev, >>> >>> I am working on creating a Airavata REST service using API's. I have >>> created a Epic https://issues.apache.org/jira/browse/AIRAVATA-521. I have >>> attached the Template project to the JIRA for suggestions. >>> >>> My question to community is where does this code belong? >>> trunk/sandbox/extras. I think it belong to trunk to keep this updated with >>> latest version and new API's. >>> >>> Thanks >>> Raminder >>> >>> >> >
signature.asc
Description: Message signed with OpenPGP using GPGMail
