Re: Proposal for building module info
On Fri, Feb 10, 2012 at 4:47 AM, Neil Bowers n...@bowers.com 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 the data class? CPAN::Module::GetMetadata for the builder? CPAN::Module::Metadata::Factory? The CPAN distribution already has CPAN::Module. Since your classes have nothing to do with CPAN.pm or installing CPAN modules, I think it's confusing to put your code under that namespace. If you're really not happy with Curation, perhaps CPAN::Summary would be a more fitting name, or CPAN::Mashup if you want to be cute about it. David
Re: Proposal for building module info
[[ This message was both posted and mailed: see the To, Cc, and Newsgroups headers for details. ]] In article cde0816b-a963-4854-9e76-defceefa6...@bowers.com, Neil Bowers n...@bowers.com 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 idea, although I'd probably go with CPAN::Curate CPAN::Module::Metadata for the data class? CPAN::Module::GetMetadata for the builder? CPAN::Module::Metadata::Factory? I don't really like the second name, but can't think of a better one off the cuff. I don't think you have to worry about the internal classes so much. Pay more attention to the user-visible ones. You can change the hidden ones later. :) -- brian d foy (one of many PAUSE admins), http://pause.perl.org PAUSE instructions: http://pause.perl.org/pause/query?ACTION=pause_04about Archives: http://www.xray.mpe.mpg.de/mailing-lists/modules Please send all messages back to modu...@perl.org with no CC to me.
Re: Proposal for building module info
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 are cool. Strengthening the CPAN is Museum, with even more stuff in the basement than what you see by strolling through the galleries idea may help with the endless stream of criticism from people who want CPAN to be something other than what is is. -- Digital artists often sneer when they effect an effect because sometimes affect affects an effect's effect.
Re: Proposal for building module info
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::Factory? I don't really like the second name, but can't think of a better one off the cuff. There are a number of modules which do related things, but I couldn't find one which does this, when I started. Questions: Is there an appropriate module / distribution that this could be fit into? Does this make sense to have as a separate dist? What are good names for the two classes? Firstly I favour a name like Module::Metadata::* because: o It'll be data about modules o There are several modules in that namespace already (including 2 of mine) For the last part (the *), I'd use Metacpan, as in Module::Metadata::Metacpan since that's the source of this particular data. Of course, other sources may come into it, but Metacpan remains the primary source (I'm assuming). Either way, I feel it's a fairly good name. Secondly, Neil, if you want send me the code and I'll clean it all up and turn it into a stand-alone module -- Ron Savage http://savage.net.au/ Ph: 0421 920 622
