Migrate module to Vox Pupuli

[ghoneycutt]

• Prepare your repo for transfer
  • If this module was created with PDK delete .sync.yaml.
  • Ensure that the module has a correct LICENSE file in the docroot that matches the mentioned license in the metadata.json.
• At this point you can transfer your own repository.
• Ask an admin to
  • Ensure github issues are enabled.
  • Verify that all webhooks are disabled.
  • Enable Automatically delete head branches in the repository settings.
  • Add the collaborators team to the module's Collaborators & Teams 'Teams' list with Write permissions (e.g. https://github.com/voxpupuli/puppet-gitlab/settings/collaboration (that link works only for admins).
  • Update the access permissions (that link works only for admins) for forge.puppet.com secrets so releases can be published.
• Add the module to our modulesync setup.
• Execute modulesync for this module.
• Our modulesync will delete a CONTRIBUTING.md in the root directory and place one at .github/CONTRIBUTING.md. Please enhance our existing template if the version in the docroot contains useful parts.
• Release the first version under Vox Pupuli.
• Create a GitHub issue for the FORGE project and ask to deprecate the old module (and approve the new one if the old one was approved as well).
• Do you think the module qualifies to be approved? Wait until it is released, then raise a GitHub Issue in the Puppetlabs organisation.
• Write a very short blog post about the migration (example). Write to our mailinglist about the migration/new blogpost.

[bastelfreak]

forge issue: puppetlabs/forge_issues#47

[bastelfreak]

blogpost voxpupuli/voxpupuli.github.io#433

[alexjfisher]

Reopening as I've spotted a few things left to cleanup.
See comments in #20 and #23