Hi, After a good night sleep, I´ve regrouped and though about the arguments presented, and I would like to reply to them.
On Fri, Sep 7, 2012 at 11:47 AM, sawyer x <xsawy...@gmail.com> wrote: > I don't understand why people upload things to CPAN that are specifically > exclusively without-a-doubt on-purpose just for them? Two reasons: * it is very convenient to install, just use the commands you already know about; * the author can include that module as a dependency on his projects like he does with all the other CPAN dependencies. The second one is the most important to me. Just because it is a module that you might not use, it might be a module that is installed on your system as a direct dependency of other modules I have on CPAN. Other use cases I have: Moo/Moose roles. I have a couple of roles that I reuse on a lot of projects, including some modules that eventually will be uploaded to CPAN. Are they worth moving to Moo(se)X::Roles::Something? Maybe they are, maybe they aren't. At this point I don't really know, and instead of polluting that namespace, I would upload them to my Author namespace, and use them as dependencies. If others find them useful, I can then rename them to a more official namespace and adjust my own distributions. > People always say "hey, if it's useful for even one person, it should be out > there", but these are things that are on purpose only useful and meant for > the author. Why upload them? Just because it's only useful to the author, it doesn't mean it only be installed by the author. CPAN is there to promote reuse. I have modules that I want to reuse but I don't know if they should be real full blown CPAN modules. So I uploaded them to my Author namespace, and reuse them on other modules. Personal modules does not imply single use or private use only. On Fri, Sep 7, 2012 at 12:30 PM, David Precious <dav...@preshweb.co.uk> wrote: > Public experiments, IMO, would be better done on GitHub et al, with the code uploaded to CPAN if it reaches a point where it's useful. Without exposure on CPAN, how would you evaluate usefulness? Our tools make it trivial to install modules from CPAN, and uploading something to CPAN proves a certain level of commitment to the work. I can throw something half-assed to github as a proof of concept. Sending it to CPAN is whole new ball game, I won't upload stuff that I'm not terrible proud of. On Fri, Sep 7, 2012 at 4:48 PM, sawyer x <xsawy...@gmail.com> wrote: > It's not about putting weight strain on CPAN mirrors (though I'm not sure > it's impossible to make such a claim), but of the pollution of CPAN. About this two points, strain and pollution of CPAN. The fact that they are clearly labeled Author modules actually helps with the strain on CPAN. Right now, a lot of personal modules (Task::BeLike and dzil PluginBundles::Author) exist and are mixed with more useful modules. But if they are clearly labeled, then you can target them with a policy to reduce the strain on CPAN. You can skip indexing them on search/metacpan, or index them and not include them on general search results. Make that opt-in. You can more aggressively remove old versions. You can delete old versions to Backpan. Or even send skip sending them at all to Backpan. And you can skip them when you create your local CPAN mirror, pulling only your own namespace. Regarding pollution of CPAN, moving personal stuff that *is already on CPAN* to a personal namespace actually reduces the pollution of CPAN. > When I reach a new machine, I clone both and set things up. I used to also > have a bash script that ran "cpanm $MODULES" to install the modules I use > frequently. Me too. The cpanm part is actually: cpanm Task::BeLike::MELO I would love to move that to Author::MELO::Stack (with possible new ::Stack::Runtime and ::Stack::Devel). On Fri, Sep 7, 2012 at 5:20 PM, Dave Rolsky <auta...@urth.org> wrote: > I think it's also worth noting that every extra upload has the potential to > show up in search results. As I said above, the fact they are clearly labeled on the Author namespace makes it possible to remove them from default search results. Right now, personal modules are spread throughout CPAN and they already pollute the search results. *** I still think this is an idea worth considering. You can see it as just another garbage namespace, but if you do, I can only argue "Good, maybe a lot of the garbage already on CPAN can be moved to their proper place now". I still need to upload a policy module that will be included with all my modules. I can pollute the Pod::Weaver::PluginBundle::Author somemore but I rather not. Just because its personal, doesn't mean its not meant for reuse. Even if it just personal reuse, it is still reuse. And IMVHO, reuse is what CPAN is all about. What do you think? -- Pedro Melo @pedromelo http://www.simplicidade.org/ http://about.me/melo xmpp:m...@simplicidade.org mailto:m...@simplicidade.org
