Please refer to : " [Gsoc 2014][proposal 5: WSO2 Deployment Engine] Implementation guide " mail on [email protected].
Thanks and regards, Thilina Piyasundara Systems Engineer (DevOps) M: 071-775-0006 Blog: blog.thilina.org WSO2, Inc. <http://wso2.com/> lean . enterprise . middleware On Tue, Mar 18, 2014 at 1:06 PM, Tharindu Peiris <[email protected]>wrote: > Thilina, > > Have some confutions with technologies that we may use for this. > so if you can give me a roughf idea about tecnologies that may easy for me > and to go to a beeter proposal. > > if you have a idea about and feeling free please make a reply to me. > including what kind of technologies that you prefer for UI development, > internal process and etc... > > Thanks. > Tharindu. > > > On Mon, Mar 17, 2014 at 2:39 AM, Thilina Piyasundara <[email protected]>wrote: > >> Yes, that's better. >> >> Thanks and regards, >> >> Thilina Piyasundara >> Systems Engineer >> (DevOps) >> M: 071-775-0006 >> Blog: blog.thilina.org >> >> WSO2, Inc. >> <http://wso2.com/> >> lean . enterprise . middleware >> >> >> On Mon, Mar 17, 2014 at 2:49 PM, Tharindu Peiris < >> [email protected]> wrote: >> >>> Thilina, >>> >>> yes, thanks and you are right , wide scope may make some confusions. >>> I would try to minimize it's scope and make it more achievable. >>> I suppose to make a better timeline with a rapid development plan. >>> version by version development.(suppose 2 or 3 versions ) >>> What would you think about..? >>> >>> Tharindu. >>> >>> >>> On Mon, Mar 17, 2014 at 9:55 AM, Thilina Piyasundara >>> <[email protected]>wrote: >>> >>>> Hi Tharindu, >>>> >>>> Its great to hear that you're interested in this project. >>>> Your ideas are great but you need to think about the timeline you got. >>>> >>>> As we know, it takes lots of time to development this tool specially >>>> those UI components. >>>> Our main objective is to provide a rich user experience. So you need to >>>> spend lot of time and effort on those UI/UX related drag and drop, >>>> validation, etc. features. >>>> >>>> For the record, there is no best solution we can pre-define. Everything >>>> will depend on the situation, customers requirement and the cost factor. >>>> We need to generate a 'json' file to save the deployment as a template. >>>> Uses can use these templates to start their deployment but they can/will >>>> change/modify it according to the situation. Don't spend much time on >>>> documentation. We will provide the puppet modules for you. And try to use >>>> Apache-Jclouds to interact with IaaS. >>>> >>>> I hope you read this doc : >>>> wso2-oxygen-tank.10903.n7.nabble.com/attachment/93081/0/GSoSProposalsWSO2DeploymentEngine.pdf >>>> >>>> Please contact [email protected] if you need further clarification. >>>> >>>> >>>> Thanks and regards, >>>> >>>> Thilina Piyasundara >>>> Systems Engineer >>>> (DevOps) >>>> M: 071-775-0006 >>>> Blog: blog.thilina.org >>>> >>>> WSO2, Inc. >>>> <http://wso2.com/> >>>> lean . enterprise . middleware >>>> >>>> >>>> On Sat, Mar 15, 2014 at 7:40 AM, Tharindu Peiris < >>>> [email protected]> wrote: >>>> >>>>> hi, >>>>> >>>>> I would like to make a contribution for GSOC 2014, WSO2 project >>>>> proposal 5, >>>>> I create some basic proposal structure including my ideas about the >>>>> project. >>>>> you can go with from fallowing link and feeling free to make a comment >>>>> what are the opinions about and have you expect some more. >>>>> >>>>> [1] >>>>> https://docs.google.com/document/d/1d6uhll7HoxENECf3uR7df7M153n8bFM6uGzl6_PMZNY/edit?usp=sharing >>>>> >>>>> Thanks, >>>>> Tharindu. >>>>> >>>> >>>> >>> >> >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
