You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by Kiran Ayyagari <ka...@apache.org> on 2015/01/14 01:10:48 UTC
[Kerberos] re-organizing the module structure
I suggest we reorganize the modules under directory-kerberos.
All the modules under 'contrib' are essential components hence must be
moved to the project root directory.
Add a new folder 'mech' or 'mechanisms' and move various auth mechanisms
like 'pkix', 'token' etc there.
Move 'haox-kdc/kdc-server' to the root level and the create a new folder
at the root level to hold all the backend implementations (and the
ldap-identity-backend
will be moved here).
'contrib' folder can be used to store any contribution from other parties.
And, we should drop the project prefix from the folder names and set
that prefix in <artifactId> in the respective module's pom.xml.
For example, 'haox-asn1' should be renamed to 'asn1' and change the pom.xml
to contain <artifactId>haox-asn1</artifactId>
wdyt?
--
Kiran Ayyagari
http://keydap.com
Re: [Kerberos] re-organizing the module structure
Posted by Kiran Ayyagari <ka...@apache.org>.
Hello Kai,
Now that we have fixed on the name, shall we proceed on the proposed
re-organization?.
Let me know if you want me to complete this.
On Fri, Jan 16, 2015 at 10:38 AM, Zheng, Kai <ka...@intel.com> wrote:
> OK, I will proceed.
>
> >> Especially if we want to reuse it in ApacheDS !
> I guess so, but I thought we might need a separate thread to discuss about
> this. I do have some concerns or questions to make sure about.
>
> Regards,
> Kai
>
> -----Original Message-----
> From: Emmanuel Lécharny [mailto:elecharny@gmail.com]
> Sent: Thursday, January 15, 2015 9:49 PM
> To: dev@directory.apache.org
> Subject: Re: [Kerberos] re-organizing the module structure
>
> Le 15/01/15 04:18, Zheng, Kai a écrit :
> > For the haox-asn1 module, I rethought a bit and agree with Kiran that we
> should promote it to be in the root level, since it’s essential to the
> Kerberos implementation.
>
> That would make a lot of sense. Especially if we want to reuse it in
> ApacheDS !
>
>
--
Kiran Ayyagari
http://keydap.com
RE: [Kerberos] re-organizing the module structure
Posted by "Zheng, Kai" <ka...@intel.com>.
OK, I will proceed.
>> Especially if we want to reuse it in ApacheDS !
I guess so, but I thought we might need a separate thread to discuss about this. I do have some concerns or questions to make sure about.
Regards,
Kai
-----Original Message-----
From: Emmanuel Lécharny [mailto:elecharny@gmail.com]
Sent: Thursday, January 15, 2015 9:49 PM
To: dev@directory.apache.org
Subject: Re: [Kerberos] re-organizing the module structure
Le 15/01/15 04:18, Zheng, Kai a écrit :
> For the haox-asn1 module, I rethought a bit and agree with Kiran that we should promote it to be in the root level, since it’s essential to the Kerberos implementation.
That would make a lot of sense. Especially if we want to reuse it in ApacheDS !
Re: [Kerberos] re-organizing the module structure
Posted by Emmanuel Lécharny <el...@gmail.com>.
Le 15/01/15 04:18, Zheng, Kai a écrit :
> For the haox-asn1 module, I rethought a bit and agree with Kiran that we should promote it to be in the root level, since it’s essential to the Kerberos implementation.
That would make a lot of sense. Especially if we want to reuse it in
ApacheDS !
RE: [Kerberos] re-organizing the module structure
Posted by "Zheng, Kai" <ka...@intel.com>.
For the haox-asn1 module, I rethought a bit and agree with Kiran that we should promote it to be in the root level, since it’s essential to the Kerberos implementation.
Regards,
Kai
From: Zheng, Kai
Sent: Wednesday, January 14, 2015 6:58 PM
To: Apache Directory Developers List
Subject: RE: [Kerberos] re-organizing the module structure
Hi Kiran,
Thanks for your thorough thoughts. Sorry for late response.
>>All the modules under 'contrib' are essential components hence must be moved to the project root directory.
These components like haox-asn1, haox-event, haox-config and etc. are not necessarily related to Kerberos (sorry for missing necessary document to clarify them). If they’re all populated into the root/global then it could be too crowded. Maybe we could give a better name than ‘contrib’?
>>Add a new folder 'mech' or 'mechanisms' and move various auth mechanisms like 'pkix', 'token' etc there.
Again, sorry for missing necessary document to clarify the components haox-pkix and haox-token. They are only helper/utils for implementing the mechanisms PKINIT and token. The actual mechanism implementations are separated into three parts, client side (kerb-client), server side (kerb-server) and common (kerb-common, shared by client and server), each part codes are located in preauth package, below the package there’re separate sub packages to place any mechanism specific logics.
>>Move 'haox-kdc/kdc-server' to the root level and the create a new folder at the root level to hold all the backend implementations (and the ldap-identity-backend will be moved here)...
I agree. Yes we would have such to better serve/depict our product level constructs like Kerby-KDC, relevant identity backends and client tools as well in top level. We would leave all the components in haox-kerb folder as lightweight library level constructs that can be used as embedded in applications or contexts, without heavy dependencies involved. Just explained this by the way.
>>And, we should drop the project prefix from the folder names and set that prefix in <artifactId> in the respective module's pom.xml.
I would agree. Given the naming decided, may be much clearer.
>>For example, 'haox-asn1' should be renamed to 'asn1' and change the pom.xml to contain <artifactId>haox-asn1</artifactId>
I’m not quite clear about this. But maybe ‘kerby-asn1’ would be better mentioned than simple ‘asn1’ because we won’t pollute any global namespace in case it could be used by other projects. Again given the naming decided, let’s see how it would look better.
Thanks.
Regards,
Kai
From: Kiran Ayyagari [mailto:kayyagari@apache.org]
Sent: Wednesday, January 14, 2015 8:11 AM
To: Apache Directory Developers List
Subject: [Kerberos] re-organizing the module structure
I suggest we reorganize the modules under directory-kerberos.
All the modules under 'contrib' are essential components hence must be
moved to the project root directory.
Add a new folder 'mech' or 'mechanisms' and move various auth mechanisms
like 'pkix', 'token' etc there.
Move 'haox-kdc/kdc-server' to the root level and the create a new folder
at the root level to hold all the backend implementations (and the ldap-identity-backend
will be moved here).
'contrib' folder can be used to store any contribution from other parties.
And, we should drop the project prefix from the folder names and set
that prefix in <artifactId> in the respective module's pom.xml.
For example, 'haox-asn1' should be renamed to 'asn1' and change the pom.xml
to contain <artifactId>haox-asn1</artifactId>
wdyt?
--
Kiran Ayyagari
http://keydap.com
RE: [Kerberos] re-organizing the module structure
Posted by "Zheng, Kai" <ka...@intel.com>.
Appreciate if we could accelerate on this. It makes a lot sense to make the project comfortable for all of us. Thanks!
Regards,
Kai
From: Kiran Ayyagari [mailto:kayyagari@apache.org]
Sent: Wednesday, January 14, 2015 9:18 AM
To: Apache Directory Developers List
Subject: Re: [Kerberos] re-organizing the module structure
On Wed, Jan 14, 2015 at 9:05 AM, Zheng, Kai <ka...@intel.com>> wrote:
Hi Kiran,
Thanks for taking care of this!
Looks like we could re-organize the project much better if we get the naming issue resolved first. For example, if Kerby is used, maybe ‘kerby-asn1’ would be a choice, which allows it to be used in other contexts/projects without worrying about polluting their global namespace.
yes, indeed, we all should come to a consensus on this naming issue
so I request all to cast their vote/opinion here https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-66
Just a quick reply. Will provide my thoughts for each item thoroughly late today.
Regards,
Kai
From: Kiran Ayyagari [mailto:kayyagari@apache.org<ma...@apache.org>]
Sent: Wednesday, January 14, 2015 8:11 AM
To: Apache Directory Developers List
Subject: [Kerberos] re-organizing the module structure
I suggest we reorganize the modules under directory-kerberos.
All the modules under 'contrib' are essential components hence must be
moved to the project root directory.
Add a new folder 'mech' or 'mechanisms' and move various auth mechanisms
like 'pkix', 'token' etc there.
Move 'haox-kdc/kdc-server' to the root level and the create a new folder
at the root level to hold all the backend implementations (and the ldap-identity-backend
will be moved here).
'contrib' folder can be used to store any contribution from other parties.
And, we should drop the project prefix from the folder names and set
that prefix in <artifactId> in the respective module's pom.xml.
For example, 'haox-asn1' should be renamed to 'asn1' and change the pom.xml
to contain <artifactId>haox-asn1</artifactId>
wdyt?
--
Kiran Ayyagari
http://keydap.com
--
Kiran Ayyagari
http://keydap.com
Re: [Kerberos] re-organizing the module structure
Posted by Kiran Ayyagari <ka...@apache.org>.
On Wed, Jan 14, 2015 at 9:05 AM, Zheng, Kai <ka...@intel.com> wrote:
> Hi Kiran,
>
>
>
> Thanks for taking care of this!
>
>
>
> Looks like we could re-organize the project much better if we get the
> naming issue resolved first. For example, if Kerby is used, maybe
> ‘kerby-asn1’ would be a choice, which allows it to be used in other
> contexts/projects without worrying about polluting their global namespace.
>
> yes, indeed, we all should come to a consensus on this naming issue
so I request all to cast their vote/opinion here
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-66
>
>
> Just a quick reply. Will provide my thoughts for each item thoroughly late
> today.
>
>
>
> Regards,
>
> Kai
>
>
>
> *From:* Kiran Ayyagari [mailto:kayyagari@apache.org]
> *Sent:* Wednesday, January 14, 2015 8:11 AM
> *To:* Apache Directory Developers List
> *Subject:* [Kerberos] re-organizing the module structure
>
>
>
> I suggest we reorganize the modules under directory-kerberos.
>
>
>
> All the modules under 'contrib' are essential components hence must be
>
> moved to the project root directory.
>
>
> Add a new folder 'mech' or 'mechanisms' and move various auth mechanisms
> like 'pkix', 'token' etc there.
>
> Move 'haox-kdc/kdc-server' to the root level and the create a new folder
>
> at the root level to hold all the backend implementations (and the
> ldap-identity-backend
>
> will be moved here).
>
>
> 'contrib' folder can be used to store any contribution from other parties.
>
>
>
> And, we should drop the project prefix from the folder names and set
>
> that prefix in <artifactId> in the respective module's pom.xml.
>
>
> For example, 'haox-asn1' should be renamed to 'asn1' and change the pom.xml
>
> to contain <artifactId>haox-asn1</artifactId>
>
> wdyt?
>
> --
>
> Kiran Ayyagari
> http://keydap.com
>
--
Kiran Ayyagari
http://keydap.com
RE: [Kerberos] re-organizing the module structure
Posted by "Zheng, Kai" <ka...@intel.com>.
Hi Kiran,
Thanks for taking care of this!
Looks like we could re-organize the project much better if we get the naming issue resolved first. For example, if Kerby is used, maybe ‘kerby-asn1’ would be a choice, which allows it to be used in other contexts/projects without worrying about polluting their global namespace.
Just a quick reply. Will provide my thoughts for each item thoroughly late today.
Regards,
Kai
From: Kiran Ayyagari [mailto:kayyagari@apache.org]
Sent: Wednesday, January 14, 2015 8:11 AM
To: Apache Directory Developers List
Subject: [Kerberos] re-organizing the module structure
I suggest we reorganize the modules under directory-kerberos.
All the modules under 'contrib' are essential components hence must be
moved to the project root directory.
Add a new folder 'mech' or 'mechanisms' and move various auth mechanisms
like 'pkix', 'token' etc there.
Move 'haox-kdc/kdc-server' to the root level and the create a new folder
at the root level to hold all the backend implementations (and the ldap-identity-backend
will be moved here).
'contrib' folder can be used to store any contribution from other parties.
And, we should drop the project prefix from the folder names and set
that prefix in <artifactId> in the respective module's pom.xml.
For example, 'haox-asn1' should be renamed to 'asn1' and change the pom.xml
to contain <artifactId>haox-asn1</artifactId>
wdyt?
--
Kiran Ayyagari
http://keydap.com
RE: [Kerberos] re-organizing the module structure
Posted by "Zheng, Kai" <ka...@intel.com>.
Hi Kiran,
Thanks for your thorough thoughts. Sorry for late response.
>>All the modules under 'contrib' are essential components hence must be moved to the project root directory.
These components like haox-asn1, haox-event, haox-config and etc. are not necessarily related to Kerberos (sorry for missing necessary document to clarify them). If they’re all populated into the root/global then it could be too crowded. Maybe we could give a better name than ‘contrib’?
>>Add a new folder 'mech' or 'mechanisms' and move various auth mechanisms like 'pkix', 'token' etc there.
Again, sorry for missing necessary document to clarify the components haox-pkix and haox-token. They are only helper/utils for implementing the mechanisms PKINIT and token. The actual mechanism implementations are separated into three parts, client side (kerb-client), server side (kerb-server) and common (kerb-common, shared by client and server), each part codes are located in preauth package, below the package there’re separate sub packages to place any mechanism specific logics.
>>Move 'haox-kdc/kdc-server' to the root level and the create a new folder at the root level to hold all the backend implementations (and the ldap-identity-backend will be moved here)...
I agree. Yes we would have such to better serve/depict our product level constructs like Kerby-KDC, relevant identity backends and client tools as well in top level. We would leave all the components in haox-kerb folder as lightweight library level constructs that can be used as embedded in applications or contexts, without heavy dependencies involved. Just explained this by the way.
>>And, we should drop the project prefix from the folder names and set that prefix in <artifactId> in the respective module's pom.xml.
I would agree. Given the naming decided, may be much clearer.
>>For example, 'haox-asn1' should be renamed to 'asn1' and change the pom.xml to contain <artifactId>haox-asn1</artifactId>
I’m not quite clear about this. But maybe ‘kerby-asn1’ would be better mentioned than simple ‘asn1’ because we won’t pollute any global namespace in case it could be used by other projects. Again given the naming decided, let’s see how it would look better.
Thanks.
Regards,
Kai
From: Kiran Ayyagari [mailto:kayyagari@apache.org]
Sent: Wednesday, January 14, 2015 8:11 AM
To: Apache Directory Developers List
Subject: [Kerberos] re-organizing the module structure
I suggest we reorganize the modules under directory-kerberos.
All the modules under 'contrib' are essential components hence must be
moved to the project root directory.
Add a new folder 'mech' or 'mechanisms' and move various auth mechanisms
like 'pkix', 'token' etc there.
Move 'haox-kdc/kdc-server' to the root level and the create a new folder
at the root level to hold all the backend implementations (and the ldap-identity-backend
will be moved here).
'contrib' folder can be used to store any contribution from other parties.
And, we should drop the project prefix from the folder names and set
that prefix in <artifactId> in the respective module's pom.xml.
For example, 'haox-asn1' should be renamed to 'asn1' and change the pom.xml
to contain <artifactId>haox-asn1</artifactId>
wdyt?
--
Kiran Ayyagari
http://keydap.com