Archives
Archives
| From: | Brian Harring <ferringb@×××××.com> | ||
|---|---|---|---|
| To: | gentoo-dev@l.g.o | ||
| Cc: | robbat2@g.o | ||
| Subject: | Re: [gentoo-dev] RFC: Moving more developer data to LDAP, for scalability/redundancy (away, foward, permissive, SMTP password, plan) [WAS: Suggestion to ask devs to change their bugzilla name] | ||
| Date: | Sat, 12 Jun 2010 20:24:12 | ||
| Message-Id: | 20100612202209.GB7561@hrair | ||
| In Reply to: | Re: [gentoo-dev] RFC: Moving more developer data to LDAP, for scalability/redundancy (away, foward, permissive, SMTP password, plan) [WAS: Suggestion to ask devs to change their bugzilla name] by Alec Warner |
||
| 1 | On Thu, Jun 10, 2010 at 11:42:10PM -0700, Alec Warner wrote: |
| 2 | > perl_ldap is feature-ful but hard to use. The bind options are |
| 3 | > confusing (user / recruiters / infra) do I bind as myself? As anon? |
| 4 | > Do I specify -b user or |
| 5 | > -b antarus? Mutli-valued attributes are confusing for users. |
| 6 | |
| 7 | We should specifically have a tool for this instead of having people |
| 8 | invoking perl_ldap- said tool also gives us easier validation and |
| 9 | sanity checking. I'd started one in '06 but had to retire it at |
| 10 | the time due to ldaps not being supported by the python ldap bindings |
| 11 | I was using- afaik that issue bindings wise is now long since gone. |
| 12 | |
| 13 | Robin, any remenant of that survive? Else a new one could be wrote I |
| 14 | suppose. |
| 15 | ~harring |
| Subject | Author |
|---|---|
| Re: [gentoo-dev] RFC: Moving more developer data to LDAP, for scalability/redundancy (away, foward, permissive, SMTP password, plan) [WAS: Suggestion to ask devs to change their bugzilla name] | Theo Chatzimichos <tampakrap@g.o> |