in reply to Where to store the "golden" copy of a CPAN distro?

Well, it doesn't matter :) you use github to share/publish your code , to get an issue/bug-tracker/wiki... to isolate your ip/computer from the rest of internet

you need pgp/gnupg keys to publish to github, they're what make the github version "golden" ie official

you can move away from github, its your public keys that make it official for everyone else

Just remember to configure your git to not leave a history of every computer you've ever used :) and don't commit passwords and other sensitive data

but you shouldn't worry about it , the actual chances of attracting interest enough for someone to fork your module and send you a pull request are low :)

Also, FWIW, the way github works (last I checked years ago), you always create stuff locally and push to github (git push origin master)

Read more about git/github and try it from your browser at git parable, practical git, git howto, try github found via What is the minimal GIT setup?

  • Comment on Re: Where to store the "golden" copy of a CPAN distro? (on github)

Replies are listed 'Best First'.
Re^2: Where to store the "golden" copy of a CPAN distro? (on github)
by tobyink (Canon) on Aug 31, 2013 at 12:14 UTC

    I think you're misunderstanding the point of giving Github your SSH public keys. They are just there so git-over-ssh can work; not to make anything "official".

    use Moops; class Cow :rw { has name => (default => 'Ermintrude') }; say Cow->new->name

      I think you're misunderstanding the point of giving Github your SSH public keys. They are just there so git-over-ssh can work; not to make anything "official".

      Nope, merely misremembering/imagining that github did something extra , like sign some SHA1's with your public keys...

        They'd need your private keys to sign anything. You should never give out your primary keys.

        use Moops; class Cow :rw { has name => (default => 'Ermintrude') }; say Cow->new->name