[Mageia-sysadm] [RPM] cauldron core/release tagtool-0.12.3-2.mga1

[Buchan Milne]

----- "Tux99" <tux99-mga at uridium.org> wrote:

> Quote: Michael Scherer wrote on Fri, 04 March 2011 10:20
> 
> > I see no reason to add complexity without having a clear use case.
> > So that's no.
> > 
> > We do have 1 email, that's enough for forwarding, when it will be
> > setup
> > ( as this depend on rather careful change to not disrupt mailling
> list
> > on the main domain ).
> 
> The use-case is to keep separate email addresses for separate purposes
> like
> many people do (myself included).
> 
> I don't think adding a second email field in LDAP and filling it by
> default
> with the same address as the primary email field is a complex task, or
> is
> it?

But we are duplicating information we already have, the uid, for no reason, and only to keep it exactly uid or uid@$domain. So, instead we should make a postfix alias map mapping uid to mail, on a host running an smtpd for maintainers.mageia.org.

It's not about whether adding custom rules into CatDap is a complex task or not, it is about whether doing so makes the software useless to any other organisation.

There are many other use cases I have for CatDap besides identity.mageia.org, and if the desire is to tailor it to identity.mageia.org so much that all other use cases are virtually impossible, I can't justify spending much time on it.

E.g., I would like to see us shipping something like CatDap in the distribution, to make it easier for organisations to implement LDAP directories on Mageia. Yes, there is a lot of work to do for that, but it already provides some value, and I am currently investigating how to most easily tie it into some other internal web interfaces at $work to provide a web interface for user management (that until now has been using commandline-based LDAP tools, ad-hoc CGIs and some other perl scripts in cron).

Alternatively, maybe I need to investigate adding some kind of plugin feature.

Regards,
Buchan