Hi Ryan, I would like to be part of the maintainers team(OpenLDAP). I haven't contributed to debian before, I have worked in Linux based servers for more than 11 years. If the prior experience in contribution is not mandatory, please let me know how to proceed.
thanks, Karthik On Sat, 5 Dec 2020 12:36:00 -0800 Ryan Tandy <r...@nardis.ca> wrote: > I'm still looking for help with the OpenLDAP packages. I'm not an > OpenLDAP user any more, and I would like to eventually hand off the > package to a new maintainer. > > The current 2.4 package is in OK shape. It's up-to-date in unstable and > backports, and I'm able to handle the low volume of security updates and > bug reports. I'm also responding to Debian-specific issues on the > upstream support channels (lists/bugs/IRC). The status quo will probably > be fine for bullseye; however, I'm not making much progress on > developing or improving the package. > > Here are some of the major projects that I would appreciate help with: > > * Updating to OpenLDAP 2.5. > > The first 2.5 alpha has been released already. I hope the final > release will happen in time that we can transition to it for bookworm. > This will include a SONAME transition, which should be mostly painless > as the library API has not changed much. > > The bulk of the work will be to support slapd upgrades. The biggest > change is that the Berkeley DB backends (BDB and HDB) have been > removed. These were the default for Debian installations for a long > time and I know not all users have migrated to LMDB yet. We should > provide an automated migration from BDB/HDB to LMDB, as was done for > LDBM previously. There are also some old bugs in the maintainer > scripts for upgrading databases, which still need to be addressed. > > Upstream still supports both slapd.conf and cn=config configuration > (though slapd.conf is considered deprecated), so any upgrade path has > to support both. > > * Overhauling the debian/copyright file. > > The copyright file is old and not in DEP5 format yet. We basically > need to do a full copyright review of the upstream source in order to > write a complete and correct DEP5 copyright file, and then commit to > maintaining it going forward. > > I don't know at all what the license of debian/* is supposed to be. We > might have to do some legwork of contacting previous maintainers and > trying to obtain copyright statements from them. > > * Replacing the slapd init script with a systemd service. > > This is a smaller project, but still not as trivial as it sounds. The > init script supports a number of configuration variables, and it also > picks up some information dynamically from the slapd configuration. > This probably requires extracting some of the init script code to a > wrapper script for executing slapd with appropriate arguments. > > Supporting both slapd.conf and cn=config adds complexity here as well. > > * Working with upstream on GnuTLS support. > > Upstream still supports GnuTLS, but reluctantly. They expect the > Debian maintainer to be actively involved with triaging and fixing > GnuTLS issues upstream. > > The autoca overlay is new in 2.5 and only supports OpenSSL right now.
