Simplify plugin adoption guidelines (github repository transfer) #6
Description
The current documented process for transferring a plugin under pytest-dev is quite complex and it does work work wellbeing done offline: it requires both sender (plugin author) and receiver (one random pytest admin) to be available at the same time.
Being online is not easily achieved as there is no ultimate IM that everyone uses and we also have timezones.
I seen migrations being delayed for months, sometimes even more than an year due to broken communication channels so I am considering proposing few changes that should make it easier.
- Plugin author should open ticket on https://github.com/pytest-dev/meta/issues for adoption, this will be used as tracker, likely linked on a similar issue in the source repository.
- pytest-dev cores confirm that the plugin is meeting the documented requirements
- plugin author is invited to pytedev team, once he accepts github invitation he can create new repositories under pytest-dev. This also enables him to perform the transfer at any time he wishes.
- Once the transfer happens, one pytest-dev admin restores the rights of the plugin author. This is needed because transfer resets ACL and github secrets
- Now plugin author can fix secrets and perform other administrative changes related to the transfer, like reconfigure CI/CD pipelines.
This process does not require pytest admin and plugin author to work in tandem to perform the move and avoids double move of repository, which was quite an awkward move. If the light strikes the pytest admin mid process, we can end-up loosing control over the repository.
The only downside of this process is that the plugin author temporary looses administrative rights on the repository. Write rights are not affected at any moment because when author is added to the team, he also receives write rights to all repos.