Hi Ryan,
What I actually meant is that these extensions are available in the main distribution itself instead of people are searching for it, downloading it, copying files, changing files, etc. (I'm using your LDAP extension, though I'm yet to experiment with the group synchronization :( )
By UI-based, access control mechanism, I meant not a UI to LDAP; but a UI for access control within wiki.
I know the basic philosophy of wiki is not to restrict, but be as open as possible. But still, that won't work always. In Wikipedia, even if there's error in some article, that won't affect anyone critically. But in a corporate wiki, the information may critical. E.g. our wiki deals with configuration information of our s/w for banking and telecom sector. if wrong information is there and if anyone uses that information to configure the s/w, that may lead to error or unwanted results.
Regards,
Jack ---------------------------------------------------------------- "If you can find something everyone agrees on, it's wrong"
-----Original Message----- From: mediawiki-l-bounces@lists.wikimedia.org [mailto:mediawiki-l-bounces@lists.wikimedia.org] On Behalf Of Lane, Ryan Sent: Thursday, July 05, 2007 10:52 PM To: MediaWiki announcements and site admin list Subject: Re: [Mediawiki-l] Looking for MW Business Users
I hope (and I can only hope) somebody will come up with features that make MW a natural choice in business wikis as well. As Dave pointed out, an inbuilt WYSWYG editor is everyone's dream. Other than that, I think a wiki administrator would like to have built in features in MW as:
Different authentication mechanisms like LDAP, NTLM UI for creating users, groups and assigning users to groups UI for creating categories and assigning categories to articles UI-based access control mechanism based on article categories/user groups and usernames Review mechanism if needed Rating of articles
If you mean, you'd like to see support those auth methods, support is already available for them. The LDAP one will sync groups from LDAP, and it is possible to have the wiki create LDAP accounts (if you *really* want that). There are also quite a few access control extensions around, that work on categories, and even per page; the regular saying goes that the access control plugins can't be trusted regarding read rights...
If you only wanted the UI, then PHPldapAdmin, or some other LDAP admin gui would solve at least part of your problem.
V/r,
Ryan Lane
_______________________________________________ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org http://lists.wikimedia.org/mailman/listinfo/mediawiki-l
This electronic mail (including any attachment thereto) may be confidential and privileged and is intended only for the individual or entity named above. Any unauthorized use, printing, copying, disclosure or dissemination of this communication may be subject to legal restriction or sanction. Accordingly, if you are not the intended recipient, please notify the sender by replying to this email immediately and delete this email (and any attachment thereto) from your computer system...Thank You
I know the basic philosophy of wiki is not to restrict, but be as open as possible. But still, that won't work always. In Wikipedia, even if there's error in some article, that won't affect anyone critically. But in a corporate wiki, the information may critical. E.g. our wiki deals with configuration information of our s/w for banking and telecom sector. if wrong information is there and if anyone uses that information to configure the s/w, that may lead to error or unwanted results.
I find it is usually OK to mark things like that as draft, and include a warning saying that the documentation may not be complete/accurate yet. The upcoming stable version stuff may work perfectly for that. Mark checked articles as complete, and have everything else considered draft (possibly with a warning).
V/r,
Ryan Lane
mediawiki-l@lists.wikimedia.org