Migrating to Vox Pupuli

[ju5t]

As our focus has shifted to other priorities @saz suggested moving this module to Vox Pupuli.

Reference: https://voxpupuli.org/docs/migrate_module/

• Remove PDK .sync.yaml if it exists.
• Ensure correct LICENSE.
• Enable GitHub Issues.
• Vox Pupuli Admin: Verify all webhooks are disabled.
• Vox Pupuli Admin: Enable Automatically delete head branches in repository settings.
• Vox Pupuli Admin: Add the collaborators team to the Team list with Write permissions.
• Vox Pupuli Admin: Update access permissions to allow forge.puppet.com secret access for releases.
• Add to voxpupuli/modulesync_config.
• Execute voxpupuli/modulesync_config for the module.
• Release a new version under Vox Pupuli.
• Create a forge issue requesting deprecation of the old module.
• Write a blog post about the migration.
• Send notification to the mailing list about the new module.

[ju5t]

@bastelfreak I'm ready to move this to repo. I'm not entirely sure what this would do with the PR that's open at the moment though. Should we wait until that's resolved or can I move the repo before that?

I would like to keep my maintainer role by the way, if possible.

[bastelfreak]

All the PRs stay open and can still be merged, and you keep write access to the repo.

[ju5t]

@bastelfreak cool, migration is done! :)

[bastelfreak]

@ju5t thanks a lot!

[ju5t]

@bastelfreak what's the status of this? I was hoping when migrating this to you guys it would be treated better than I could, but it seems the project is a bit stale.

[saz]

It's primarily my fault. Planning to work on this this week