On Tue, Jan 17, 2017 at 5:19 PM, Denis Gervalle <[email protected]> wrote: > On Tue, Jan 17, 2017 at 5:08 PM, Thomas Mortagne <[email protected]> > wrote: On Tue, Jan 17, 2017 at 5:02 PM, Vincent Massol <[email protected]> > wrote: >> Hi Thomas, >> >>> On 17 Jan 2017, at 16:54, Thomas Mortagne <[email protected]> wrote: >>> >>> Hi devs, >>> >>> I'm thinking since a long time that maybe we should automatically make >>> superadmin the author of the pages when installing a XAR as long as >>> the current user (and current author) have programming right (i.e. has >>> the same rights than superadmin when the extension is installed). I >>> don't really see anything against it these days and it's easy to do so >>> why not. >>> >>> Basically the goal is to reduce the possibility to break extensions >>> when you play with existing users/groups/rights. Common user case >>> being to get rid of some old adminsys leaving the company. >>> >>> WDYT ? >> >> Why not. However I haven’t thought enough about it but right now the >> downside I see is the loss of accountability/tracability. It’s interesting >> to know what user has installed a given page. Using superadmin would loose >> this info. > > You can know wo installed the extension so it reduce a bit the history > problem. > Couldn’t we keep the author as is, and just apply this to the content author > ? Wouldn’t this be sufficient for our purpose ?
Not because all wiki components (wiki macros, wiki components, translations, etc.) use author. > >> >> BTW and related to this, I’d prefer to have a System user instead of using >> superadmin. The rationale is that super admin is user and you can log with >> it whereas System wouldn’t be a user that you can log with. It would >> represent a change made by the system. This could be another discussion but >> I thought I would mention it here to be complete. > > The main issue is that it's not so easy to introduce new virtual users > without potentially colliding with some existing user somewhere. > That's the issue with possible virtual admin user too. > >> >> Thanks >> -Vincent >> >>> Note: to be complete we could imagine the same kind of thing for admin >>> user but that require the introduction of a virtual admin right user >>> like superadmin is a vitual programming right user. But let's not >>> discuss too many thing at once. >>> >>> -- >>> Thomas Mortagne >> > > > > -- > Thomas Mortagne > -- > Denis Gervalle > SOFTEC sa - CEO -- Thomas Mortagne
