Beefy Boxes and Bandwidth Generously Provided by pair Networks
We don't bite newbies here... much

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

If you (and the co-maintainer) already have a source repo that meets your needs (especially if it is publicly available), I would just stick with that. Just gathering bug reports, IMO, is not reason enough to push an unmaintained copy (assumption) of your source to github. IMO, it is better to have one canonical source, and use the rest as automatically updating child repositories. Changes can flow up from the child to the parent, but without the automatically updating (or just a lack of communicating that XYZ is the master repo) part, there will be a question as to which is the authoritative source.

However, if you are planning on setting up synchronization between the two repos, or if RT does not meet your needs, or if GitHub provides some whiz-bang feature that you just need to have, then it may make sense to look at GitHub for hosting your source.

GitHub also supports a subset of svn operations.

There is more value to GitHub than just that it uses git. There are pulls, issue tracking and management, project wiki, and a few other tools that I am not familiar with. It comes down (at least to me) to if the tool does the job you need. It seems to me that if the provider of your source repo is doing everything you need, change for the sake of change is not a good thing.


In reply to Re: Maintaining a CPAN Module. by MidLifeXis
in thread Maintaining a CPAN Module. by tmharish

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, 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, 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.
  • Log In?

    What's my password?
    Create A New User
    and all is quiet...

    How do I use this? | Other CB clients
    Other Users?
    Others examining the Monastery: (4)
    As of 2018-04-23 20:26 GMT
    Find Nodes?
      Voting Booth?