Hi, folks!
I'm maintaining a private Phase-III installation and managed to set the whole thing up at last (with a customized language file, skin and some added functionality), but I still have some questions:
+ Is there /any/ documentation that covers admin issues besides of the source code? If so: where? I searched Wikipedia, the Meta-Wikipedia and this mailing list but didn't find anything that answers my questions.
In particular, I'd like to know:
+ Is there a way to put the Wiki into a "write-only-if-you-are-logged-in"-mode?
+ Is there a way to put the Wiki into a whitelist mode (i.e. disabling users from getting an account without the agreement of the admin)?
+ What privilege concept does Phase-III have? What is the difference between a plain user, a sysop and a developer in terms of user_rights?
+ I have some ideas of features that would be nice to add. One of these is a user configurable default set of namespaces to search for. In Wikis for small communities that are only just evolving many users will want to search for some documentation which can only be found by searching for the keyword, failing and then selecting the proper namespace (which the user probably doesn't know). I hardcoded this mechanism into my setup but this is far from being a Good Idea (TM). What's the procedure to become a developer with write access to the CVS repository and to convince the other developers to be allowed to include certain features?
Thanks in advance and bye!
Matthias
Matthias Jordan wrote:
- Is there a way to put the Wiki into a
"write-only-if-you-are-logged-in"-mode?
No. At least, not yet. I am working on some things, user management amongst them. You can use the "isloggedin" function (or something like that) prior to editing/saving.
- Is there a way to put the Wiki into a whitelist mode (i.e. disabling
users from getting an account without the agreement of the admin)?
No. The user management I'm working on (for a so-called "sifter" version of wikipedia) would roughly work like that: 1. You become a "logged-in" user, with no editing rights in the article namespace (same for not-logged-in) 2. You apply for an "editors" access 3. Some sysop grants that so you can work in article namespace
- What privilege concept does Phase-III have? What is the difference
between a plain user, a sysop and a developer in terms of user_rights?
Logged-in: Uploading of files, some personal settings and watchlist gimmicks Sysop: Can delete (and undelete) articles, use "SELECT" SQL queries Developer: Unlimited queries to the database, make sysops, other developers (similar to "root")
- I have some ideas of features that would be nice to add. One of these
is a user configurable default set of namespaces to search for. In Wikis for small communities that are only just evolving many users will want to search for some documentation which can only be found by searching for the keyword, failing and then selecting the proper namespace (which the user probably doesn't know). I hardcoded this mechanism into my setup but this is far from being a Good Idea (TM). What's the procedure to become a developer with write access to the CVS repository and to convince the other developers to be allowed to include certain features?
Well, major changes should not be implemented in the CVS without consensus (yes, you just read "consensus"!;-) of the wikipedia-l list.
I (and others) can give you access to the CVS, if you give me your SourceForge user name; it might be nice to have an example of what you'd like to do on the web, that can be tried out by the wikipedia-l crowd (they can react quite annoyed about sudden changes, as I had the pleasure to experience myself :-)
New coders (especially those with time to spare) are always welcome!
Magnus
Matthias Jordan wrote:
- I have some ideas of features that would be nice to add. One of these
is a user configurable default set of namespaces to search for. In Wikis for small communities that are only just evolving many users will want to search for some documentation which can only be found by searching for the keyword, failing and then selecting the proper namespace (which the user probably doesn't know). I hardcoded this mechanism into my setup but this is far from being a Good Idea (TM). What's the procedure to become a developer with write access to the CVS repository and to convince the other developers to be allowed to include certain features?
A simple method that I'd like to search in namespaces is to recognise a search for (say) "User talk:Lir" as a search for "Lir" in the [[User talk:]] namespace. Something like this already works for Go.
-- Toby
wikitech-l@lists.wikimedia.org