>>>> Christian Boltz <opensuse@cboltz.de> 1/9/2013 9:58 AM >>>
>Hello,
>
>I didn't hear anything about the wiki upgrade since months.
>Can you please give a status update? ;-)
>
>To make things more interesting,
>- the mw_upgrade_1.19 branch on github seems to contain 1.17 again :-/
>  The history looks like 1.19 was never there, but I don't know git good
>  enough to really know or find out what happened.
>- in the meantime, MediaWiki 1.20.2 was released (requires PHP >= 5.3.2,
>  but en.o.o has only 5.2.14 according to special:version)
>- OTOH, the MediaWiki 1.19 branch will get "longterm support" [1]
>
>So, the questions are:
>- what happened to the mw_upgrade_1.19 branch on github?
>- which version will we upgrade to - 1.19 or 1.20?
>- is it possible to get a newer PHP on the server? (if not, this answers
>  the previous question ;-)
>- can you give a timeframe for the upgrade?

Scott is working on a reply, so I'll let him answer those questions.

>As a wild idea, I was also thinking about switching to OpenID login. The
>advantage would be that we can probably use an existing extension from
>upstream MediaWiki instead of having to maintain the AccessManager
>extension ourself.
>As I said, this is a wild idea - I don't know if it really makes sense
>or if it would work at all ;-)

Novell and SUSE both have OpenID providers that are integrated with the Access Manager

login, so at first glance, it seems feasible.  It's hard to tell without know what's currently out

there.  It does have the advantage of allowing people to log in with other providers that we

would trust, so that's a big plus. 

 

The big disadvantage is losing the seamless login across the wikis.  You would still be SSO, but

you would have to click login in each wiki you visit to make it go through the authentication

process.  I don't think maintenance will be much of an issue either way, since we only really need

to maintain it when MW makes a change to the authentication hooks.

 

-Matt