Remove link to old CPAN Ratings site#26
Open
paultcochrane wants to merge 1 commit into
Open
Conversation
As noticed in iinteractive#22, the cpanratings link is a redirect. The CPAN Ratings site is no longer online and [was set to read-only in 2018](https://log.perl.org/2018/06/cpan-ratings-read-only.html). See also [the discussion about removing CPAN Ratings MetaCPAN](metacpan/metacpan-web#1653). Since the site is no longer available, it seems a good idea to remove the link to it from the OX documentation.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As noticed in #22, the cpanratings link is a redirect. The CPAN Ratings site is no longer online and was set to read-only in 2018. See also the discussion about removing CPAN Ratings MetaCPAN. Since the site is no longer available, it seems a good idea to remove the link to it from the OX documentation.
Note that implementing this change would also resolve the issue mentioned in #22.