I am a bit concerned that people who transfer repos to pytest-dev think that it receives magic maintenance because this relevant section in the docs
http://doc.pytest.org/en/latest/contributing.html#submitting-plugins-to-pytest-dev is not very explicit about it, even says "sharing some of the maintenance responsibility". I suggest we explicitely say that maintainers are generally expected to continue maintaining their plugins. And how about having a "pytest-dev" user which has release rights on pypi for all pytest-dev plugins? The credentials could be shared in a file in our public repo, encrypted to known GPG public keys. Speaking of which, we could collect gpg keys of contributors in another file. lastly, if we had a pure pytest-announce mailing list we could announce new pytest-dev plugins (from time to time) and releases there. We can certainly get that list on python.org. best, holger
holger.key
Description: application/pgp-keys
_______________________________________________ pytest-dev mailing list [email protected] https://mail.python.org/mailman/listinfo/pytest-dev
