On Tue, Jul 23, 2013 at 2:40 PM, Eranda Sooriyabandara <[email protected]>wrote:
> Hi Senaka, > > > On Tue, Jul 23, 2013 at 2:17 PM, Senaka Fernando <[email protected]> wrote: > >> Hi all, >> >> This is WRT, #1725 on Redmine. >> >> +++++++++++++++++++++ >> The idea is to create a special role that gives READ, WRITE, DELETE and >> AUTHORIZE access to a particular asset making it possible for a particular >> user or set of users take ownership of it. This thought came up during a >> WSO2 Store Milestone Planning Meeting, and mimics the functionality of >> Google Docs. >> +++++++++++++++++++++ >> >> Before going ahead with this, we have a few things to get clarified. >> >> 1. How would this role be named? This shouldn't be the name of the Asset >> itself, because there can be multiple assets by the same name. It even >> cant be name + namespace (or similar prefix/postfix), because there can >> be assets that differ by version. So, what's the best way to name it? >> > > Do we need to create a role for each asset? Can't we have a role per user > which has the ownership details, which may be more scalable if there are > lots of artifacts. > There are complications if we do in that way. In asset specific user roles, when we create a new asset we create few user roles unique to that particular asset and then we can assign those to users. But when we create user profile for users at which point we are going to do that? I think both converge to a one point having a one to one mapping. > > >> >> 2. How should we be displaying this role in the management console? >> Should it show up just like any other role, or is there some special >> treatment in the Registry Browser? Since the role and the asset are 1-to-1, >> we shouldn't be displaying such roles against other assets, which makes it >> require some special treatment. >> > > Can't we have a new tab "My Resources" under Main -> Resources. > > >> >> 3. Is it just one such role or more? For instance, G-Docs has three types >> of privileges when it comes to sharing (i.e. View, Edit, Owner). >> > > We can specify this level of privileges if we have role per user model. > So per asset we need to define foo_edit, foo_view, foo_owner etc which has specific permissions for that role. > thanks > Eranda > > >> >> Appreciate some quick responses on these in order to make it possible for >> us to ship this with G-Reg 4.6.0, making it available for WSO2 Store etc. >> >> Thanks, >> Senaka. >> >> -- >> * <http://us13.wso2con.com/> >> * >> * >> * >> *Senaka Fernando* >> Senior Technical Lead; WSO2 Inc.; http://wso2.com* >> Member; Apache Software Foundation; http://apache.org >> >> E-mail: senaka AT wso2.com >> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 >> Linked-In: http://linkedin.com/in/senakafernando >> >> *Lean . Enterprise . Middleware >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > *Eranda Sooriyabandara > *Senior Software Engineer; > Integration Technologies Team; > WSO2 Inc.; http://wso2.com > Lean . Enterprise . Middleware > > E-mail: eranda AT wso2.com > Mobile: +94 716 472 816 > Linked-In: http://www.linkedin.com/in/erandasooriyabandara > Blog: http://emsooriyabandara.blogspot.com/ > > > > * > * > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *Shelan Perera* Senior Software Engineer ** Integration Technology Group *WSO2, Inc. : wso2.com* lean.enterprise.middleware. *Blog* : blog.shelan.org *Linked-i*n : http://www.linkedin.com/pub/shelan-perera/a/194/465 *Twitter* : https://twitter.com/#!/shelan *Mobile* : +94 772 604 402
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
