Package: gforge-ldap-openldap Version: 3.1-26 Severity: wishlist
Hi, First-off: Thank you, major-ly, for the debconf & packaging work. GForge running on a home box is .. a big deal, heh, & a nice prototypical setup. Here's what I'd wanted to mention, though: I just found this out, not sure what to do about it, but though that I might as well pass the word along, about it: It is possible, "of course", to configure kontact/kaddressbook to use a gforge LDAP database as a contact-list data source. I am not sure how this might be worked for a site, automatcally. (I had to grep my ~/.kde/ to see how kaddressbook's address-book "stuff" is even being configured, in the first place.) http://pim.kde.org/ might have some info about this, though I"m not wholly sure, as to whether it would be any in-depth info. So, here's a prototypical, "adapted for public distribution" copy of of what I'd found in my ~/.kde/share/config/kresources/contact/stdrc : [Resource_<odd base64-like text>] LdapAnonymous=false LdapAttributes=city,l,commonName,cn,description,description,facsimileTelephoneNumber,facsimileTelephoneNumber,familyName,sn,formattedName,gecos,givenName,givenName,jpegPhoto,jpegPhoto,mail,mail,mailAlias,debGforgeForwardEmail,mobile,mobile,objectClass,inetOrgPerson,organization,o,pager,pager,phoneNumber,homePhone,postalcode,postalCode,state,st,street,street,telephoneNumber,telephoneNumber,title,title,uid,uid LdapAutoCache=true LdapBindDN=uid=<user's own gforge-site UID>,ou=People,dc=<myhost>,dc=<mydomain>,dc=<mytld> LdapCachePolicy=0 LdapDn=dc=<myhost>,dc=<mydomain>,dc=<mytld> LdapFilter=(&(gecos=*)(!(cn=anoncvs))(!(uid=Dummy))(!(uid=None)) ) LdapHost=localhost LdapMech=CRAM-MD5 LdapPassword=<encyphered user password> LdapPort=389 LdapRDNPrefix=0 LdapRealm= LdapSASL=false LdapSSL=false LdapSizeLimit=0 LdapSubTree=true LdapTLS=false LdapTimeLimit=0 LdapUser=<user's own gforge-site UID> LdapVer=3 ResourceIdentifier=<odd base64-like text> ResourceIsActive=true ResourceIsReadOnly=true ResourceName=ldapkio address book - CWXN:GForge ResourceType=ldapkio Of course, everything in the <blocks> is edited from the original. The <odd base64-like text> was the same, in the INI-header and in the LdapUser field I'm sure that the rest of the <edited-text> will make sense, heh; maybe it's worth mentioning, though: Of course, some of that data -- namely, the LDAP server's base DN, and maybe the server's host-name -- I'd guess that it could be determined, automatically, upon the 'debconf' data for OpenLDAP So, the user's GForge-site UID and GForge-site password should be the only fields/values that the user should need to input, during an automatic installation of a resource-configuration block, like that one excerpted, above Some considerations, furthemore - pertaining more about GForge feature-requests, albeit, but worth mentioning here, probably: *) With the resource-configuration excerpted above, the user's debGforgeForwardEmail is the email address being shown; I do not know how it could be worked, either, to get the email address to be displayed, in each user's kontact/kaddresbook, as: {GForge-site [EMAIL PROTECTED] Host} *) There are more contact-management-supporting "obectClass attributes" -- more than what are presently being used for the gforge user database. Granted, GForge isn't a contact-management server, heh, but there are more attributes, though, which would be supported in GFOrge, for editing, and which might be of some use, for/in-regards-to: Contact management. *) Integrating "contact management" with an LDAP directory should be rather nifty, I'd think, for any given GForge site *) LDAP directory access-control lists may be a matter of concern, for the proverbial LDAP-directory admin. to consider Those "thoughts" may be more fit to mention in a GForge.org forum, I suppose. I thought that I might pass it by you - the deb:gforge-ldap-openldap maintainer - firstly, though. I'm not even sure about which gforge.org forum this could be worth mentioning in, exactly, or if it should be filed as a 'tracker' item, there, or what-else. If this seems worth mentiong at gforge.org, then I can "take the initiative" to mention it myself, there for what it's worth (user 'gimbal' at gforge.org, heh) ...and of course, if you'd have any suggestion, as to: Where at gforge.org this could be mentioned -- then I'd appreciate the suggestion! I hope that this may-be/may-have-been some helpful "FYI". --- Tangential question, with some initial explanation: Do you ever wonder: What might Debian developers ever think, possibly -- in any long while, and/or "hypothetically", today -- what might folks think, about GForge being integrated, ever, with the Debian BTS & Debian {more}? (Something about "project management system" and "package distribition system" ... seem like they shold be fit together, ultimately. Granted, also: Debian packages tend to be made not-upstream, but still, there may be something "groovin" that could be worked-in, for integrating GForge with Debian, ever -- perhaps, quite cooperatively so) Thank you. --- Sean Champ -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i586) Kernel: Linux 2.6.10 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages gforge-ldap-openldap depends on: ii debconf 1.4.42 Debian configuration management sy ii debianutils 2.11.2 Miscellaneous utilities specific t ii gforge-common 3.1-26 Collaborative development tool - s ii gforge-db-postgresql [gforge- 3.1-26 Collaborative development tool - d ii ldap-utils 2.1.30-3 OpenLDAP utilities ii libdbd-pg-perl 1.32-2 a PostgreSQL interface for Perl 5 ii libdbi-perl 1.46-5 Perl5 database interface by Tim Bu ii libnss-ldap 220-1 NSS module for using LDAP as a nam ii perl 5.8.4-6 Larry Wall's Practical Extraction ii slapd 2.1.30-3 OpenLDAP server (slapd) -- debconf information excluded -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
