-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
(Disclaimer: I'm not a native speaker, and that means I ramble a bit
from lack of skill in making short sentences. Please bear with me.)
Hi module authors,
I'm DOMQ on CPAN, and I'm about to release a new application, NutsPKI.
Problem is, I don't know where to put it on the CPAN, if at all.
The application is an X509 PKI, which delivers X509 certificates. It's
not just the CA (that would be Crypt::OpenSSL::CA, which is already on
CPAN), and it's not just a Web application; when finished, it will
have a Web interface, a validation workflow, it will send emails, have
crontabs, store stuff into an LDAP directory, and supervise and/or own
security-critical parts of the infrastructure (eg its own Apache web
server, an OpenLDAP server and an OCSP responder).
Of course I'll strive to keep it as modular as possible (eg ship the
OCSP part as Crypt::OCSP::Responder or something). But at the end of
the day, there remains a need for a little pyramid-shaped piece of
Perl to go on top of that heap of CPAN slabs and act as the
application proper. This whatever-NutsPKI-0.01.tar.gz will not be
re-useable code in OO parlance (meaning that you'll have to edit it in
order to change its purpose).
My options wrt the CPAN namespace are:
1. not put it on the CPAN at all (eg Slashcode);
2. use the root namespace ("NutsPKI"), which some high-profile CPAN
contributor advised me to do over IRC today (a lot of the
newfangled Catalyst applications do that these days, eg Angerwhale);
3. use a themed toplevel namespace, ie Crypt::NutsPKI
(Mail::SpamAssassin does that);
4. create a whole new Application:: namespace to host applications,
in the sense of code that is not re-useable without alteration
(no precedent).
My own order of preference is 4 > 3 > 2 > 1. I imagine that going for
4 requires some kind of formal approval or consensus on the part of
the community of the CPAN contributors, ie you. So please comment.
Cheers,
- --
<< Tout n'y est pas parfait, mais on y honore certainement les
jardiniers >>
Dominique Quatravaux <[EMAIL PROTECTED]>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iQCVAwUBRkrJ5vTYH7KfeIIFAQK9yAQAw5H5UaKbGviC7g5bxMw5nDZUYBSs2MTL
SU/CHqVR32EavuMEefsgUL0R1FTqoy3I53FLsq3CmJMInNhq9r3vTquHnZBURtsp
egwR2zkoCSipSQpS8vdTPapl8fgjIX6r7tjwdhxuIgb3YBB03NvbUjA4N2xVNBVA
59Zzj1UfVug=
=zQDq
-----END PGP SIGNATURE-----
