Just my thoughts:
If we do this, we ought to spend quite a bit of time evaluating all of
the different options. And there are a lot. Let's not discuss
specifics of each option yet.

Before I mention this, I know little of the specifics, and
implications of such an approach and possibly dont really know what I
am talking about, but I know that LDAP can be utilised as a backend
for passwords and usernames and such. Maybe theres someone here who
can contribute, or we could put a bit of research into it.
After a short thirty second google, I found such backends for the
forums and the wiki. Flyspray is a smallish project still, so there
isnt many custom things for that. Integrating it into anything is not
going to be so simple.
The AUR is undergoing a rewrite at the moment as I understand, so
bumping ldap support into that wouldnt be too difficult.

If this goes ahead (we ought to have that decided on that first...
that'd help), that's one idea,

iphitus
--
iphitus - ArchCK Maintainer, Arch Trusted User, Arch Developer.
Home:iphitus.loudas.com

_______________________________________________
arch mailing list
[email protected]
http://www.archlinux.org/mailman/listinfo/arch

Reply via email to