Yes, I understand... unfortunately, I understand :-) Last question: if all this is true (ACL side), what do you think of: http://www.blue-spice.org/ It seems they use an ACL extension as a workaround of the MW limitations, no ? Thanks again for all your comments !
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Tom Sent: Saturday, August 10, 2013 6:48 PM To: MediaWiki announcements and site admin list Cc: MediaWiki announcements and site admin list Subject: Re: [MediaWiki-l] Mediawiki as an Enterprise wiki http://en.wikipedia.org/wiki/Access_control_list http://www.mediawiki.org/wiki/Security_issues_with_authorization_extensions By design MW is not a CMS. You need a content management system with a good ACL built in. You are asking for too much with your example but a CMS could handle it just fine. e.g. Type 'Secret Docs' - Tech 1 could be a Company A, B, C maintainer. Tech 2 could be a Company C, D, E, F maintainer. Tech 3 could be a Company A and E maintainer. All 3 techs could also be in a Type 'Public Docs' group. You can take it even further with Tech 3 being a read only user. So the tech could read Company A and E docs on Tech 1 can edit A and Tech 2 can edit E. MW does have permissions but they are group based. ACL in a CMS can compare group, user, content(page), category, state(read, edit, etc.) then make sure a user has met every Access Control before proceeding. Tom On Aug 10, 2013, at 3:21 PM, Pierre Labrecque <[email protected]> wrote: > E _______________________________________________ MediaWiki-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/mediawiki-l _______________________________________________ MediaWiki-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
