[CentOS-docs] proposed changes option

Sat Apr 4 13:58:50 UTC 2009
Alain Reguera Delgado <al at ciget.cienfuegos.cu>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ralph Angenendt wrote:
> Marcus Moeller wrote:
>> Dear Ralph,
>>
>>>> On top of my personal list is LDAP integration, as we want to push
>>>> website v2 a bit.
>>> LDAP integration is just a config change, so no big problem. The
>>> problem is that website accounts and wiki accounts don't have
>>> anything in common.
>> At the moment or in the future?
> 
> At the moment. And I don't see any easy way to resolve that if there are duplicate account names.
> 
>> As the aim should be to create one single backend for all parts of the
>> website (News, Forum, Wiki, Planet...).
> 
> Yes. Which one is the leading account? Trac? Wiki? Website? 

Well, I would chose the source where there are more accounts and user
information. Based on that we could break those records into appropriate
LDAP attributes.

For example, and because is what I've seen by now, if the accounts
source chosen would be Xoops.users we could use the the name field to
build a wiki name that could be stored into another LDAP uid attribute.
Then point somehow MoinMoin to match that.

Of course, users that aren't in Xoops.users won't be in LDAP, so in
order to make the migration we need to request users to register in a
common place or create some kind of script that help us migrate things
from different sources into a common source.

I would like to request the creation of a wiki page to organize these
things, so we can define solutions and a direction, based on real
conditions/logistic/resources and any thing involved.

b.t.w. Did any one have test:
http://php-bb.dev.centos.org/private/newbb_to_phpbb/ ? I would like to
make that script public if possible (getting it out of private directory
) for anyone to test.

- --
Alain Reguera Delgado <al at ciget.cienfuegos.cu>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with CentOS - http://enigmail.mozdev.org

iD8DBQFJ12eayXxCQEoXDZARAo+zAJ4l1JQWcyE6ytreP8qWR5pG1t68jACfRjuU
cuF0AVUoF8uEDETbqSPqkXo=
=KTRz
-----END PGP SIGNATURE-----