Avalon Members, LDAPd Members, and Nickola, Okay it looks good. 4 out of the 5 of the LDAPd guys already replied with a +1 so we're well above the 3/4ths majority. We're in if the Avalon PMC votes positively on sponsoring LDAPd for the incubator. I guess if and when the PMC votes positively on LDAPd we need to have the LDAPd folks fill out this form
http://incubator.apache.org/forms/ASF_Contributor_License_2_form.pdf and fax or mail it some where but there is no mention of how to submit this to Apache on the incubator site. We can deal with this if and when we have to. Thanks to all, Alex Karasulu > > From: Nicola Ken Barozzi <[EMAIL PROTECTED]> > Date: 2003/07/14 Mon AM 11:51:58 EDT > To: [EMAIL PROTECTED] > Subject: Re: [OT] LDAPd and Avalon > > > [EMAIL PROTECTED] wrote, On 14/07/2003 16.47: > > > Nicola, > > > > Forgive me but I thought I'd change the subject of the email > > Hey, I should thank you :-) > > > and perhaps if you would like we could move it to a more appropriate mailing list. > > > > "How does it sound?" You ask, well it all sounds good to me. Avalon is a great > > fit and pathway immediately out of the incubator since the server is an Avalon > > based server. We should fell right at home with it there and think several Avalon > > folks could help join the effort. So I guess the sponsoring PMC we would need to > > contact would be Avalon's PMC. Seeing as how you're the Avalon PMC Chair would > > you begin the process of sponsoring LDAPd? I don't know what this entails on your > > side but I guess its a PMC vote to sponsor right? > > Yes. > > > I just have a few questions regarding the process and structure of things to come. > > First you will be asking the incubator to add us. What will determine the > > graduation into Avalon as an Avalon subproject? I'm guessing the formation of a > > community around the OS project in line with the Apache Way is the goal. > > Not exactly. Here is how it works: > > 1 - A projects looks for a sponsioring Apache member. > Better even, a sponsoring Apache PMC. > 2 - the PMC asks the Incubator for incubation > 3 - Incubation - the sponsoring PMC helps and Incubator watches > 4 - When the incubation is ok, the project is voted out > of the Incubator and lands in the requesting Project > > > Now LDAPd has several CVS projects segmenting the code into logical areas. For > > example there is an ldapd-common for common client and server code. There is a > > ldapd-client which contains clients and client specific library code. Then there > > is ldapd-server which contains the blocks of the ldap server in a package > > structure reflecting the blocks. Also there are CVS modules for each type of > > backend like modjdbm, modjdbc etcetera. My question is how would all these > > different repositories need to be managed would we merge them into one or can they > > stay separate. I would rather keep them separate since some people will have > > access to clients and others will be server side and library developers. This is > > probably why I eventually would like to see this become a top level project like > > James. Please don't misconstrue my LDAP vision for sensibility - we would > > certainly need incubation time and a good amount of time maturing under Avalon > > before reaching such a production grade > sta > > te. I'm just looking forward to a future where I can go to one place to do my > > Java LDAP shopping so to speak just like the way I can do it for Java Servlets, > > and Java Mail today at Apache. > > I understand. What I'd see is simply an avalon-ldap repository. > Inside, you can create the directories you talk about. > > > I know all the guys at LDAPd would be fine with the move I would still need to run > > it by them and take a count. It's the right thing to do. What else would I need > > to do to begin the process if the PMC approves the sponsorship? > > If the project and the Avalon PMC both vote ok for it, the Incubation > will start. The first thing we'll need are signed papers from *all* code > contributors that give Apache the rights. Then we'll see together. > > -- > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
