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:[email protected]] 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
