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 Sat, 22 Sep 2007 17:29:47 GMT
Just to clarify my proposal : I just want Kerberos to be clearly
separated from apacheds, as is daemon, shaed and installers.

The fact that there is not enough community does not have anything to
do with it, being part of apacheds or not won't help at all to gather
some new committers around it. However, it can still be a plugin, but
I would like it to be less tighly coupled with apacheds.

I must admit I don't understand your -1.

On 9/22/07, Alex Karasulu <> wrote:
> -1
> Kerberos does not have enough community around it to warrant the exposure of
> having it a
> separate project.  It was at some point separate but I purposely merged it
> back in as
> a plugin of ApacheDS.
>  On 9/22/07, Emmanuel Lecharny <> wrote:
> > I was wondering if we couldn't move all the kerberos code into a
> > specific subproject, at teh same level as apacheds, daemon, shared ?
> >
> > Kerberos is really not deeply tight to the apacheds project, so it
> > could make sense to have it moved in its own place.
> It will be much more integrated once we remove the JNDI layer.  It's fine
> where it is as a
> set of separate modules and as an ApacheDS plugin.
> Alex

Emmanuel L├ęcharny

View raw message