[EMAIL PROTECTED] wrote, On 11/07/2003 18.43:
I do encourage your group to propose ldapd for the ASF. I don't know if it would best be an Incubator project or Jakarta (Commons). Personally, I'm
I'm working with a few of the guys right now to rethink the design of LDAPd. We're trying now to enable LDAPd with a catelog similar to Oracle's where actual tables are used to manage other tables. Like Oracle we will be using a default backend (a directory context) to store this catelog information that can be manipulated by admins usign the LDAP protocol. Anyway this default backend will make the injection of orthogonal services like authorization, trigger support etcetera easier to implement. For the time being the server is close to RFC2251 but needs significant work. Although labeled alpha it performs like a beta and its just missing a few of the bells and whistles: the access and protocol is solid.
I and others have thought about joining ASF to have more proficient ASF quality developers on board the project. LDAPd is very nicely aligned with several ASF projects: Avalon, Commons, Slide, James and even Tomcat. Do you think joining the ASF will help progress LDAPd? I and the others would be up for it if I have support from you guys on the Avalon team. Do we have your (the Avalon team's) support/sponsorship to join?
You have mine.
Now in terms of Jakarta verse the incubator I don't have a preference other than what will help both parties come along. Looking at the direction of Apache in general and some of the code in LDAPd I see some very interesting things we can do.
As a member if the incubator: any project that enters Apache must pass through the Incubator. The point is about where it will go after incubation, if under another project or as it's own top level project.
First I see db.apache.org and so I'm thinking ldap.apache.org. I guess this is a natural progression after going through perhaps some incubation. The code used in LDAPd's default backend is very conducive for an embedable RDBMS. In fact we can build out a dbcore package in Jakarta's Commons supporting BTrees and composite structures like indices and tables etcetera built on them. This package can then be leveraged directly by databases in ldap.apache.org and db.apache.org and by certain Avalon components that may be conjured up. Both ldap.apache.org and db.apache.org can be one stop OS shoping centers for you database and LDAP needs. What do you and the Avalon folks think about these ideas?
I would really like to see the project land at Apache.
I would propose you that you find a sponsoring PMC that will ask the Incubator for you to enter Apache. Then, after incubation, your project would be a sub-project of Avalon. When it will become big enough, we can decide to make it get out of Avalon ond reside top-level as ldap.apache.org. This is what most other projects have done: Avalon was under Jakarta, James too, Ant the same, Cocoon under xml.apache.org, etc.
What does this sound like? :-)
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
------------------------------------------------------------------------------------------------------------------------------------------ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
