TIMTOWTDI. At times, there also seems to be TMWTDI (Too Many Ways To Do It). That's where I feel like I'm at with the Dist::Zilla right now. There are tons of Dist::Zilla bundles out there that allow you to do all kinds of crazy things. Over the past day, I've fell into kind of a rabbit hole exploring all the different options for automating module maintenance on CPAN and on GitHub.

Though I've learned quite a bit, I'm left with many questions at this point and feeling a little lost at sea. I see many developers simply mirroring their CPAN module on GitHub. That's probably convenient, but it seems to entail sorting through a lot of cruft and it's not very inviting to go on GitHub and see all the CPAN related modules. But cpanm allows you to install a cpan module from a GitHub repo so maybe it's worth it for that? And, overall, how much work and effort should go into customizing a release for GitHub as compared to CPAN? For example, is it good to have a different README and install instructions for GitHub compared to CPAN? And is Pod::Weaver the best way to autogenerate the pod or is it easier just to rely on a default template that you modify? Also, some more basic questions: when do you commit to GitHub vs. releasing to GitHub and CPAN?

I have a bunch of other questions but I was wondering if I could get some basic advice and hear how others are using Dist::Zilla/CPAN/GitHub to try to find an optimal software release solution. Thanks.

$PM = "Perl Monk's";
$MCF = "Most Clueless Friar Abbot Bishop Pontiff Deacon Curate Priest";
$nysus = $PM . ' ' . $MCF;
Click here if you love Perl Monks

In reply to What are your best practice recommendations for maintaining CPAN module with GitHub repo? by nysus

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.