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 Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
