directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny" <>
Subject Re: What about Kerberos becoming a separate project ?
Date Wed, 10 Oct 2007 06:12:23 GMT
I would add something to what Alex just said : we didn't anted to make
Kerberos a separate Apache project, but a separate sub-project, from
Maven point of view. This was just about an internal refactoring.

Kerberos and Apache Directory Project are tighly coupled right now,
and will remain coupled for a while.

Last, not least, I see no way for Harmony to use any of the Apache
Directory project due to the very restrictive condition you have to
fulfill to become a contributor of this project (ie, not having read
any line of SUN java source). We can't guarantee that the ADS
developpers haven't been tainted by SUN code.

I would suggest first that you contact Harmony peeps to get a clear
idea of those constraints, and as stated by Alx, you are welcome to
participate to our project too !

On 10/10/07, Alex Karasulu <> wrote:
> On 10/9/07, Leo Li <> wrote:
> > Hi, all:
> >      I happend to find this thread. Is it a little outdate? :)
> No not at all the topic can be discussed at any time :).  However rehashing
> the
> same topic repeatedly is a real PITA when nothing else has changed.
> >      Harmony project is now implementing a JGSS provider which
> > contains a lot of work with kerberos. We intend to borrow kerberos
> > related code from apache Directory and it will be great if kerberos is
> > a seperate project.
> How about getting involved with the parts that you're interested in first?
> It sounds
> to me like you want the client side functionality and I think we already
> have some of
> that in a separate client project.  Just jump in and get involved with the
> community.
> > And I also acknowledge the concern to maintain a
> > sub project and I think we can give some help if we can and are
> > looking forward to its becoming true.
> That's great! Having a separate subproject should not be the driver though.
> However
> if there is ample community around the code base then there's no reason not
> to consider
> it again.  The point being supportability with a healthy group of people
> around that code
> base.  Please feel free to just dig in and start contributing.
> Alex

Emmanuel L├ęcharny

View raw message