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

Resolution: Preparing the Raku Ecosystem for the Future #318

Merged
merged 3 commits into from
Mar 24, 2022
Merged
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 28 additions & 0 deletions solutions/meta/sunsetting-p6c-cpan.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
# Sunsetting p6c / CPAN ecosystems

This document provides a solution to [issue 316](https://github.com/Raku/problem-solving/issues/316).

## Announcement

The p6c and CPAN ecosystems are to be sunsetted as far as installation of Raku modules is concerned. This will consist of the following steps:
lizmat marked this conversation as resolved.
Show resolved Hide resolved

- Enable the Raku Ecosystem Archive by default in zef immediately
This will allow any installation of a Raku module to look through the [Raku Ecosystem Archive (REA)](https://github.com/raku/REA) if not found on zef, p6c or CPAN ecosystems.

- Disable the p6c / CPAN ecosystems by default in zef immediately
With the REA enabled, the modules that currently reside on p6c and CPAN ecosystems can be downloaded and installed from the REA.

- Migrate the remaining raku-community-modules to zef before July 1st 2022
There are about 95 modules in the raku-community-modules repo that still need migrating to zef ecosystem. More than 20 have already been moved. Elizabeth Mattijsen intends to move them all by July 1st, unless someone beats her to it.

- Alert any module authors after July 1st, 2022
Any module authors still not having moved their modules to the zef ecosystem by July 1st 2022, should be informed with a i**single** issue that lists the modules in question. This could be an issue in the problem solving repo, but another repo would work as well. The module authors should also be able to indicate they no longer wish to support a module themselves: in that case, a move to the raku-community-modules repo should be considered.
lizmat marked this conversation as resolved.
Show resolved Hide resolved

- Stop the ecosystem harvesters on January 1st, 2023
Stop running the ecosystem harvesters of p6c and CPAN, both the zef one as well as the one run for the REA. This will effectively disregard any updates of any modules on those ecosystems.

- Offer to move any remaining modules to raku-community-modules
Any authors still having modules in the p6c and CPAN ecosystems, should be offered help in moving their modules to zef and/or the raku-community-modules repo (which would then be followed by a move to the zef ecosystem).

- Security updates on remaining modules
Any module remaining in the p6c and CPAN ecosystem, should be forked in the raku-community-modules repo and re-released with a version bump if a security update to these, clearly abandoned modules, is necessary.