user-pic

KENTNL

  • Commented on What is your release process?
    I have a few oddities, and I do things MyWay™, but I have a few tricks I don't see employed often which I find incredibly useful for a number of reasons. The most important to me, is the [Git::CommitBuild] plugin...
  • Commented on The Four Major Problems with CPAN
    I think it would be "nice" to have something at least somewhat visible via the metacpan ui, but it definitely has to be "external" data to classes, data provided by user submission / crowd sourcing / data analysis , NOT...
  • Commented on Pumpkin Perl - Redux
    I definitely prefer "pumpkin" and "pumpkin perl" over "perli". "perli" is just begging to increase the current rate at which people associate "perl" with "peril". Can't say I'm fond with that. After discussion with MST, it appears to me we're...
  • Commented on Pumpkin Perl - Redux
    just wait, harry potter references are just around the corner. pumpkinbrew init pumpkinbrew abracadabra wand -v Image::Magick...
  • Commented on Pumpkin Perl - Redux
    I have some thoughts, but they're not really "well, if we do x then we have to do y, z etc as well", more "there are many things y which are hard to get away with doing without doing x"....
  • Commented on Bringing Perl5 to GitHub
    I feel the real let-down of github issues is its very weak on metadata vs RT. Metadata tools are limited to tagging and milestones, and thats basically it, and for seriously large projects this gets seriously out of hand. ie:...
  • Commented on Visually graphing module dependencies
    Something else you may want to consider as a feature: Classifying dependencies by type, and augmenting the graph to suit, ie: Build/Configure/Runtime/Test/Develop dependencies And "Suggested/Recommended/Required" subsets of those dependencies. You could opt to include these in the depgraph, and colour/pattern...
  • Posted Redesigning Package::Strictures to KENTNL
    Package::Strictures on metacpan Design goals
    1. An infrastructure for having “optional” code blocks…
  • Posted Musing on Perl::Critic config to KENTNL

    I've been exploring the Perl::Critic configuration file somewhat, and something struck me as unusual.

    It seems fine for using for the usecase of "inherit some predefined set of rules and apply them selectively", which works fine if you ju…

  • Commented on Please Ensure ABSTRACT and LICENSE fields in your META.yml/json
    Yeah, actually, I was aware of this problem with the CPANdeps service months ago, possibly even years ago. Emitting only YAML is the default behaviour if you're using the basic (@Basic) bundle. Users can freely elect to not generate YAML,...
  • Posted Please Ensure ABSTRACT and LICENSE fields in your META.yml/json to KENTNL

    I've been opening quite a few bugs lately for distributions failing these 2 criteria, so, I figured I'd save everyone some effort and unify it cohesively.

    Reason

    While it may seem a trivial squabble, ABSTRACT and LICENSE…

  • Commented on Looking up the location of an IP address
    "Web site localisation: automatically redirecting the user to the best default site, perhaps changing the language in the process." I should point out if it wasn't already obvious that you should never infer language by source IP's country code. Its...
Subscribe to feed Recent Actions from KENTNL

  • asknet999.myopenid.com commented on The Four Major Problems with CPAN

    Other than voting, metacpan or cpan site should include a counter that tells how many times a particular module has been installed or downloaded. This is one of the measurement used by many users when there is a huge catalog. For example, mobile apps installed from app store has this counter, the greasemonkey scripts installed from userscripts.org has something similar.

    What I believe, is CPAN model should be similar to Mobile app store, where the app store gives information like; reviews, rating, no of downloads, other modules by author, suggested modules and so on.

  • Brendan Byrd commented on The Four Major Problems with CPAN

    This discussion was held several times over the years. A solution INSIDE the CPAN package is pointless here. For one: It doesn't address anything about EXISTING packages, which are 99% of the problem, new modules are rarely having these problems. So next, if you mandate definition inside the META file, then someone will NOT do it, or do it wrong. What you have then? RIGHT, the exactly same state then before.

    Calm down. Some of the ideas are META improvements, but I think the bulk of the fixes would be the first two ideas: search engine improvements and better ways of handling…

  • larryl commented on The Four Major Problems with CPAN

    @brian d foy said:

    > I am constantly and consistently surprised about how many
    > people do not first try to work with existing projects.

    For me, GitHub has been the single biggest factor in lowering the barriers to entry to making contributions to existing CPAN modules. I find I'm far more likely to contribute changes to an existing module when all I need to do is fork it and send a subsequent pull request. Maybe if more source code was handled via GitHub (or similar mechanism) there might be less of a tendency to reinvent the wheel as opposed to enhancing existing co…

  • Buddy Burden commented on The Four Major Problems with CPAN

    Yet Another Problem with the ideas (not that I wish to discourage you--definitely keep pursuing these ideas, as they're much needed--but just to make sure you're thinking of all the issues) is that, while sometimes there is a "right" and a "wrong" module, sometimes there isn't. That is, sometimes there are two modules that both do the job and there just isn't a clear reason to prefer one over the other. Perhaps one is OO and the other isn't. Perhaps one has more features but the other has a simpler interface. Perhaps one works well for A but not at all for B, while the other…

  • grt@opendevnet commented on Bringing Perl5 to GitHub

    Hmm, I agree with these comments. It's possible to duplicate efforts ... even with forking and pulling :-) Proliferating organizational repos can confuse people (or at least people like me) who are used to the well-herded namespaces of CPAN!

    I think I am encouraged that Matt Trout thinks something like perlsourcemap is a good idea. Well, I am either encouraged or just less afraid :-)

Subscribe to feed Responses to Comments from KENTNL

About blogs.perl.org

blogs.perl.org is a common blogging platform for the Perl community. Written in Perl and offering the modern features you’ve come to expect in blog platforms, the site is run by Dave Cross and Aaron Crane, with a design donated by Six Apart, Ltd.