Hi, User invitation and update for application owner implemented and tested in 105 machine. But there are several problems arises. 1-API manager subscriptions are only allowed for the user that created the app 2-and many other places that checks whether the logged in user is app owner, 3-even in block level method such as getAppOwner needs to be changed
So IMHO , we should not push this to live until we get these solved. On Thu, Jul 18, 2013 at 11:27 AM, Shiroshica Kulatilake <[email protected]>wrote: > Hi All, > > The requirement of Samisa is also part of the aPaaS story as Sameera > pointed out very correctly. > > So we need to think in that line as well. > > Will we be doing a similar QSP to introduce aPaaS inhouse ? if not will we > be migrating this into aPaaS ? > > Thank you, > Shiro > > > On Thu, Jul 18, 2013 at 10:05 AM, Manisha Gayathri <[email protected]>wrote: > >> Hi Samisa, >> >> Yes. As Asanka mentioned, we will have considered this aspect for the >> internal QSP. >> We have removed having multiple app owner concept in this 1.0.0 release, >> basically because of the fact that if all the app owners were deleted, then >> the app is going to be unusable. For that we will disable the App Owner >> Deletion permission. >> >> At the end of the QSP, the AF will be able to maintain multiple app >> owners per app and we will be pushing these features to the AF Live as >> well. To keep track of this, have created the JIRA [1] and [2]. >> >> [1]. https://wso2.org/jira/browse/APPFAC-1419 >> [2]. https://wso2.org/jira/browse/APPFAC-1420 >> >> Thanks >> Manisha >> >> On Thu, Jul 18, 2013 at 9:18 AM, Samisa Abeysinghe <[email protected]>wrote: >> >>> In addition to having multiple users in app owner role, there is more >>> into this, in terms of perspectives. >>> >>> Lets get the feature in first, and we can dig more into pespectives >>> later. >>> >>> On the subject of patching, I think we agreed that we will keep updating >>> the live one on a regular basis, meaning, we will do builds (and thus not >>> just the support patches, rather "build" number increment releases of AF) >>> on a weekly basis on AF. So I hope these features will be available >>> "tomorrow" rather than in next October. >>> >>> >>> On Thu, Jul 18, 2013 at 8:38 AM, Shiroshica Kulatilake >>> <[email protected]>wrote: >>> >>>> 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 >>>> >>>> >>> >>> >>> -- >>> >>> 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 >>> >>> >> >> >> -- >> ~Regards >> *Manisha Eleperuma* >> Software Engineer, Solutions TG >> WSO2, Inc.: http://wso2.com >> lean.enterprise.middleware >> >> *blog: http://manisha-eleperuma.blogspot.com/* >> *mobile: +94 71 8279777* >> * >> * >> >> _______________________________________________ >> 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 > > -- *Asanka Dissanayake Software Engineer* *WSO2 Inc. - lean . enterprise . middleware | wso2.com* * email: [email protected] <[email protected]>, blog: cyberwaadiya.blogspot.com, asankastechtalks.wordpress.com mobile: +94 71 8373821*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
