From 3de16a68c8cc2fb5fcc91f7a32cc15a2e7955eec Mon Sep 17 00:00:00 2001 From: Elizabeth Mattijsen Date: Tue, 22 Feb 2022 14:04:02 +0100 Subject: [PATCH 1/3] First stab at resolution document for #316 --- solutions/meta/sunsetting-p6c-cpan.md | 31 +++++++++++++++++++++++++++ 1 file changed, 31 insertions(+) create mode 100644 solutions/meta/sunsetting-p6c-cpan.md diff --git a/solutions/meta/sunsetting-p6c-cpan.md b/solutions/meta/sunsetting-p6c-cpan.md new file mode 100644 index 0000000..45e9d1d --- /dev/null +++ b/solutions/meta/sunsetting-p6c-cpan.md @@ -0,0 +1,31 @@ +# 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: + +- 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. + +- Stop the ecosystem harvesters on January 1st, 2023 +Stop running the ecosystem harvesters of p6c and CPAN. This will effectively disregard any updates of any modules on those ecosystems. But any updates with a new version would still become visible in the REA, as that runs its own harvester. + +- 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). + +- Stop the REA harvester on July 1st, 2023 +Stop running the REA harvester: this would make the p6c and CPAN ecosystems truly sunsetted. + +- 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. From 48d2b014bd008b89b9bded19e2885a9d3f15f1ad Mon Sep 17 00:00:00 2001 From: Elizabeth Mattijsen Date: Wed, 2 Mar 2022 10:03:00 +0100 Subject: [PATCH 2/3] Stop the REA harvester at the same time as zef This will make the sunsetting of p6c and cpan clearer and more definite. It also wouldn't necessitate REA offswitching by default. Anybody who would still like to use p6c / cpan as an ecosystem, is welcome to take the REA harvester code and set up their own ecosystem which can then be activated in zef by those people who would like to do that. --- solutions/meta/sunsetting-p6c-cpan.md | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/solutions/meta/sunsetting-p6c-cpan.md b/solutions/meta/sunsetting-p6c-cpan.md index 45e9d1d..2c9c07b 100644 --- a/solutions/meta/sunsetting-p6c-cpan.md +++ b/solutions/meta/sunsetting-p6c-cpan.md @@ -19,13 +19,10 @@ There are about 95 modules in the raku-community-modules repo that still need mi 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. - Stop the ecosystem harvesters on January 1st, 2023 -Stop running the ecosystem harvesters of p6c and CPAN. This will effectively disregard any updates of any modules on those ecosystems. But any updates with a new version would still become visible in the REA, as that runs its own harvester. +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). -- Stop the REA harvester on July 1st, 2023 -Stop running the REA harvester: this would make the p6c and CPAN ecosystems truly sunsetted. - - 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. From e1c5d9e097eebbda1d7ed3df37e20e6a9ca551c8 Mon Sep 17 00:00:00 2001 From: Elizabeth Mattijsen Date: Wed, 2 Mar 2022 14:15:37 +0100 Subject: [PATCH 3/3] Use deprecated instead of sunsetting initially - also refer to sunsetting at shutdown of harvesters - remove spurious i --- solutions/meta/sunsetting-p6c-cpan.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/solutions/meta/sunsetting-p6c-cpan.md b/solutions/meta/sunsetting-p6c-cpan.md index 2c9c07b..888430e 100644 --- a/solutions/meta/sunsetting-p6c-cpan.md +++ b/solutions/meta/sunsetting-p6c-cpan.md @@ -4,7 +4,7 @@ This document provides a solution to [issue 316](https://github.com/Raku/problem ## 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: +The p6c and CPAN ecosystems are to be deprecated as far as installation of Raku modules is concerned. This will consist of the following steps: - 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. @@ -16,10 +16,10 @@ With the REA enabled, the modules that currently reside on p6c and CPAN ecosyste 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. +Any module authors still not having moved their modules to the zef ecosystem by July 1st 2022, should be informed with a **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. - 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. +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. This will mark the sunsetting of the p6c and CPAN 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).