Hi All, So then we can safely conclude that the repository management task is done only in AF - and working with whatever repositories would be done within either IDE.
On Fri, Apr 18, 2014 at 11:17 AM, Dimuthu Leelarathne <[email protected]>wrote: > Hi Jasintha, > > Additionally, could we get end-to-end user story that Dev Studio is > working on? > > thanks, > dimuthu > > > +1 since that would help the merging bit of the story. Thank you, Shiro > > On Fri, Apr 18, 2014 at 11:07 AM, Dimuthu Leelarathne > <[email protected]>wrote: > >> Hi Jasintha, >> >> Please see my comments inline. >> >> >> On Fri, Apr 18, 2014 at 10:56 AM, Jasintha Dasanayake >> <[email protected]>wrote: >> >>> HI >>> >>> According to offline discussion had with Dimuthu, our initial plan was >>> to provide this option (fork the code) in DevS. But as mentioned here, it's >>> important to figure out that forking task is a management task or >>> development task, based on that we can decide whether we provide this >>> option in DevS or not . >>> >>> >> I agree with Ramith on simplicity. Perhaps I wasn't clear, but was >> waiting for your mail on the discussion. What we discussed was to show the >> forked repo on the Dev Studio. This would make Codenvy and DevStudio in >> sync. What is more important is the merging of fork to master. If Dev >> Studio and Codenvy can manage the merging that would be very developer >> friendly. >> >> >> thanks, >> dimuthu >> >> >> >>> For me, it's look like a developer task , >>> >>> Thanks >>> /Jasintha >>> >>> >>> >>> >>> On Fri, Apr 18, 2014 at 10:09 AM, Ramith Jayasinghe <[email protected]>wrote: >>> >>>> I think not allowing users manage repositories in any where else is >>>> reasonable ( e.g. Dev Studio) because of following reasons: >>>> 1) If we support that through Dev Studio we might eventually have to >>>> support that in CodeEnvy ( to keep things uniform) isn't it? >>>> 2) Forking repositories is not a frequent operation compared >>>> commits/fetch operations and to me looks more like a management task ( - as >>>> the name implies -> repo management). >>>> 3) Simplicity. >>>> >>>> thoughts? >>>> >>>> >>>> >>>> On Fri, Apr 18, 2014 at 8:48 AM, Shiroshica Kulatilake >>>> <[email protected]>wrote: >>>> >>>>> Hi, >>>>> >>>>> *Context:* >>>>> In AppFactory an application version has a main repository. When a >>>>> application team is added to the application a developer can create their >>>>> own working repository which is known as the per-developer repository. So >>>>> all code changes pertaining to an application version would first be done >>>>> in a per-developer repository and then merged into the application repo. >>>>> >>>>> *Current management:* >>>>> When a developer logs into AF he/she can select which >>>>> application-version is to work on and then create a per-dev repo through >>>>> forking. This is done through the AF UI. >>>>> >>>>> *Code editing:* >>>>> Once a per-dev repo has been created the developer has the option to >>>>> either work on this through the Codenvy editor, through Dev-Studio or by >>>>> simply using git to get a clone of the per-dev repo and code using a >>>>> editor >>>>> of choice. >>>>> >>>>> In codenvy - to create a workspace it is a pre-requisite to have a >>>>> repository - if not one should first be created in AF. >>>>> >>>>> In Dev-studio - once a developer logs in his/her per-dev repos should >>>>> be displayed and then he/she would work on a selected repo. >>>>> >>>>> Once editing is done and tested the changes are pushed back to the >>>>> per-dev repo and then needs to be merged to the application-repo. >>>>> >>>>> *Question* >>>>> So the question is should we restrict repository management to only >>>>> AppFactory or whether we should provide it else where - e.g. Dev-Studio ? >>>>> >>>>> Do we consider the Codenvy editor and Dev-Studio to be the same for a >>>>> AF user or do we consider Dev-Studio as more than an IDE ? >>>>> >>>>> Thoughts ? >>>>> >>>>> Thank you, >>>>> Shiro >>>>> >>>>> -- >>>>> Shiroshica Kulatilake >>>>> >>>>> Architect, >>>>> WSO2, Inc. http://wso2.com/ >>>>> Phone: +94 776523867 >>>>> >>>>> _______________________________________________ >>>>> Architecture mailing list >>>>> [email protected] >>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>> >>>>> >>>> >>>> >>>> -- >>>> Ramith Jayasinghe >>>> Technical Lead >>>> WSO2 Inc., http://wso2.com >>>> lean.enterprise.middleware >>>> >>>> E: [email protected] >>>> P: +94 776715671 >>>> >>>> >>>> _______________________________________________ >>>> Architecture mailing list >>>> [email protected] >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> >>> -- >>> >>> *Jasintha Dasanayake * >>> >>> *Software EngineerWSO2 Inc. | http://wso2.com <http://wso2.com/> lean . >>> enterprise . middleware* >>> >>> >>> *mobile :- 0711368118 <0711368118> * >>> >> >> >> >> -- >> Dimuthu Leelarathne >> Architect & Product Lead of App Factory >> >> WSO2, Inc. (http://wso2.com) >> email: [email protected] >> Mobile : 0773661935 >> >> Lean . Enterprise . Middleware >> > > > > -- > Dimuthu Leelarathne > Architect & Product Lead of App Factory > > WSO2, Inc. (http://wso2.com) > email: [email protected] > Mobile : 0773661935 > > Lean . Enterprise . Middleware > -- Shiroshica Kulatilake Architect, WSO2, Inc. http://wso2.com/ Phone: +94 776523867
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
