Re: naming advice required
On Mon, 2009-11-09 at 09:17 -0500, Ryan Voots wrote: On Sunday 08 November 2009 02:32:32 Jonathan Rockway wrote: Why not just Github::? I Thought the typical convention was to try to find some other root namespace to put things in rather than making yet another one? Well,someone has to start the the root namespace sometime. But it is nice of you to think about it. I like modules that are related to applications or implementing applications to start in App:: though. Nadim.
Re: naming advice required
Aristotle Pagaltzis wrote: * Ryan Voots simcop2...@yahoo.com [2009-11-09 15:20]: I Thought the typical convention was to try to find some other root namespace to put things in rather than making yet another one? No one browses CPAN by namespace any more, so it hardly matters. Ahem. Just because it's deliberately made difficult to do so doesn't mean that no one does it. In particular the Math and Algorithm namespaces are something I browse through often, and I doubt that I'm the only one. Whereas I find the trend toward cutesy names problematic. Because ultimately what matters is that things be findable by sticking the obvious keywords into search.cpan.org. Github::Fork::Parent is quite acceptable by that criterion. Regards, -john
Re: naming advice required
On Tuesday 10 Nov 2009 19:42:09 John M. Gamble wrote: Aristotle Pagaltzis wrote: * Ryan Voots simcop2...@yahoo.com [2009-11-09 15:20]: I Thought the typical convention was to try to find some other root namespace to put things in rather than making yet another one? No one browses CPAN by namespace any more, so it hardly matters. Ahem. Just because it's deliberately made difficult to do so doesn't mean that no one does it. In particular the Math and Algorithm namespaces are something I browse through often, and I doubt that I'm the only one. Yeah. I should note that now that I've started contributing to CPANHQ (see http://perlbuzz.com/2009/07/introducing-cpanhq.html ) I've been thinking of implementing a dynamic category tree, similar to the Sourceforge.net/old- Freshmeat.net trove categorisation, only somewhat more suitable to Perl and CPAN. People didn't like my suggestion for a list of canonical categories besides the keywords section at the META.yml, but I think I can use the keywords section for that by doing cat/t/topic/word-proc keywords (or alternatively keep the database in an external place). I don't intend to depend on the authors alone - by all means ordinary surfers will be able to tag or categorise stuff too (though that would be with less weight). Also see this post to the wikimedia-L on why I think free-form tags have not completely superseded category trees: http://lists.wikimedia.org/pipermail/foundation-l/2009-October/055734.html I should note that as great as the hierarchical organisation of the Perl 5 namespaces is (and by infusion CPAN's), it still can be misleading. If you're looking for an OOP module, you are likely to look under Object- or Class- - not under Moose. I don't want to have hard rules against keeping things in proper order, I'm just saying that we need a more semantic categorisation system than the Perl 5 namespaces. Regards, Shlomi Fish Whereas I find the trend toward cutesy names problematic. Because ultimately what matters is that things be findable by sticking the obvious keywords into search.cpan.org. Github::Fork::Parent is quite acceptable by that criterion. Regards, -john -- - Shlomi Fish http://www.shlomifish.org/ What does Zionism mean? - http://shlom.in/def-zionism Chuck Norris read the entire English Wikipedia in 24 hours. Twice.
Re: naming advice required
* On Fri, Nov 06 2009, Ryan Voots wrote: On Friday 06 November 2009 14:09:47 brian d foy wrote: Is this something that would be useful outside of GitHub? Are you screen scraping or doing something special with git? I think a name might be Github::Fork::Parent, if this is only for Github. Maybe even WWW::Github::Fork::Parent or something on there since its interacting with a website? Why not just Github::? -- print just = another = perl = hacker = if $,=$
Re: naming advice required
On Sunday 08 November 2009 02:32:32 Jonathan Rockway wrote: * On Fri, Nov 06 2009, Ryan Voots wrote: On Friday 06 November 2009 14:09:47 brian d foy wrote: Is this something that would be useful outside of GitHub? Are you screen scraping or doing something special with git? I think a name might be Github::Fork::Parent, if this is only for Github. Maybe even WWW::Github::Fork::Parent or something on there since its interacting with a website? Why not just Github::? I Thought the typical convention was to try to find some other root namespace to put things in rather than making yet another one?
Re: naming advice required
* Ryan Voots simcop2...@yahoo.com [2009-11-09 15:20]: I Thought the typical convention was to try to find some other root namespace to put things in rather than making yet another one? No one browses CPAN by namespace any more, so it hardly matters. Whereas I find the trend toward cutesy names problematic. Because ultimately what matters is that things be findable by sticking the obvious keywords into search.cpan.org. Github::Fork::Parent is quite acceptable by that criterion. Regards, -- Aristotle Pagaltzis // http://plasmasturm.org/
Re: naming advice required
# from Ryan Voots # on Monday 09 November 2009 06:17: Why not just Github::? I Thought the typical convention was to try to find some other root namespace to put things in rather than making yet another one? No, but that's a common misunderstanding. The recommendation is roughly: Claiming Github.pm for yourself is somewhat anti-social, where as breaking the ice on Github:: is liberating to anyone else who might come later (because it gives them a beaten path to follow.) But, if Github.pm and a tree under it already existed as a coherent object system/application, you should use GithubX:: for extensions (or whatever the Github.pm author's request is.) --Eric -- Insert random misquote here --- http://scratchcomputing.com ---
naming advice required
Hello GitHub allows to fork your git repository just by pushing Fork button. NGP (possible name - Net::GitHub::Parent) is a module to determine which module stands in a root of forking hierarhy or in other words, which repository is a parent one for this. Net::GitHub is a similar module, but it is more low level, more complex and requires several modules, for ex. Crypt::SSLeay. NGP will depend only on YAML::Tiny and LWP::UserAgent. Possible applications: my new projects: eumm-upgrade (to use new functionality of ExtUtil::MakeMaker) and eumm-migrate (to convert Makefile.PL to Build.PL). Both will use Module::Install::Repository to detect repository and NGP to get correct one (in case this one is forked one). -- WBR, Alexandr mailto:alexcho...@gmail.com
Re: naming advice required
On Thu, 2009-11-05 at 19:52 +0200, Alexandr Ciornii wrote: Hello GitHub allows to fork your git repository just by pushing Fork button. NGP (possible name - Net::GitHub::Parent) is a module to determine which module stands in a root of forking hierarhy or in other words, which repository is a parent one for this. Net::GitHub is a similar module, but it is more low level, more complex and requires several modules, for ex. Crypt::SSLeay. NGP will depend only on YAML::Tiny and LWP::UserAgent. Possible applications: my new projects: eumm-upgrade (to use new functionality of ExtUtil::MakeMaker) and eumm-migrate (to convert Makefile.PL to Build.PL). Both will use Module::Install::Repository to detect repository and NGP to get correct one (in case this one is forked one). so what is your request? Nadim.
Re: naming advice required
Hello 2009/11/5 nadim na...@khemir.net: NGP (possible name - Net::GitHub::Parent) is a module to determine which module stands in a root of forking hierarchy or in other words, which repository is a parent one for this. so what is your request? It's is the subject - is Net::GitHub::Parent a good name? Are there any other good names for this module? -- Alexandr Ciornii, http://chorny.net
