Ryszard, at curriki.org, the rights model is fairly different. There are resources which are private (only you can read), protected (all can read, only you can modify), and public (all can read and modify). There are groups which can be closed or opened… they have spaces which are read only or write only for particular people. All of these things are implemented using the flexible XWikiRights object saved at appropriate places (in the resources' docs, in the webPreferences) and groups (a few for each group). Left on top of that, you have to create the UI that satisfies all of that.
Implementing what you say is not too hard: - XWikiRights in WebPreferences (which can be given using the Admin feature) - avoid XWikiRights in individual pages) … you're left to implement "inheritance of spaces" by hand by copying the things (they do not really exist, as far as I know, and that's fine this way). Note that page-parentship is orthogonal. paul On 16 août 2014, at 16:53, "[email protected]" <[email protected]> wrote: > Hi Ryszard, > > On 16 Aug 2014 at 13:42:51, Ryszard Łach > ([email protected](mailto:[email protected])) wrote: > >> Hi. >> >> I'd like to introduce a concept of space owner - a person who is responsible >> for >> the whole space, it's content, structure etc. >> >> I'd like to designate one of users for each of my spaces and have it's >> name/email/avatar displayed in each one WebHome page. >> >> How would you recommend to implement this? > > I would not use spaces for this but instead use the multi wiki feature of > XWiki and have a local admin for a subwiki. > > Note that this is why we implement “workspaces” as subwikis. > > Thanks > -Vincent > > _______________________________________________ > users mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/users _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
