Hi All, I've now added most of core pytest-dev team (i.e. owners of pytest-dev on github/bitbucket) to the following districutions on the cheeseshop:
py pytest pytest-cpp pytest-faulthandler pytest-mock pytest-qt pytest-timeout pytest-xdist It seems most of the plugin authors/contributors haven't joined this yet. So if you're a pytest-dev member on github/bitbucket and would like to be able to release any of the above packages (or just want to increase their bus-factor even if you don't mind being able to release them) just let me know your pypi username. Likewise if you're a plugin maintainer and would like to increase the pypi bus-factor of your plugin give me permissions and ping me and I'll add all pytest-dev members to your package. No need to worry, unless there's something important and you're not responding for a few months no one will do a release without your consent. Regards, Floris On 5 August 2015 at 18:43, Floris Bruynooghe <[email protected]> wrote: > Hi all, > > As discussed at EuroPython I was looking at giving everyone in the > pytest-dev groups on bitbucket and github access on the cheeseshop > (pypi) to be able to do releases. Currently I only know the following > cheeseshop usernames however: > > hpk > ronny > flub > nicoddemus > anatoly > > So could other people in pytest-dev on either bitbucket or github > please let me know their usernames? Preferably gpg signed and/or > encrypted if possible [0][1], but don't worry too much if not. > > Additionally I only have the permissions to do this on the following > packages: > > pytest > pytest-xdist > pytest-timeout (not yet in pytest-dev but it really should be ;-)) > > In particular I'm missing access to py :-) > > Could owners of other repos enable other people as well if they agree? > Or if you can't be bothered to do this currently very manual task for > everyone just give me permissions and tell me to add the full list of > people and I'll patiently go through the list. > > Regards, > Floris > > [0] My key is 4CCB3FFC, as signed > > [1] I also have keybase.io invites if you'd like some form of > verification. Keybase provides an easy way to "prove" a > particular private key can control a particular github account, > which has it's use [2]. > > [2] Not that this couldn't be done manually, but everyone is bad with > manually doing things as proven by after having met Holger a few > times in real life we still haven't verified our keys despite > using them sometimes in email. Ah, gpg. _______________________________________________ pytest-dev mailing list [email protected] https://mail.python.org/mailman/listinfo/pytest-dev
