Skip to content
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

Open
ppisar opened this issue May 15, 2019 · 5 comments
Open

META data link to perl.org instead to GitHub #69

ppisar opened this issue May 15, 2019 · 5 comments

Comments

@ppisar
Copy link

ppisar commented May 15, 2019

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).

@karenetheridge
Copy link
Member

Because Devel-PPPort development happens on Github

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.

@atoomic
Copy link
Member

atoomic commented May 15, 2019

@karenetheridge I agree with your assessment concerning dist modules but in practice over the last few months most of the development for PPPort occurs there directly as we can easily use Travis CI.

Indeed we make sure to keep blead in sync with master and only release what is in blead!

@khwilliamson
Copy link
Member

So, what to do about this ticket @atoomic @karenetheridge

@karenetheridge
Copy link
Member

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.

@khwilliamson
Copy link
Member

khwilliamson commented Dec 15, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants