Hi, If this change (and others that we may discover through doing the QSP) are to be for AF in general then shouldn't we also have these as Jiras which get committed into the support branch as well ? Then such additions will go through the normal process of adding or improving the product - e.g. review, test etc..
Thank you, Shiro On Thu, Jul 18, 2013 at 8:11 AM, Asanka Dissanayake <[email protected]>wrote: > Hi samisa, > It is ok to have multiple app owners for an app. But at the mean time it > is restricted by UI. Sumedha and tried it using direct back end call > yesterday. It worked. There are slight changes in the front end to be > done. Once they are done we are good to go. > On 18 Jul 2013 07:23, "Samisa Abeysinghe" <[email protected]> wrote: > >> The more I try to use AF, the more I feel the need for $subject >> >> For e.g. we are developing a series of apps for internal WSO2 use. In >> here, Maheshica and myself act as the stakeholders of the apps. >> When I map the use case to AF, not being able to be owners of the same >> app as stakeholders is a major blocker. >> >> Here, app owner is a role, and there could be multiple users who play the >> role. >> >> -- >> >> Thanks, >> Samisa... >> >> Samisa Abeysinghe >> VP Engineering >> WSO2 Inc. >> http://wso2.com >> http://wso2.org >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- 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
