> At the moment I have everything internally under a CPAN::Curation::
> namespace, but if released separately I don't think that's appropriate.
>
> CPAN::Module::Metadata for the data class?
> CPAN::Module::GetMetadata for the builder? CPAN::Module::Metadata::Factory?
>
I like "Curation." Museums
Hi Neil
On 10/02/12 20:47, Neil Bowers wrote:
At the moment I have everything internally under a CPAN::Curation:: namespace,
but if released separately I don't think that's appropriate.
CPAN::Module::Metadata for the data class?
CPAN::Module::GetMetadata for the builder? CPAN::Module::Metadata
[[ This message was both posted and mailed: see
the "To," "Cc," and "Newsgroups" headers for details. ]]
In article , Neil
Bowers wrote:
> At the moment I have everything internally under a CPAN::Curation::
> namespace, but if released separately I don't think that's appropriate.
I like that
On Fri, Feb 10, 2012 at 4:47 AM, Neil Bowers wrote:
> At the moment I have everything internally under a CPAN::Curation::
> namespace, but if released separately I don't think that's appropriate.
I think that namespace is fine -- it's about your project, after all.
> CPAN::Module::Metadata for t
Hi,
At the start of each CPAN module review I do, there is a table of summary
information for all the modules reviewed. Ron suggested that the module which
builds up this information be released to CPAN. See an example at
http://neilb.org/reviews/constants.html
At the moment this is part of th
