There's no naming convention. Anyone using the p5 prefix will have been doing so to distinguish it from p6 rather than p4, but thankfully that is no longer a concern. I would not fret about the name.
Github and CPAN are not connected. Nor are Gitlab and CPAN. Nor Bitbucket and CPAN. How you store or manage your code prior to release is unimportant for CPAN. The only means of connecting them is with the repository metadata which you can include with your dist when uploaded (see CPAN::Meta::Spec for lots more on this).
I wouldn't have different accounts on any one hub/forge for different purpose. Github has "Organisations" and you can release code in any given organisation to which you belong. That's how I would separate work from hobbyist releases.
🦛
In reply to Re: Version Control - GitHub and CPAN
by hippo
in thread Version Control - GitHub and CPAN
by Bod
For: | Use: | ||
& | & | ||
< | < | ||
> | > | ||
[ | [ | ||
] | ] |