4e23eb18a0
By design, accessbot doesn't *remove* access when you remove yourself from the access lists; you are just limited to a lower level. This is noted in the configuration file: # The label 'mask' is special: anyone with perms on a channel that # isn't otherwise listed for the channel or in the global list will # have their access limited to the mask but otherwise left alone. However I'm feel like it's reasonable to assume that when you remove yourself you are giving up your permissions; and in the *very* unlikely case of a bad actor, we would want to know we did actually remove them from all channels. To make this clearer, but still allow for unlisted users to maintain whatever permissions they have, this adds an "alumni" section to the configuration, and allows for alumni to be set on individual channels. If your nick appears in this list, your access is removed. Obviously once this has run once, people could be removed from alumni if there is a need to cater for something tricky like removing global access but then adding permissions. But in general I think it will work to just keep a record of contributors in the common case of "moved on from openstack work and no longer want to admin things". Change-Id: I0858e963cdf4bc90c30f9d60ea524d778ae3d150 |
||
|---|---|---|
| files | ||
| manifests | ||
| spec/acceptance | ||
| templates | ||
| .gitignore | ||
| .gitreview | ||
| Gemfile | ||
| LICENSE | ||
| README.md | ||
| Rakefile | ||
| bindep.txt | ||
| metadata.json | ||
README.md
OpenStack Accessbot Module
Overview
Configures Accessbot.