Skip to content
This repository has been archived by the owner on Dec 20, 2024. It is now read-only.

Deprecate and archive puppet-mcollective #396

Closed
smortex opened this issue Apr 4, 2023 · 3 comments · Fixed by #397
Closed

Deprecate and archive puppet-mcollective #396

smortex opened this issue Apr 4, 2023 · 3 comments · Fixed by #397

Comments

@smortex
Copy link
Member

smortex commented Apr 4, 2023

For these reasons, this module does not make sense in a modern Puppet ecosystem, therefore I propose to deprecate and archive it.

@tuxmea
Copy link
Member

tuxmea commented Apr 5, 2023

+1 @bastelfreak

@TheMeier
Copy link

reminder: please archive :D

@ekohl
Copy link
Member

ekohl commented Dec 20, 2024

Copying the steps from https://voxpupuli.org/docs/deprecated_and_archived_modules/ and it looks like most steps have already been taken.

  • An issue needs to be raised on the module to discuss whether it should be archived or not. An additional post to the mailing list for better visibility is recommended. The decision will be made by lazy consensus (as described in our governance guidelines)
  • The README.md needs a bold message at the beginning
    • It must mention that the module is archived
    • If a successor exists, that one should be linked to
    • The deprecation issue in that project must be linked
  • The GitHub repository needs to be archived in the GitHub settings
  • On forge.puppet.com the module needs to be archived, with a link to the successor (if available)
  • The module needs to be removed from our modulesync_config.
  • The Vox Pupuli admins can manage the org secrets. The permission for the archived module needs to be revoked.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants