* Juergen Ulbts <j.ulbts at uni-oldenburg.de> [2007-03-07 15:58]:
> The old Wiki seems to work again...
[...]
> As of now the new Wiki doesn't contain anything ...

old wiki? new wiki? consider me confused.

new ox codename hypertion (wtf?!), no tomcat, no ldap, no postgres, no
migration? is *that* the "big surprise" martin talked about months
ago (to silence all discussion about Netline not being open enough,
among other things)?

well, looking at the (new) wiki I was indeed surprised (besides the
changed components/web architecture):

- complete and friendly installation documentation!
  no more community guess-work with obsolete install instructions.
  http://typo3.open-xchange.com/wiki/index.php?title=Open_Xchange_Installation

- public CVS access (from the install instructions)!
  let's only hope it's for real this time.

on the other hand, keeping everyone on the lists completely in the
dark about this /for months/ (let alone gather input or comments)
sounds just too familiar like the "old" Netline.

there's a new wiki the but open-xchange website has no mention of
it. there's a new architecture but by keeping everyone enthusiastic
about your software in the dark you might just start building a new
"community" and throw away all the old wikis, fora, mailing lists &
archives, etc.  it looks like there's noone left anyway. those that
are still around (hi, everyone) are worrying about migration
(guesswork and reverse engineering of schemas, all over again?).

actually, I was trying hard to find some time to finally update our
small production system from SLOX 4.1 to OX 5 SP2 -- I guess that's a
moot point now.


following up on something else juergen mentioned:

* Juergen Ulbts <j.ulbts at uni-oldenburg.de> [2007-02-28 14:54]:
> I'm not sure what is stored in LDAP beside the login
> information. This might require more work...I would move the login
> stuff to the existing Central Authentication Service (CAS), which
> was already on my TODO list for OX 0.8.2-x. I pushed that back
> because of the project task problem mentioned above.

we're also in the beginnings of looking at WebSSO and Shibboleth (and
compatibles, e.g. Liberty later on) but I haven't spent much time
thinging about this. one part would be hacking the authentication out
of the application and getting it from apache's REMOTE_USER (via
mod_cas or mod_cosign or whatever), the webmail is the other
thing. since CAS has a PAM module, this might actually be pretty easy,
pointing saslauthd at PAM. the webmail might still try to pass some
username + password to the imapd. and I don't know if the new OX still
has the sessiond and it's implications here.

regards,
-p.schober

-- 
peter.schober at univie.ac.at - vienna university computer center
Universitaetsstrasse 7, A-1010 Wien, Austria/Europe
Tel. +43-1-4277-14155, Fax. +43-1-4277-9140