Hi Shiro,
On Tue, Aug 13, 2013 at 6:42 AM, Shiroshica Kulatilake <[email protected]>wrote: > Hi, > > 1. Should the word team be used for application team when an app owner > creates a team and hence use the word organisation in this page ? > 2. CXO and Tenant Admin should be two separate roles - from a dashboard > point of view users of these two roles would see different dashboards. > We have never mixed up CXO and Tenant Admin, and they MUST be two different roles. For dashboards we can add any of number of roles as desired. > 3. Do we need another AppOwner role or can it be taken that admins are > those who are privileged to create apps ? > These are two separate roles. > 3. Should there be a default tenant role for all who belong to the > organisation ? > The platform already provides it. It is called "Everyone" > 4. When an app owner creates an application and adds team members would it > be restricted to the organisation members added ? > Yes for the first cut. > 5. AppUser seems to be a more general role than AppDev - and shouldn't we > have at least the Dev/QA/DevOps categories that were used for other > sections e.g. governance ? > If we are using a more elaborative role scheme, it would make more sense to use Dev/QA/AppOwner as oppose to AppUser/Dev/QA/AppOwner. I think we can leave out the DevOps in the OOTB configuration. Why? 1 - Our AF automatically does ALM and deployment. It is a automated DevOps platform and in the cloud deployment it makes sense to take out DevOps role, because AF provides it for you. 2 - We have taken out Staging for the cloud deployment. So "DevOps" role played a major role in Staging. Since we have taken out staging it make sense to take the role out. thanks, dimuthu All of these are configurations we can alter them anytime once the code is in place. But it is good to decide on the OOTB configuration. thanks, dimuthu > > The above are some questions that came to mind. > > Thank you, > Shiro > > > On Tue, Aug 13, 2013 at 5:51 AM, Dimuthu Leelarathne <[email protected]>wrote: > >> Hi all, >> >> This is what we (Sameera and AF team) have discusses so far. >> >> 1) A person creates an organization. He becomes the admin of that >> organization. The default set of roles are AppOwners and CXO. These are the >> tenant roles. >> >> 2) He add people to his organization and specify who are AppOwners. >> Please see screenshot. This is a new page that comes under >> organization/settings. How do we add users to organization? By sending >> email invites. Later on we'll add bulk invites as well. >> >> When AppOwners login they see the "Create App" button but others don't >> see it. >> >> >> 3) AppOwners can create applications. When an application is created >> there are a set of default roles created for the Application. Lets call >> them - "Application Roles". We need to define what are the default set of >> "Application Roles". How about "AppDevs" OOTB ? The person who creates the >> app is also in it. >> >> Underlying implementation - Tenant roles with ApplicationKey appended. >> >> WDYT? >> >> thanks, >> dimuthu >> >> -- >> Dimuthu Leelarathne >> Architect & Product Lead of App Factory >> >> WSO2, Inc. (http://wso2.com) >> email: [email protected] >> Mobile : 0773661935 >> >> Lean . Enterprise . Middleware >> >> _______________________________________________ >> 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 > > -- Dimuthu Leelarathne Architect & Product Lead of App Factory WSO2, Inc. (http://wso2.com) email: [email protected] Mobile : 0773661935 Lean . Enterprise . Middleware
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
