search

Dual-Life / Devel-PPPort

Perl/Pollution/Portability
9 stars 28 forks source link

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

Open ppisar opened 5 years ago

ppisar commented 5 years ago

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 (https://github.com/Dual-Life/Devel-PPPort/issues/5).

karenetheridge commented 5 years ago

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 commented 5 years ago

@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 commented 4 years ago

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

karenetheridge commented 4 years ago

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 commented 4 years ago

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.