Re^2: How do I package a module and related apps for successful upload to cpan

Yes, after your advice I found those too. I decided to repackage my collection under Weather -- but not Weather::NOAA simply because the code there is defunct and the author unreachable. Weather::GHCN::Fetch is my new package name.

A quick look at Geo::WeatherNOAA says it's for grabbing forecasts from www.weather.gov. Looks like it once accessed http://iwin.nws.noaa.gov/iwin/ but not any more. The url nws.noaa.gov is still ping-able, but doesn't return any response. Weather:: seems like a better place for that module (if it even works) and it shouldn't have NOAA in the name.

CPAN has some cruft, that's for sure. Is there a process for cleanup?

Comment on Re^2: How do I package a module and related apps for successful upload to cpan

Replies are listed 'Best First'.
Re^3: How do I package a module and related apps for successful upload to cpan (CPAN and Git References) by eyepopslikeamosquito (Archbishop) on Sep 17, 2022 at 23:11 UTC
CPAN has some cruft, that's for sure. Is there a process for cleanup? This is a problem faced by all open repositories with a low barrier to entry, such as Python Package Index, RubyGems, GitHub ... even Perl Monks (which has an infamous zombification process - including an option to raise from the dead :). To encourage authors to cleanup their old cruft on CPAN, Perl has The BackPAN (a complete history of CPAN) from which nothing is ever deleted. Curating CPAN References Curating Old Releases by neilb (2015) Curating CPAN sometimes means really deleting stuff by BooK (2014) "Curating CPAN" section at Writing Solid CPAN Modules CPAN References Writing Solid CPAN Modules Re^7: Meaning of XS object version (Package Manager Security References - example building Perl securely from source) - includes an example of securely building Perl from scratch on Linux, followed by installing CPAN modules via `cpanm` RFC: A guide to installing modules for Win32 (2022 Edition) by pryt (Jul 25 2022) A guide to installing modules for Win32 (2022 Edition) by pryt (Jul 31 2022) Git References Git (wikipedia) GitHub (wikipedia) GitLab (wikipedia) Re^4: testing/release advice [was: Stopping tests] by stevieb (2023) - use Github Actions to perform automated CI testing on every push to the repo RFC: Continuous Integration (CI) for your CPAN modules (for free!) by stevieb (2016) - CI with Github, Travis-CI, Coveralls, CPAN, Devel::Cover (reply mentions cpancover) Re^8: How to create and name module tarball for CPAN by soonix (2023) - links to git tutorials See Also Re: Sane deprecation policy for a CPAN module? (Software Versioning and Exporter References) Updated: Added References sections.	[reply] [d/l]

Replies are listed 'Best First'.

Re^3: How do I package a module and related apps for successful upload to cpan (CPAN and Git References)
by eyepopslikeamosquito (Archbishop) on Sep 17, 2022 at 23:11 UTC

CPAN has some cruft, that's for sure. Is there a process for cleanup?

This is a problem faced by all open repositories with a low barrier to entry, such as Python Package Index, RubyGems, GitHub ... even Perl Monks (which has an infamous zombification process - including an option to raise from the dead :).

To encourage authors to cleanup their old cruft on CPAN, Perl has The BackPAN (a complete history of CPAN) from which nothing is ever deleted.

Curating CPAN References

Curating Old Releases by neilb (2015)
Curating CPAN sometimes means really deleting stuff by BooK (2014)
"Curating CPAN" section at Writing Solid CPAN Modules

CPAN References

Writing Solid CPAN Modules
Re^7: Meaning of XS object version (Package Manager Security References - example building Perl securely from source) - includes an example of securely building Perl from scratch on Linux, followed by installing CPAN modules via cpanm

RFC: A guide to installing modules for Win32 (2022 Edition) by pryt (Jul 25 2022)
A guide to installing modules for Win32 (2022 Edition) by pryt (Jul 31 2022)

Git References

Git (wikipedia)
GitHub (wikipedia)
GitLab (wikipedia)

Re^4: testing/release advice [was: Stopping tests] by stevieb (2023) - use Github Actions to perform automated CI testing on every push to the repo
RFC: Continuous Integration (CI) for your CPAN modules (for free!) by stevieb (2016) - CI with Github, Travis-CI, Coveralls, CPAN, Devel::Cover (reply mentions cpancover)

Re^8: How to create and name module tarball for CPAN by soonix (2023) - links to git tutorials

See Also

Re: Sane deprecation policy for a CPAN module? (Software Versioning and Exporter References)

Updated: Added References sections.

[reply]
[d/l]