Basically this will outline the basic process to transfer a repo over to be community maintained. It consists of a few steps:
- Create an issue on Our Plugin Community Issues which should have a template that asks a few questions to determine if you would like to continue maintaining it or not.
- A maintainer will evaluate and assign the issue to themselves.
- Attempt to bring the plugin into as much alignment as possible to our Skel
- Depending on whether it is a personal or an organizational repo the requirements are slightly different. In order to transfer the repo out you must be an owner on the repo and to transfer in you must be an owner in the
sensu-pluginsorg to accept it. - Once the transfer has been initiated to the maintainer he will then transfer it to their account and then to the org (unless they happen to be an owner in both but they would probably not need this guide)
- Once this has been completed the maintainer should then mark the issue with a label of
Repo Createdand then do the required setup to do various things like:- terraform setup
- travis setup
- rubygems setup
- badges
- cleanup
- If there was a gem previously pushed to rubygems.org then we need to become an owner so we can can do deploys. The command should look like this:
gem owner sensu-plugins-systemd -a sensu-plugin@sensu-plugins.io - Once everything is setup the issue should be closed and any concerns like adding additional documentation, testing, etc should create issues in the respective repo.