-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
META data link to perl.org instead to GitHub #69
Comments
It actually doesn't. Some may find it more convenient to post pull requests here for review, but Devel-PPPort is a dual-life, blead-first distribution and all changes technically happen there first, and reviewed by the porters, before then being duplicated here in this repository for a cpan release. |
@karenetheridge I agree with your assessment concerning Indeed we make sure to keep |
So, what to do about this ticket @atoomic @karenetheridge |
Even though releases occur in blead first, it would be desirable to attract bug reports and pull requests here. Development pretty clearly happens in this repository now, not github.com/Perl/perl5, so I am in favour of changing the metadata. |
On 12/15/19 11:10 AM, Karen Etheridge wrote:
Even though releases occur in blead first, it would be desirable to
attract bug reports and pull requests here. Development pretty clearly
happens in this repository now, not github.com/Perl/perl5, so I am in
favour of changing the metadata.
—
That makes sense to me.
|
Because Devel-PPPort development happens on Github, it would be great to update metadata (Makefile.PL:102) to actually point a bugtracker and a repository to GitHub. It links to perl.org RT and gitweb now.
A similar change has already been made in a POD (#5).
The text was updated successfully, but these errors were encountered: